SQL Server Diagnostic Information Queries for November 2017

This month, there are more minor updates to the all of the versions of the queries, primarily in the comments and documentation. I often make additional minor updates to the queries periodically during the month, so if you are in doubt, downloading the latest version is always a good idea.

Rather than having a separate blog post for each version, I have just put the links for all seven 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 Azure SQL Database, SQL Server 2017, 2016, 2014 and 2012:

Azure SQL Database Diagnostic Information Queries

Azure SQL Database Blank Results Spreadsheet

SQL Server 2017 Diagnostic Information Queries

SQL Server 2017 Blank Results Spreadsheet

SQL Server 2016 Diagnostic Information Queries

SQL Server 2016 Blank Results Spreadsheet

SQL Server 2014 Diagnostic Information Queries

SQL Server 2014 Blank Results Spreadsheet

SQL Server 2012 Diagnostic Information Queries

SQL Server 2012 Blank Results Spreadsheet

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 a while ago, and so far, I have not heard any complaints. I have made some updates to these queries periodically since January.

SQL Server 2008 R2 Diagnostic Information Queries

SQL Server 2008 R2 Blank Results Spreadsheet

SQL Server 2008 Diagnostic Information Queries

SQL Server 2008 Blank Results Spreadsheet

SQL Server 2005 Diagnostic Information Queries

SQL Server 2005 Blank Results Spreadsheet

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 quite a few comments and links in the script on how to interpret the results after each query.

After running 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 am not planning on moving these to Github any time soon.

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 related Pluralsight courses, which are SQL Server 2014 DMV Diagnostic Queries – Part 1SQL 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…

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

Presenting Two Sessions at the PASS Summit 2017 in Seattle

I’ll be presenting two sessions at the PASS Summit 2017 in Seattle, WA. There will be a half-day session called Migrating to SQL Server 2017 on Wednesday, November 1 in Room 6A, starting at 3:15PM, and then a regular session called Improving SQL Server Performance on Thursday, November 2 in Room 612, starting at 4:45PM.

Here are the abstracts:

Migrating to SQL Server 2017

How do you design and implement a safe and successful migration from an older version of SQL Server to SQL Server 2017 with no data loss and virtually no downtime? What if you have a limited hardware budget for the upgrade effort and you are worried about the core-based licensing in SQL Server 2017? How can you choose your hardware wisely in light of the new licensing model? How can you convince your organization that the time is right to upgrade to SQL Server 2017? This session will cover several different methods for migrating your data to SQL Server 2017 while meeting these objectives and minimizing your hardware and licensing costs. You will also learn how to help make the case that a complete data platform upgrade makes excellent sense from a business perspective. You will also learn how to do effective capacity planning for the new environment to ensure that you have the best performance possible with a manageable SQL Server 2017 licensing cost.


Improving SQL Server Performance

Has anyone ever told you that your SQL Server database or instance was running too fast? Probably not, but it is all too common to hear complaints about poor performance. As a database professional, you need to have the right tools and techniques for finding and correcting performance bottlenecks at all layers of your SQL Server instance. Starting with your hardware and storage, including virtualization, operating system considerations, instance-level configuration settings, database properties, and concluding with index and query tuning, we will cover all of the layers of common performance bottlenecks. You will learn detailed and practical information for improving SQL Server performance at every layer in the system.


My SQLskills colleague, Erin Stellato will also be at the PASS Summit 2017, presenting a pre-conference session called Solving Common Performance Problems Using Query Store on Monday, October 30, and then two regular sessions: Query Store and Automatic Tuning in SQL Server and Data Systems at Scale – A Panel Discussion on November 1 and November 2, respectively.


The PASS Summit is always a fun and useful conference, where you can connect and reconnect to people in the SQL Server Community. I hope to see you there, in my sessions and in the hallways and escalators!

Update: Just to make it easier to find, here are links to my Migrating to SQL Server 2017 session, Migrating to SQL Server 2017 demos, Improving SQL Server Performance session, and Improving SQL Server Performance demos.




SQL Server 2017 CU1 is Available

On October 24, 2017, Microsoft released SQL Server 2017 Cumulative Update 1, which is Build 14.0.3006.16. This CU has 68 hot fixes by my count, which is a fairly high count. This shows that Microsoft has been busy fixing issues that have shown up since the RTM build. I think this is a good thing.

Keep in mind that Microsoft has revised their servicing model for SQL Server 2017, with what they are calling the Modern Servicing Model for SQL Server, as I discussed here.

The gist of this new servicing model is that there will be no Service Packs for SQL Server 2017. Cumulative Updates will be released every month for the first year after GA, on the 3rd Tuesday of each month. After that, they will be released every three months, for the next four years, until SQL Server 2017 falls out of Mainstream support on October 11, 2022.

This means that hot fixes will be available more quickly during the first year, when most of the issues are discovered and corrected. You don’t have to install every single CU when it is released, but you should make a habit of looking at the fix list for each CU, to see if anything that might be affecting you is included. Once you do install the latest CU (which Microsoft recommends you do proactively), you will have all of the hotfixes since RTM, since they are actually cumulative in nature, as the name suggests.