SQLSaturday#71 is only a day away! - Final Schedule....
Just a final note for all of you planning on attending tomorrow's SQL Saturday #71 event extravaganza up in Boston. The event...
2011-04-01
764 reads
Just a final note for all of you planning on attending tomorrow's SQL Saturday #71 event extravaganza up in Boston. The event...
2011-04-01
764 reads
It's March Madness, and we're not just talking about basketball. We're not just talking about Women's History Month, which is...
2011-03-15
2,104 reads
Just wanted to take the opportunity to summarize my experience at SQLSaturday#69 in Philadelphia, this past Saturday. Another city, another amazing event! I haven't been...
2011-03-08
2,374 reads
Jump on the SQLExpress – Useful info, ways to schedule and run maintenance jobs
Sometimes, folks come to me, and ask for...
2011-03-04
5,051 reads
It's just a little less than 2 weeks to SQLSaturday#69 at DeVry University, 1140 Virginia Drive, Ft. Washington, PA 19034...
2011-02-21
871 reads
A Synopsis of My Experiences of the “Intro to SSAS” BI Workshop in NYC!
By Robert Pearl
Well it’s a wrap of...
2011-02-18
1,843 reads
Well, we always see, hear, and read about the list of NEW features in the myriad of articles, columns and blogs...
2011-02-08
1,741 reads
Happy Monday! I'm sure many of you may have already caught on, that Waits & Queues is the way to go...
2011-02-07
714 reads
Don’t let the above title fool you! Have you been confused on the Microsoft SQL Server Licensing requirements? Per Processor, Per CAL, Per Core, Per Socket, Per Node – Per haps (space intended :-), we should revisit the issue again, and try to offer some assistance as you go forward in making your purchasing decisions.
2011-02-04
4,848 reads
BIG in BOSTON
Last time, I blogged about the first upcoming event in the North East in Philadelphia, PA – SQLSaturday#69, but...
2011-02-02
634 reads
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,...
By Tim Radney
As a SQL Server DBA with years of experience tuning production environments, I’ve seen...
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
Comments posted to this topic are about the item Index Fragmentation Explained: Page Splits,...
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