This month, I spent some time adding columns for the new SERVERPROPERTY options, along with adding more comments and links to the scripts. 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 as I discover interesting new things in SQL Server 2016. 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 and save me time in looking up supporting documentation.
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 (October 2015)
SQL Server 2016 Blank Results
SQL Server 2014 Diagnostic Information Queries (October 2015)
SQL Server 2014 Blank Results
SQL Server 2012 Diagnostic Information Queries (October 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 seven 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 starting at 9:30AM on Friday, Oct 30, 2015 in Seattle.
Please let me know what you think of these queries, and whether you have any suggestions for improvements. Thanks!
9 thoughts on “SQL Server Diagnostic Information Queries for October 2015”
Your queries are fantastic and the session @ PASS Summit 2015 was even better. Thanks for the session and for providing these!
Glad you liked the session! It was fun to deliver it over a longer period, so I did not have to rush.
I was also able to attend your PASS 2015 session, and it was very enjoyable. About 5 or 10 minutes of slides and the rest was demos! Lots of fun. I do have a question, though. Do you have any sort of license that people use these scripts under (similar to the license that Ola Hallengren distributes his scripts via)?
There is some licensing language in the scripts themselves.
Your presentation at PASS was fantastic. Thanks for providing such a valuable resource.
Thanks for the scripts as well as the presentation at PASS! It was a great session.
One very small potential correction as I’ve been using the scripts: for query 65, the “blocker_stmt” column really should be called “blocker_batch”. Taking into account the distinction made between “waiter_batch” and “waiter_stmt”, the logic applied to the blocker’s SQL text actually matches the logic applied to “waiter_batch” by taking the full batch without applying any statement start/end offsets.
Glad you liked the session at PASS. I have changed the column alias as you have suggested. Thanks!