Introduction of Azure SQL Hyperscale: Stairway to Azure SQL Hyperscale Level 1
In Level 1 of the Stairway to Azure SQL Hyperscale, we learn about the architecture and create a hyperscale instance.
2025-09-03
3,950 reads
Azure SQL
Deploy DACPAC to Azure SQL Database using Visual Studio
This guide will walk you through the process of deploy DACPAC to Azure SQL database directly from Visual Studio.
2025-03-10
1,704 reads
Serverless Gets Faster
In Azure SQL Database serverless edition, we get an upgrade to our configuration.
2024-10-12
124 reads
2024-03-29
8,621 reads
Deploying Azure SQL Database Using an ARM Template
Provisioning infrastructure in a timely and reliable manner is essential for agile development. One well-liked method that lets you use code to automate resource management and provisioning is infrastructure as code (IaC). Azure Resource Manager templates are one IaC solution for Azure (ARM templates).
2024-02-02
2,695 reads
Optimized locking in Azure SQL Database
I don’t think I’ve ever had a great impression of Azure SQL Database as a place for production applications. In its early days, it was missing several important features (like data compression). While that hole has been plugged, there are still other limitations and differences you should be aware o
2024-02-02
Batch Execution Mode on a Rowstore in SQL Server 2022
Batch execution mode is a new optimization feature in SQL Server. In this Article, we'll explore how Batch execution mode works and how you can use it to get faster query results on Rowstore data.
2023-10-30
4,583 reads
The SQL Developer Experience: Beyond RDBMS
Microsoft has built an amazing platform with Azure SQL Database and has recently announced an offer to use this for free. Read about the capabilities and options with this cloud database platform.
2023-10-13
2,872 reads
Exploring Parameter Sensitive Plan Optimization in SQL Server 2022
PSPO (Parameter Sensitive Plan Optimization) is a SQL Server feature that improves query performance by accepting varied data sizes based on the runtime parameter value(s) specified by the customer. It deals with the situation in which a single cached plan for a parameterized query isn't the best option for all potential incoming parameter values. Non-uniform data distributions exhibit this phenomenon. When using PSPO, SQL Server keeps several execution plans for a single query, each one customized for a particular parameter value. With the help of this feature, numerous execution plans for a parameterized query are generated, each of which is tailored for a certain range of parameter values.
2023-07-21
4,558 reads
Database Deployment with Terraform - Modules
Deploy resources in Azure using reusable code with Terraform modules.
2026-02-16 (first published: 2022-10-10)
12,865 reads
Blogs
“We love to debate minutiae”
By Brian Kelley
I am guilty as charged. The quote was in reference to how people argue...
Advice I Like: Knots
By Steve Jones
Learn how to tie a bowline knot. Practice in the dark. With one hand....
Shifting Mindsets: Why FinOps is Essential for Cloud Efficiency
By HeyMo0sh
As a DevOps practitioner, I’ve always focused on performance, scalability, and automation. But as...
Forums
Windows logins for users migrated from DomainA to DomainB
Hi, I have a SQL Server instance where users connect to via Windows Authentication,...
Multiple Deployment Processes
Comments posted to this topic are about the item Multiple Deployment Processes
How to Use sqlpackage to Detect Schema Drift Between Azure SQL Databases
Comments posted to this topic are about the item How to Use sqlpackage to...
Question of the Day
Upgrading Admin Queries
I have a query from a former DBA that we run on SQL Server 2025 to check on database metadata. This query references sys.sysaltfiles. I want to refactor this code to be more modern. Which DMV should I reference instead?
See possible answers