SQL Server Time Bombs
Common Reasons for Emergency SQL calls If you are a production DBA (or Accidental prod DBA) you’ve gotten that frantic call in the middle of the night. Or maybe...
2025-03-12 (first published: 2025-02-28)
560 reads
Common Reasons for Emergency SQL calls If you are a production DBA (or Accidental prod DBA) you’ve gotten that frantic call in the middle of the night. Or maybe...
2025-03-12 (first published: 2025-02-28)
560 reads
If you’re an experienced SQL user eager to sharpen your expertise with real-world challenges, the March SQL Practice is the perfect opportunity. This month’s challenge is designed for advanced...
2025-03-11
6,577 reads
This month’s T-SQL Tuesday blog party is hosted by Deborah Melkin, and it’s a good one that asks us where we are making the world better. The topic is...
2025-03-11
6,585 reads
T-SQL Tuesday is a monthly blog party hosted by a different community member each month. This month, Deborah Melkin
(blog) asks us to talk about our relationship with mentoring and...
2025-03-11
22 reads
Howdy folks! Long time no write.
In this post, I will be answering a couple of questions from the previous posts about dropping columns.
A quick refresh
If you haven’t read the...
2025-03-10
4 reads
The AI revolution isn’t coming – it’s here. Companies are racing to integrate artificial intelligence into their operations, eager to unlock efficiency, automation, and data-driven decision-making. But while AI...
2025-03-10 (first published: 2025-02-20)
242 reads
https://sqlsaturday.com/2025-03-08-sqlsaturday1102/#schedule SQL Saturday Atlanta BI is one of my favorite SQL Saturdays of the year. This year was especially sweet to see a lot of the SML (Saturday Morning...
2025-03-10
29 reads
One interesting concept in SQL Server is Deferred Name Resolution. This is something many developers struggle with understanding how this works and where it works. In the Microsoft docs,...
2025-03-10 (first published: 2025-03-03)
439 reads
waldosia– n. a condition in which you keep scanning faces in a crowd looking for a specific person who would have no reason to be there, as if your...
2025-03-07
31 reads
Digital exhaust, or data exhaust, is the information you generate as you interact digitally. We've typically thought of this in terms of tracking cookies and the like, but it...
2025-03-07 (first published: 2025-02-25)
195 reads
By Steve Jones
It’s Prime Day. A few of my recommendations, since I want to do some...
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...
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