3 lessons learned about Azure SQL Database
Hosted cloud databases make a lot of administrative tasks easier, or take care of them for you altogether.
But here are three things that I’ve found a little too easy to forget about Azure SQL Database.
Hosted cloud databases make a lot of administrative tasks easier, or take care of them for you altogether.
But here are three things that I’ve found a little too easy to forget about Azure SQL Database.
We’ve just published a new article in the SQL docs, Tune nonclustered indexes with missing index suggestions . The article explains what the missing index feature is, limitations of the feature, and how to use missing index DMVs and missing index suggestions in Query Store to tune indexes.
During a discussion of troubleshooting query timeouts in Azure SQL Database recently, I thought – hey, I wonder if you can find queries that timed out in Query Store?
Turns out, you can.
We’ve recently updated the SQL Server and Azure SQL index architecture and design guide. This article is an in-depth guide to indexing in databases using the SQL Server engine, including SQL Server, Azure SQL Database, Azure SQL Managed Instance, and Azure Synapse Analytics.
Our recent update adds a table to categorize the types of indexes discussed in the article, clarifies B-trees vs B+ trees, and describes how row locators (aka “secret columns”) are used in nonclustered indexes.
We now explicitly define ‘requests’ and ‘workers’ in the Azure SQL Database documentation, and we’ve cleaned up multiple places where we used to equate the two terms. In this post, I share the history of the two terms when it comes to Azure SQL Database, why the two were ever equated, and why things like this are tricky to change.
Writing helps me learn. In my job as a Content Developer, this is more true than ever: there’s a fantastic group of folks, both in the Database Docs team and in the Microsoft Data Platform engineering team, who review and contribute to content.
I’ve just had the pleasure of publishing my first new article in the Microsoft Docs, Diagnose and troubleshoot high CPU on Azure SQL Database.
I’d like to openly and honestly answer the rumors that I have been removed from the Microsoft MVP program.
Have you ever tried to create an object in SQL Server, but it failed due to a missing table, column, or other dependency? If so, you’ve hit a case where SQL Server doesn’t offer ‘deferred name resolution’.
Have you been meaning to learn about SQL Server in the Azure cloud, but never seem to get around to it? It’s easy to be overwhelmed and not know where to begin.
I recommend you start with the Azure SQL Fundamentals Learning Path.
I stepped through this training this week and WOW, this is an incredibly high quality free course, complete with hands-on exercises in an online sandbox. I wish I’d done this sooner!
Today I walked through the Use Azure Data Studio to connect and query Azure SQL database Quickstart. This Quickstart is solid and is great for someone new to Azure Data Studio.
At the end of the Quickstart it suggested I try the Tutorial: Use the Transact-SQL editor to create database objects - Azure Data Studio. The tutorial taught me a couple of things that I’ve not noticed about Azure Data Studio, even though I’ve used it for a couple of years.
Copyright (c) 2024, Catalyze SQL, LLC; all rights reserved. Opinions expressed on this site are solely those of Kendra Little of Catalyze SQL, LLC. Content policy: Short excerpts of blog posts (3 sentences) may be republished, but longer excerpts and artwork cannot be shared without explicit permission.