SQL in the City 2013 US Tour
It was a huge honor to be chosen for the 2013 US tour of SQL in the City. Red Gate...
2013-08-30
1,202 reads
It was a huge honor to be chosen for the 2013 US tour of SQL in the City. Red Gate...
2013-08-30
1,202 reads
Recently attempting to install a new three node cluster I ran into a new issue. Once I was able to...
2013-08-28 (first published: 2013-08-21)
1,279 reads
In April 0f 2012 I was fortunate enough to be asked to become Linchpin People LLC’s first ever TeamMate. (blog)....
2013-08-13
838 reads
PASS Summit 2013 will be my fifth Summit to attend. I wrote a blog post about how different my fourth...
2013-08-09
642 reads
I started this post over a year ago and have just now come back around to finish it. Over the...
2013-07-24
657 reads
I have been working on a project recently to collect system metrics of a SQL Server environment. One of the items...
2013-06-27
1,395 reads
Being a production DBA means having to quickly look at a SQL Server and diagnose issue with it. We know...
2013-03-08
4,552 reads
On Thursday March 14th (PI Day) in Duluth GA, Audrey Hammonds and Julie Smith will put on a spectacular SSIS training...
2013-02-12
576 reads
I have been working with a client recently who purchased a nice top of the line de-duplication backup device in...
2013-02-08
1,084 reads
I recieved an email today from my publisher Joes 2 Pros that my book was now available on Barnes and...
2013-02-05
541 reads
With Fabric Mirroring, Microsoft is promoting a nice and appealing story for operational reporting...
If you’ve been watching AI roll through the data community and thinking, “this seems...
By Arun Sirpal
Not every production incident is a database in RECOVERY_PENDING or a corrupted event (like...
Comments posted to this topic are about the item SQL Art, Part 4: Happy...
Because we are NABL Accredited Laboratories, our personal care and cosmetics research center provides...
WhatsApp:0817-866-887 Jl. Ahmad Yani No.31, Pattunuang, Kec. Wajo, Kota Makassar, Sulawesi Selatan 90174 (@bcakcumakassar)
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