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
4,373 reads
In Level 1 of the Stairway to Azure SQL Hyperscale, we learn about the architecture and create a hyperscale instance.
2025-09-03
4,373 reads
This guide will walk you through the process of deploy DACPAC to Azure SQL database directly from Visual Studio.
2025-03-10
1,761 reads
In Azure SQL Database serverless edition, we get an upgrade to our configuration.
2024-10-12
134 reads
2024-03-29
9,058 reads
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,749 reads
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 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,771 reads
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,894 reads
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,701 reads
Deploy resources in Azure using reusable code with Terraform modules.
2026-02-16 (first published: 2022-10-10)
13,044 reads
By Arun Sirpal
Not every production incident is a database in RECOVERY_PENDING or a corrupted event (like...
It is Friday, the queries are running, and nobody is watching the bill. That...
By Steve Jones
Annabel retired from Redgate Software this week. Across most of my career at Redgate,...
Comments posted to this topic are about the item Extreme DAX: Take your Power...
Comments posted to this topic are about the item What is the Cloud?
Comments posted to this topic are about the item Changing the Schema
I set up a few users on my SQL Server 2022 instance.
CREATE LOGIN User1 WITH PASSWORD = 'Demo12#1' CREATE USER User1 FOR LOGIN User1 GO CREATE LOGIN User2 WITH PASSWORD = 'Demo12#2' CREATE USER User2 FOR LOGIN User2 GO CREATE LOGIN User3 WITH PASSWORD = 'Demo12#3' CREATE USER User3 FOR LOGIN User3 GOI then created a schema that one of them owned. Under this schema, I added a table with some data.
CREATE SCHEMA MySchema AUTHORIZATION User1
GO
CREATE TABLE Myschema.MyTable(myid INT)
GO
INSERT MySchema.MyTable
(
myid
)
VALUES
(1), (2), (3)
GO
SELECT * FROM MySchema.MyTable
GO
I granted rights and verified that User2 could access this table.
GRANT SELECT ON Myschema.MyTable TO User2 GO SETUSER 'USER2' GO SELECT * FROM MySchema.MyTable GOThis worked. Now, I move this schema to a new user.
ALTER AUTHORIZATION ON SCHEMA::Myschema TO User3; GOWhat happens with this code?
SETUSER 'USER2' GO SELECT * FROM MySchema.MyTable GOSee possible answers