As Kimberly blogged about earlier this year<\/a>, SQLskills has an ongoing initiative to blog about basic topics, which we\u2019re calling SQL101. We\u2019re all blogging about things that we often see done incorrectly, technologies used the wrong way, or where there are many misunderstandings that lead to serious problems. If you want to find all of our SQLskills SQL101<\/strong> blog posts, check out SQLskills.com\/help\/SQL101<\/a>.<\/em><\/p>\n

If you are ready to start working with Azure SQL Database<\/a>, which is Microsoft\u2019s Platform as a Service (PaaS) offering for SQL Server, you will want some good diagnostic queries to use to help you better understand how your databases are performing and to give you more information than is exposed by the Azure Portal. After much delay and procrastination on my part, I have finally<\/u><\/strong> developed a version of my SQL Server Diagnostic Information Queries that are tailored for use with Azure SQL Database.<\/p>\n

Azure SQL Database Diagnostic Information Queries<\/a><\/p>\n

\n

Azure SQL Database Blank Results Spreadsheet<\/a><\/font><\/p>\n<\/blockquote>\n

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. <\/p>\n

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 \u201cCopy with Headers\u201d 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. <\/p>\n

Please let me know what you think of these queries, and whether you have any suggestions for improvements. Thanks!<\/p>\n","protected":false},"excerpt":{"rendered":"

As Kimberly blogged about earlier this year, SQLskills has an ongoing initiative to blog about basic topics, which we\u2019re calling SQL101. We\u2019re all blogging about things that we often see done incorrectly, technologies used the wrong way, or where there are many misunderstandings that lead to serious problems. If you want to find all of […]<\/p>\n","protected":false},"author":7,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[212,176,309],"tags":[355],"class_list":["post-1273","post","type-post","status-publish","format-standard","hentry","category-azure-sql-database","category-dmv-queries","category-sql101","tag-azure-sql-database"],"yoast_head":"\n