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
2,868 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,520 reads
Serverless Gets Faster
In Azure SQL Database serverless edition, we get an upgrade to our configuration.
2024-10-12
113 reads
2024-03-29
7,843 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,602 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,260 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,850 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,228 reads
Database Deployment with Terraform - Modules
Deploy resources in Azure using reusable code with Terraform modules.
2022-10-10
11,597 reads
Blogs
From Data Custodian to Innovation Catalyst: The Evolving Role of the CDO
By Chris Yates
There was a time when the Chief Data Officer lived in the shadows of...
Down the Rabbit Hole: Dealing with Ad-Hoc Data Requests
By Rayis Imayev
"But I don’t want to go among mad people," Alice remarked."Oh, you can’t help...
Adding a Local Model to Ollama through the GUI
By Steve Jones
I saw some good reviews of the small gemma3 model in a few places...
Forums
Create an HTML Report on the Status of SQL Server Agent Jobs
Comments posted to this topic are about the item Create an HTML Report on...
We Should Demand Better
Comments posted to this topic are about the item We Should Demand Better
Estimated Rows
Comments posted to this topic are about the item Estimated Rows
Question of the Day
Estimated Rows
I have two calls to the GENERATE_SERIES TVF in this code:
SELECT TOP 10 gs.value FROM GENERATE_SERIES(1, 10) AS gs ORDER BY NEWID () OPTION (RECOMPILE); go DECLARE @a int = 10; SELECT TOP (@a) gs.value FROM GENERATE_SERIES(1, @a) AS gs ORDER BY NEWID () OPTION (RECOMPILE);In the actual query plans, what is the estimated number of rows for each batch? See possible answers