This month, I have added a new query for SQL Server 2016, that checks your QueryStore options. The SQL Server 2016 version will continue to be improved with more SQL Server 2016-specific queries and new columns in existing queries over the next few months. I am also continuing to add more relevant comments and links to the other active versions of these queries in order to help better interpret the results of these queries.
Rather than having a separate blog post for each version, I have just put the links for all six major versions in this single post. There are two separate links for each version. The first one on the top left is the actual diagnostic query script, and the one below on the right is the matching blank results spreadsheet, with labeled tabs that correspond to each query in the set.
Here are links to the latest versions of these queries for SQL Server 2016, 2014 and 2012:
SQL Server 2016 Diagnostic Information Queries (August 2015)
SQL Server 2016 Blank Results
SQL Server 2014 Diagnostic Information Queries (August 2015)
SQL Server 2014 Blank Results
SQL Server 2012 Diagnostic Information Queries (August 2015)
SQL Server 2012 Blank Results
Here are links to the most recent versions of these scripts for SQL Server 2008 R2 and older:
Since SQL Server 2008 R2 and older are out of Mainstream support from Microsoft (and because fewer of my customers are using these old versions of SQL Server), I am not going to be updating the scripts for these older versions of SQL Server every single month going forward. I started this policy four months ago, and so far, I have not heard any complaints.
SQL Server 2008 R2 Diagnostic Information Queries
SQL Server 2008 R2 Blank Results
SQL Server 2008 Diagnostic Information Queries
SQL Server 2008 Blank Results
SQL Server 2005 Diagnostic Information Queries
SQL Server 2005 Blank Results
The basic instructions for using these queries is that you should run each query in the set, one at a time (after reading the directions for that query). It is not really a good idea to simply run the entire batch in one shot, especially the first time you run these queries on a particular server, since some of these queries can take some time to run, depending on your workload and hardware. I also think it is very helpful to run each query, look at the results (and my comments on how to interpret the results) and think about the emerging picture of what is happening on your server as you go through the complete set. I have some comments in the script on how to interpret the results after each query.
You need to click on the top left square of the results grid in SQL Server Management Studio (SSMS) to select all of the results, and then right-click and select “Copy with Headers” to copy all of the results, including the column headers to the Windows clipboard. Then you paste the results into the matching tab in the blank results spreadsheet.
About half of the queries are instance specific and about half are database specific, so you will want to make sure you are connected to a database that you are concerned about instead of the master system database. Running the database-specific queries while being connected to the master database is a very common mistake that I see people making when they run these queries.
Note: These queries are stored on Dropbox. I occasionally get reports that the links to the queries and blank results spreadsheets do not work, which is most likely because Dropbox is blocked wherever people are trying to connect.
I also occasionally get reports that some of the queries simply don’t work. This usually turns out to be an issue where people have some of their user databases in 80 compatibility mode, which breaks many DMV queries, or that someone is running an incorrect version of the script for their version of SQL Server.
It is very important that you are running the correct version of the script that matches the major version of SQL Server that you are running. There is an initial query in each script that tries to confirm that you are using the correct version of the script for your version of SQL Server. If you are not using the correct version of these queries for your version of SQL Server, some of the queries are not going to work correctly.
If you want to understand how to better run and interpret these queries, you should consider listening to my three latest Pluralsight courses, which are SQL Server 2014 DMV Diagnostic Queries – Part 1 , SQL Server 2014 DMV Diagnostic Queries – Part 2 and SQL Server 2014 DMV Diagnostic Queries – Part 3. All three of these courses are pretty short and to the point, at 67, 77, and 68 minutes respectively. Listening to these three courses is really the best way to thank me for maintaining and improving these scripts…
Finally, if you want to get even more information about how to run and interpret these queries, you should consider attending my half-day session Dr. DMV’s Troubleshooting Toolkit at the PASS Summit 2015 in Seattle this October.
Please let me know what you think of these queries, and whether you have any suggestions for improvements. Thanks!
2 thoughts on “SQL Server Diagnostic Information Queries for August 2015”
Diagnostic Queries 2012: Query # 49 and likewise (Related Performance Counters)
We come across some vague picture about Parallelism and their Logging logic in different “DMVs” (if it is the case) i.e. in case of parallel run the cost/logging counters etc would be incorrectly logged or can be calculated by any other method etc and etc.
We need to reconfirm from you, that provided queries and logic is still applicable for both parallel and single threaded execution? Or we need to have a different branch of scripts to cater parallelism impact?
I wanted to thank you for producing these courses on pluralsight. They have significantly improved my knowledge of DMVs. I am new to the DBA field, and within 9 months and with tons of studying I have learned a good amount.
I have worked with several different DBA’s and you know none of them could tell me how to utilize DMVs or even utilized DMVs most of the time. They troubleshot things starting at the windows error log/perfmon and worked from there.
I find the DMVs far more efficient, and excellent for building a knowledge source to better inform my clients about the status of their machines (along with my recommendations). I couldn’t do it without your help!