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.
I’m working through a series of tutorials and learning paths for Azure SQL and sharing bite-sized reviews.
In this first walkthrough, I’m stepping through the Create a Single Database tutorial.
This post is part of TSQLTuesday #140, “What have you been up to with containers?"
Disposable databases are indispensable for software developers, both for initial development work and in automation pipelines. Containers pair exceptionally well with temporary databases and provide a lightweight mechanism to spin up an environment on demand.
When I woke up today in the UK, Twitter was alive with jokes, hot takes, and sympathy about an email sent out to millions of folks on a contact list for HBO Max featuring the subject line, “Integration Test Email #1”.
One big gotcha that teams often encounter when automating deployments for databases is that it’s difficult– or sometimes impossible – to ensure that all changes to the production database are performed through the automation pipeline.
These out-of-band changes case the production database to “drift” away from the schema as defined in version control.
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.
