Azure SQL Database – A Copying “Gotcha”
Creating copies of your Azure SQL Database is a common and relatively simple process. You can issue a TSQL statement...
2018-04-24
360 reads
Creating copies of your Azure SQL Database is a common and relatively simple process. You can issue a TSQL statement...
2018-04-24
360 reads
vCore based performance levels are very new, currently in preview and not yet rolled out to all Azure regions (The...
2018-04-24 (first published: 2018-04-16)
2,375 reads
I have come to understand the importance of using columnstore indexes when my queries are aggregating and scanning across many...
2018-04-19 (first published: 2018-04-09)
2,241 reads
If I was a wizard I would make these 4 improvements to Azure SQL Database. They are in no particular...
2018-04-12 (first published: 2018-04-05)
2,191 reads
Initially, the main focus of this post was going to be quick and about using the latest version of SSMS...
2018-04-12
881 reads
After demo building and testing features out within Azure SQL Database I like to delete the databases to save costs....
2018-04-03
372 reads
I was looking forward to do some work with Azure SQL Data Warehouse (DWH) when I hit the new query...
2018-04-03 (first published: 2018-03-27)
3,464 reads
We all know that the magic figure for cost threshold for parallelism is 5 by default, meaning if the estimated...
2018-03-26 (first published: 2018-03-16)
2,331 reads
I have decided to do a summary blog post on backup and recovery options for Azure SQL Database. If you...
2018-03-26
580 reads
Back in September 2017 Microsoft announced a new security feature for Azure SQL Database called the SQL Vulnerability Assessment (VA)....
2018-03-22
1,006 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 SQL Art, Part 4: Happy...
WhatsApp: 0817839777 Kw. Industri Pulogadung, Jl. Raya Bekasi Km. 21, Ruko No.A2/18-19, RW.3, Wil,...
WhatsApp: 0817839777 Jl. I Gusti Ngurah Rai No.8 A-B, RT.8/RW.6, Wil, Kec. Duren Sawit,...
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