5 SQL Server White Papers Every DBA Should Read

reading coffee shopThere are countless sources for information on SQL Server available today.  There are books, webcasts, conferences, and blogs.  With all of these sources, it is easy to forget that there are white papers available from Microsoft.  It is important that  we make an effort to read the white papers that are available.

The trouble is, there are so many white papers available from Microsoft and other sources, we need to know which are most important.  Should those from the latest release of SQL Server trump the older white papers?  If a white paper hasn’t been updated, is it still valuable?

As I’ve thought about this, there are a few Microsoft white papers that are available that are more important than others.  They should be read by every DBA, and anyone that has a hand in managing or administering a SQL Server environment.  These are:

  1. Troubleshooting Performance Problems in SQL Server 2008 (also available for SQL Server 2005) –  This whitepaper is where I first turn people when they want to start learning about how to fix their performance issues with SQL Server.  It hasn’t been updated for SQL Server 2012, but the concepts remain the same, and the approaches recommended are just as valid.
  2. SQL Server 2005 Performance Tuning using the Waits and Queues – Similar to the first item, here’s another white paper in desperate need of an update but with information just as useful today as when it was first written.  When you look at how many DBAs performance tune their environments today, the roots of those methodologies are found in this white paper.  In fact, many third party monitoring tools are built around this white paper.
  3. SQL Server 2012 Security Best Practices – Security is never one of the most exciting topics, but this white paper walks through some basics, and helps dispel some myths.  It’s one of those papers that can easily provide a quick reference for security questions. It has an easily digestible length, and can be used to send to managers and peers when security questions arise.
  4. AlwaysOn Architecture Guide: Building a High Availability and Disaster Recovery Solution by Using AlwaysOn Availability Groups (for SQL Server 2008 R2 – Proven SQL Server Architectures for High Availability and Disaster Recovery) – When it comes to maintaining availability of data and your environment, you need to be well aware of the options and how all the moving parts can fit together.  These white papers provide that perspective.  Since the options between SQL Server 2008 and 2012 are so different, it is important to read both of these.
  5. SQL Server 2012 Upgrade Technical Reference Guide Whitepaper – Contrary to the other white papers in this list, this document is fairly large, coming in at 454 pages.  While lengthy, this document should be kept on hand and read through prior to any SQL Server 2012 upgrade.  In fact, when people suggest doing “a quick weekend upgrade”, send this over to them beforehand to verify that they’ve considered everything in the document already.  Not to stop or slow down the upgrade, but you need to be sure that upgrades don’t lead to disasters, because at the end of the day DBAs will be responsible for those results.

The white papers listed above are just a few of the ones available from Microsoft.  There are countless others, and even more from other vendors.  What white papers do you recommend to others on SQL Server?

Happy reading.

20 thoughts on “5 SQL Server White Papers Every DBA Should Read

    1. Thanks for the comment, that one is great as well. It may be time to do an ETL version of this post.


  1. Awesome Artical Really i have searching this type of valuable information From a lot of days i found satisfaction when Read your blog Thanks for giving this type blog and also please Read link bvba Woodstone which provide information server monitoring software & Network monitoring tools


  2. Will definitely read these sources! Esp. no.4, with all the hacking and downtime issues happening around the web it is very important to be aware of the possible options that we can do in order to resolve such issues.


    1. Thanks. Same here on #5 – too often I’ve talked to people that have missed out on that white paper (and the ones on previous versions) and then heard them talk about the problems they’ve run into – which the white paper would have helped prevent.


    1. Another good one, I might need to put together a set of BI focused white papers for people to reference.


    1. Thanks for stopping by and leaving a comment. Security is always a good topic, and one that a lot of people like to leave for later… and then forget about.


Comments are closed.