Learning from Mistakes: T-SQL Tuesday #194
We’re a week late, once again my fault. I was still coming out of the holidays and forgot to check on my host. Luckily, Louis Davidson (who did have...
2026-01-21 (first published: 2026-01-20)
57 reads
We’re a week late, once again my fault. I was still coming out of the holidays and forgot to check on my host. Luckily, Louis Davidson (who did have...
2026-01-21 (first published: 2026-01-20)
57 reads
End-to-end NVMe vs PVSCSI testing over NVMe/TCP to a Pure Storage FlashArray: TPC-C and DiskSpd results and analysis.
2026-01-21 (first published: 2026-01-07)
276 reads
I ran across this article recently (https://www.gatesnotes.com/meet-bill/source-code/reader/microsoft-original-source-code) and it has a great opening piece of ASCII Art. I have a screenshot here: For some reason, I thought, “I should...
2026-01-20 (first published: 2026-01-19)
26 reads
A customer was asking about what certain items in Redgate Monitor mean. They have a variety of skills on their staff, and they have developers accessing Redgate Monitor. This...
2026-01-19 (first published: 2026-01-05)
235 reads
2026-01-19 (first published: 2026-01-08)
227 reads
I’m in the UK today, having arrived this morning in London. Hopefully, by this time ,I’m in Cambridge and at the Redgate office. Maybe sitting in the foyer alcove,...
2026-01-19
15 reads
Somehow two years have elapsed since my last update; hopefully it won’t be that long before the next one. My last post was about SQLSaturday Orlando 2023. Since then,...
2026-01-16 (first published: 2026-01-03)
182 reads
AI is a big deal in 2026, and at Redgate, we’re experimenting with how AI can help developers and DBAs become better at their jobs. One of the areas...
2026-01-16
41 reads
Another of our values: The facing page has this quote: “We admire people who get stuff done. While there’s a place for planning, thinking and process it is better...
2026-01-16
18 reads
I was looking back at my year and decided to see if SQL Prompt could help me with some analysis. I was pleasantly surprised by how this went. This...
2026-01-16 (first published: 2025-12-31)
323 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