http://www.sqlservercentral.com/blogs/glennberry/2013/11/15/sql-server-diagnostic-information-queries-for-november-2013/

Printed 2014/09/16 02:14PM

SQL Server Diagnostic Information Queries for November 2013

2013/11/15

I have made a number updates and bug fixes, including some additional columns in some of the queries for all of the versions of my SQL Server Diagnostic Information Queries for this month.  I have also added more comments and links about how to interpret the results.

Rather than having a separate blog post for each version, I’ll just put the links for all five major versions here. There are two separate links for each version. The one on the left is the actual script, and the one on the right is the blank results spreadsheet.

SQL Server 2005 Diagnostic Information Queries SQL Server 2005 Blank Results

SQL Server 2008 Diagnostic Information Queries SQL Server 2008 Blank Results

SQL Server 2008 R2 Diagnostic Information Queries SQL Server 2008 R2 Blank Results

SQL Server 2012 Diagnostic Information Queries SQL Server 2012 Blank Results

SQL Server 2014 Diagnostic Information Queries SQL Server 2014 Blank Results

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.

The idea is that you would run each query in the set, one at a time (after reading the directions). You need to click on the top left square of the results grid 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 spreadsheet. There are also some comments on how to interpret the results after each query.

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 databases in 80 compatibility mode, which breaks many DMV queries.

There is an initial query in each version that tries to confirm that you are using the correct version of the script for your version of SQL Server.

Please let me know what you think of these queries, and whether you have any suggestions for improvements. Thanks!


Filed under: Diagnostic Queries, SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, SQL Server 2012, SQL Server 2014 Tagged: DMV, DMV Queries
Copyright © 2002-2014 Simple Talk Publishing. All Rights Reserved. Privacy Policy. Terms of Use. Report Abuse.