SAN Storage Best Practices for SQL Server

I bet you’re here because you don’t trust your SAN administrator.  The SAN admin’s been telling you everything’s fine, and that it must be a SQL Server problem, right?

Odds are, it’s not.  Time to learn what SQL Server needs from its storage, and what SAN admins need from us database administrators.

SQL Server Storage Performance Tuning

Whew!  We’ve got the SAN controllers, pathing, and Windows set up correctly, and now it’s time to install SQL Server and put our databases on it.  Here’s my thoughts on how to do it:

SAN Optimization Tips for SQL Server Performance

SAN gear is notoriously difficult to configure, but thankfully, storage vendors put a lot of work into writing good documentation on how to set up their gear for SQL Server.  Read this stuff, and believe me, there’s some fantastic tips in here that can make all the difference between good performance and bad.

Here’s the most common vendor document repositories:

Look for document titles that include the words setup, configuration, best practices, guidelines, and so on.  These are the least likely to be marketing.  If the document isn’t at least 10 pages long, skip it and keep looking – short documents tend to be marketing fluff.  The longer documents will tell you the right RAID type to use for data files, log files, and tempdb, plus much more like stripe sizes and cache configurations.

When you find the right one for your storage gear, hand the guidelines to your SAN administrator – that’s your best chance to get the right settings.  Ask them to show you the SAN management software to verify each of the settings listed in the manufacturer’s guidelines.

How to Connect SQL Servers to the SAN

The term SAN gets misused a lot because it really means Storage Area Network – the communication pipelines between your server and a magic black box called a SAN controller.  That controller is the configurable hardware that manages RAID levels, caching, and more.  Here, we’re talking about how we plug your SQL Server into the network (SAN) itself, and how it gets there is called pathing.  Here’s my articles on it:

Microsoft’s Recommendations for Storage Speed

When you need to go up against the SAN guy to prove there’s a storage problem, get Microsoft in your corner.  Here’s Microsoft’s guidelines on storage latency numbers:

  • SQLCat Troubleshooting Logs – “With respect to #1 our recommendation for response time on the log device should be in the range of <1ms to 5ms.”

Contact Us for SQL Server & SAN Performance Help

We’re here for you.  Brent Ozar Unlimited is a boutique consulting firm focused on understanding your environment and strategy. We partner with you to objectively identify pain points and develop remedies that align to your business goals.  Your experience comes first; we share our knowledge and expertise to help you.

Want to get started immediately? We’ve got video training. Our VMware, SANs, and Hardware for SQL Server DBAs Training Video is a 5-hour training video series explaining how to buy the right hardware, configure it, and set up SQL Server for the best performance and reliability. Here’s a preview:

Buy it now.