Database Reference
In-Depth Information
The starting point for any storage architecture for SQL Server Databases is actually
with our last design principle: KISS (Keep It Standardized and Simple). But all of the
principles apply. We will determine the smallest number of templates that are required
to virtualize the majority (95%) of database systems, and anything that falls outside this
will be handled as an exception.
Your first step is to analyze the inventory of the SQL Server Databases that will be
virtualized as part of your project (refer to Chapter 4 , Virtualizing SQL Server 2012:
Doing It Right ”). From this inventory, you will now put each database and server into a
group with similar-sized databases that have similar requirements. The storage
requirements for all of these existing and new databases, based on their grouping, will
be used to define the storage layouts and architecture for each of the SQL Server
Databases, Guest OS, and VM template.
Tip
If you are virtualizing existing databases, you might consider using a tool such as
VMware Capacity Planner, VMware Application Dependency Planner, Microsoft
System Center, or Microsoft Assessment and Planning Toolkit to produce the
inventory. VMware Capacity Planner and Application Dependency Planner are
available from VMware Professional Services or your preferred VMware
partner. When you're baselining a SQL Server database, a lot can happen in a
minute. We recommend your sample period for CPU, Memory, and Disk be 15
seconds or less. We recommend you sample T-SQL every minute.
SQL Server Database File Layout
Database file layout provides an important component of database storage performance.
If you have existing databases that will be virtualized, you or your DBAs will likely
have already developed some practices around the number of database files, the size of
 
 
Search WWH ::




Custom Search