MVP No more, But It’s OK
Embracing Limitations: Finding Strength and Purpose in Hard Times For four years, I was honored to receive the MVP award for my work in the
The post MVP No more,...
2024-07-26 (first published: 2024-07-12)
435 reads
Embracing Limitations: Finding Strength and Purpose in Hard Times For four years, I was honored to receive the MVP award for my work in the
The post MVP No more,...
2024-07-26 (first published: 2024-07-12)
435 reads
I almost missed this month, so this is also a good #SQLNewBlogger post. I thought about it for a few minutes as I ate breakfast at my desk and...
2024-07-26 (first published: 2024-07-09)
298 reads
Whether it's "Made with love and WordPress" or "Bob Ross rocks," you can now customize footer credits on your website.
2024-07-24
15 reads
As a Software Engineer, I would like to replicate a copy of my database from on-premise infrastructure to AWS. This will require me to look for a perfect tool...
2024-07-24 (first published: 2024-07-20)
373 reads
This month’s T-SQL Tuesday is hosted by a dear friend, long time SQL Server MVP and book author – Louis Davidson. Louis’s call is for us to blog about...
2024-07-24 (first published: 2024-07-09)
272 reads
The world runs on data, and SQL is the key to unlocking its secrets. If you're ready to level up your SQL game, online training is a power move....
2024-07-23
325 reads
External REST endpoint invocation in Azure SQL DB went GA in August 2023. Whereas before, we might have needed an intermediate technology to make a REST call to an...
2024-07-23
21 reads
External REST endpoint invocation in Azure SQL DB went GA in August 2023. Whereas before, we might have needed an intermediate technology to make a REST call to an...
2024-07-23
9 reads
External REST endpoint invocation in Azure SQL DB went GA in August 2023. Whereas before, we might have needed an intermediate technology to make a REST call to an...
2024-07-23
85 reads
I’m headed back to Wisconsin Dells next week for THAT! Conference 2024. This is my second time in Wisconsin and third THAT overall. This time I didn’t submit, but...
2024-07-23
23 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...
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