Glenn Berry2 Comments on SQL Server Diagnostic Information Queries for March 2023

SQL Server Diagnostic Information Queries for March 2023

Introduction

These are my SQL Server Diagnostic Information Queries for March 2023, aka my DMV Diagnostic Queries. They allow you to get a very comprehensive view of the configuration and performance of your SQL Server instance in a relatively short amount of time. This post is about my SQL Server Diagnostic Information Queries for March 2023.

There are separate versions of these T-SQL queries for SQL Server 2005 through SQL Server 2022.

I also have separate versions for Azure SQL Managed Instance and Azure SQL Database. My diagnostic queries have been used by many people around the world since 2009. I make regular improvements to these queries each month.

SQL Server Diagnostic Information Queries for March 2023
SQL Server Diagnostic Information Queries for March 2023

SQL Server Diagnostic Information Queries for March 2023

As always, I have made additional small improvements and corrections to all of the versions of these queries. There is now a separate version of these queries for SQL Server 2022. Recently, I have added a new Backup Compression Ratio column to an existing query for SQL Server 2012 through SQL Server 2022. It is:

  • Last backup information by database (Query 8) (Last Backup By Database)

I have also added additional SQL Server 2022 specific columns to several other queries.

Making YouTube videos about these queries has forced me to look at some of them with a new perspective. I am also using these queries very intensively at Koerber Supply Chain Software, so expect even more improvements in the next few months!

This video walks through all of the Diagnostic Information queries from the SQL Server 2019 set.

BTW, 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. They are always available from my Resources page.

Rather than having a separate blog post for each version, I have just put the links for all twelve major versions in this 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 Managed Instance, Azure SQL Database, and all available versions of SQL Server:

Azure SQL Diagnostic Queries

SQL Server Diagnostic Queries

Legacy SQL Server Diagnostic Queries

Usage Instructions

The basic instructions for manually running these queries is that you should run each query in the set, one at a time. You should read the directions for each query and my comments on how to interpret the results. It is not a good idea to simply run the entire batch in one shot. This is especially true the first time you run these queries on a particular server. Some of these queries can take some time to run, depending on your workload and hardware.

It is very useful to run each query, look at the results and think about the emerging picture of what is happening on your server. I have quite a few comments and links in the script on how to interpret the results after each query.

Saving the Results

After running each query, you click on the top left square of the results grid in SQL Server Management Studio (SSMS) to select all of the results. Next, you right-click and select “Copy with Headers” to copy the results, including the column headers to the Windows clipboard. Finally, 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. Because of this, make sure you are connected to a database that you are concerned about! Make sure you are not connected to the master system database. Running the database-specific queries while being connected to the master database is a very common mistake. As a result, I often see people make this mistake when they run these queries.

Dropbox

Note: These queries are stored on Dropbox. I occasionally hear that the links to the queries and blank results spreadsheets don’t work. This is usually because Dropbox is blocked where someone is trying to connect. I am not planning on moving these to Github any time soon, but I could change my mind.

Unfortunately, I sometimes get reports that some of the queries simply don’t work. This usually happens with an incorrect version of the script for the version of SQL Server. Sometimes, it turns out to be an issue where people have some of their user databases in 80 compatibility mode. This will break many DMV queries. This is less common than it used to be, since more people are on newer versions of SQL Server that don’t support 80 compatibility mode.

It is very important that you are running the script that matches the version of SQL Server that you are running. There is an initial query in each script that confirms that you are using the correct version of the script. If you are not using the correct version of these queries, you will have problems.

Checking Spectre/Meltdown Status

In addition, I have a T-SQL script to check whether an instance of SQL Server has been patched to mitigate against the Spectre/Meltdown CPU vulnerability. This query works for SQL Server 2008 through SQL Server 2019, for on-premises and cloud-based VM (IaaS) usage. SQL Server 2019 actually has this fix in all builds, so you don’t have to check SQL Server 2019 instances. You can get the query for this here.

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

I recorded a PASS Summit session in October of 2020 featuring the Juypter notebook version of these queries. The video for that is embedded below.

Dr DMV with Jupyter Notebooks

Additional Resources

If you want to understand how to better interpret these queries, you should listen to my YouTube videos that walk through how to interpret the results of each of these queries.

These are the ones I have completed so far:

Watching and “liking” these videos is really the best way to thank me for maintaining and improving these scripts…

If you have any questions about this post, please ask me here in the comments or on Twitter. I am pretty active on Twitter as GlennAlanBerry. Thanks for reading!

2 thoughts on “SQL Server Diagnostic Information Queries for March 2023”

  1. Alain Martin March 21, 2023 — 3:06 pm

    Hello Glenn, big fan here of your script! One of our instance has been update from 64 tp 72 cores. And we hit negative numbers for (Query 42) (CPU Utilization History). I found something here but seems not ok also (compare to pure perfmon on the box) Any alternative on this? https://support.solarwinds.com/SuccessCenter/s/article/CPU-utilization-is-not-displayed-properly-in-DPA?language=en_US

    Reply
    1. (Post author)
      Glenn Berry March 21, 2023 — 4:04 pm

      Unfortunately no. I see this fairly often with > 64 cores. sys.dm_os_ring_buffers is undocumented and unsupported.

      I doubt Microsoft will fix it, it has been an issue for many years and versions.

      Reply

Please tell me what you think

Discover more from Glenn's SQL Server Performance

Subscribe now to keep reading and get access to the full archive.

Continue reading