Presenting at SQLSaturday #16
I’ll be attending SQLSaturday #16 in South Florida on August 8th and doing two presentations, one on statistics and one...
2009-07-13
331 reads
I’ll be attending SQLSaturday #16 in South Florida on August 8th and doing two presentations, one on statistics and one...
2009-07-13
331 reads
I finished up reading Traffic: Why We Drive the Way We Do by Tom Vanderbilt last week and enjoyed it....
2009-07-10
375 reads
Part 2 of MVP Andy Warren's SQL School video on Instead of Triggers.
2009-07-09
5,254 reads
I was having a discussion with Brian Knight yesterday about whitepapers and thought I’d share some of it – from my...
2009-07-09
436 reads
If you haven’t seen the news yet we’ve got something new on the schedule this year – a 2 hour seminar...
2009-07-08
570 reads
If you have never used an instead of trigger, it's a great mechanism for evading table triggers in certain situations. MVP Andy Warren brings you part one of this SQL School video.
2009-07-07
7,526 reads
Russ Fustino from Microsoft just sent me the link to episode #3 that was filmed at SQLSaturday #14 in Pensacola....
2009-07-06
485 reads
Since the beginning of SQLSaturday I’ve covered most of the news here on my blog, beginning this week I’ll be...
2009-07-06
464 reads
Read the Declaration of Independence and then it’s time for fireworks and grilling, maybe some apple pie too!
2009-07-03
504 reads
Rolling Thunder ($7.99 @ Amazon) by John Varley is the third book in the series. I previously reviewed Red Thunder and...
2009-07-02
710 reads
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...
It is Friday, the queries are running, and nobody is watching the bill. That...
Comments posted to this topic are about the item SQL Art, Part 4: Happy...
Hi All I am trying to find 'bad' characters that users might type in....
Comments posted to this topic are about the item Extreme DAX: Take your Power...
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