Last Weeks Top 10 “Reading” Links #10
Throughout the week, I like to tweet links to the things that I’ve been reading. Since they all come out through out...
2012-12-10
766 reads
Throughout the week, I like to tweet links to the things that I’ve been reading. Since they all come out through out...
2012-12-10
766 reads
Welcome to this Friday’s reblog summary post. The aim of these posts is to bring some old posts that newer...
2012-12-07
739 reads
This post is part of a blog series which focuses on translating compatibility views in SQL Server to their respective...
2012-12-06
1,547 reads
In a previous post, there was a comparison between sysperfinfo and sys.dm_os_performance_counters which included the use of a simple query. ...
2012-12-06 (first published: 2012-11-27)
6,835 reads
Since it’s been a while since I made any real changes to the design of this blog, it was time...
2012-12-05
735 reads
Throughout the week, I like to tweet links to the things that I’ve been reading. Since they all come out through out...
2012-12-03
1,020 reads
This post is part of a blog series which focuses on translating compatibility views in SQL Server to their respective...
2012-12-03
2,104 reads
Did you know that a SQL Saturday in Fargo is in the works? If not them, hey… there’s a SQL...
2012-11-30 (first published: 2012-11-26)
1,180 reads
This post is part of a blog series which focuses on translating compatibility views in SQL Server to their respective...
2012-11-30
1,824 reads
Welcome to this Friday’s reblog summary post. The aim of these posts is to bring some old posts that newer...
2012-11-30
1,487 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