SQL Server performance considerations when configuring a SAN

Digg This!     StumbleUpon     Del.icio.us

RELATED CONTENT Microsoft SQL Server Performance Monitoring and Tuning Using traces in SQL Server Profiler SQL Server Mailbag: CALs, witnesses and unwanted changes SQL Server Mailbag: Data restoration and DB property management Working with IntelliSense in SQL Server 2008 Management Studio SQL Server Mailbag: Stored procedures, triggers and SSRS reports Troubleshooting Distributed Transaction Coordinator errors in SQL Server Clearing the Windows page file and its effect on server performance Optimizing SQL Server indexes –- even when they're not your indexes Performance implications of transaction log autogrowth in SQL Server The short course on how SQL Server really works Archive: Performance Tuning Upgrading to SQL Server 2008 advantages and hardware requirements Tool to synchronize two SQL Server databases Performance tuning for SQL Server 2005 and Exchange running on SBS SQL Server tools don't appear in menu after SQL Server 2005 install Use SQL Profiler to find long running stored procedures and commands Maintain large SQL Server database and resolve website 'Timeout Error' How to retrieve SQL Server database disk space in use Troubleshoot SQL Server 2005 temporary table performance problems View query execution plan in SQL Server with this method Adding non-clustered indexes to SQL Server columns

RELATED GLOSSARY TERMS Terms from Whatis.com − the technology online dictionary contiguity  (SearchSQLServer.com) contiguous  (SearchSQLServer.com) drilldown  (SearchSQLServer.com) hashing  (SearchSQLServer.com) hybrid online analytical processing  (SearchSQLServer.com)

RELATED RESOURCES 2020software.com, trial software downloads for accounting software, ERP software, CRM software and business software systems Search Bitpipe.com for the latest white papers and business webcasts Whatis.com, the online computer dictionary

I could use your advice in determining the following information from a performance point of view:

1. Location of the databases or files


2. RAID level


3. Number of files to use for the tempdb


4. How to configure the SAN for the above requirements

At a high level, I would recommend having this discussion with your DBAs, network engineers, storage administrators and SAN vendor. Depending on the SAN, you can have a variety of options. I would say to physically split your databases from your transaction logs on the SAN, and split your SQL Server data from other processing. You should plan how the SAN will be used in the long term so you do not have I/O contention. Next, the RAID level is SAN dependent. The fastest and most costly would be RAID 1, but I would see what other options your vendor can offer. For tempdb sized at 10 to 15 GB, I would recommend 1 MDF and 1 LDF. Finally, make sure you have redundancy to your SAN from your SQL Server, so you have no single points of failure.