
Consolidating multiple SQL Server systems onto
Dell PowerEdge R610 Servers using Microsoft’s Hyper-V
20
Configuring the physical RAID disk layout
Overview
Following Microsoft’s recommended best practices, we planned to
separate our virtualized disk activity, just as we would with a
physical machine. However, although we created separate virtual
disks for each activity type, we let the EqualLogic PS5000 SAN
manage the actual layout of the storage.
• NOTE: Plan on at least 30 minutes for drive configuration
on the server.
A note on virtualized storage
In a Hyper-V environment, you have three options available for
storage: pass-through disks, fixed-size VHDs, and dynamically
sized VHDs. If speed is your primary concern, pass-through disks
are the best option. However, pass-through disks require you to
allocate a dedicated disk to a virtual machine, making pass-
through disks less flexible. We chose to use fixed-size VHDs. This
gave us the flexibility of virtualizing our disks and better
performance over dynamically sized VHDs. You can find more
information on storage performance considerations in the Microsoft
SQL Server and Hyper-V white paper here:
http://download.microsoft.com/download/d/9/4/d948f981-926e-
40fa-a026-5bfcf076d9b9/SQL2008inHyperV2008.docx.
• BEST PRACTICE: Hyper-V requires that the operating
system VHD be on an IDE controller. For better
performance, you should attach your other virtual hard
disks to a virtual SCSI controller instead of to virtual IDE
controllers.
Tempdb database
SQL Server creates the tempdb system database, which all
databases on the SQL instance share. SQL Server uses the tempdb
database for such purposes as temporary tables, table variables,
work files for hash operations, sorting, building aggregates for
GROUP BY or ORDER BY clauses, index builds, INSERTED and
DELETED tables that triggers use, and cursor processing.
Transaction log files
Each database has one or more transaction log files. A transaction
log file stores the details for all transactions in a SQL Server
database. This information is critical for restoring database
consistency in the event of a failure.
Kommentare zu diesen Handbüchern