AgentDBA vs Critical SQL Server
It’s 07:43. Someone’s already left a message. “Something’s wrong with the DB server.” You open the terminal and go to work. This post is about what happens next —...
2026-06-16
109 reads
It’s 07:43. Someone’s already left a message. “Something’s wrong with the DB server.” You open the terminal and go to work. This post is about what happens next —...
2026-06-16
109 reads
Fourth in a series on Ai and databases. What Read-Only Advisory Actually Means A read-only advisory system does exactly two things: it observes and it recommends. It never acts....
2026-06-11
29 reads
Third part in my Ai series with databases. When building AI solutions within the database realm the first thing that people do is a straightforward concept, connect the LLM...
2026-06-09
158 reads
Second in a series on Ai and databases. One Story, three signals – I have a backup of a critical database that has failed three times, the recovery point...
2026-06-05 (first published: 2026-06-04)
29 reads
As part of my wider work exploring Claude Code and AI-assisted database engineering, I have been looking at how AI can support SQL Server operations. A failed job, missed...
2026-06-03 (first published: 2026-05-17)
503 reads
Every Claude conversation has a context window. It is the total amount of text Claude can work with in a single chat — your messages, its replies, uploaded files,...
2026-05-30 (first published: 2026-05-29)
25 reads
Claude is more than a chat window. The desktop experience includes structured workspaces, generated outputs, integrations, execution capabilities, memory and reusable workflows. This is a quick introduction to some...
2026-05-26
22 reads
You have used Claude. But which Claude? The Claude app (claude.ai, the desktop and mobile apps) is the chat product you talk to. The Claude API is the developer...
2026-05-25 (first published: 2026-05-13)
364 reads
Every major model out there can summarise documents, write code and answer multi step questions – then if you decide to go with a specific vendor based on costs...
2026-05-18 (first published: 2026-05-04)
921 reads
For those entering the AI space whether professionally or personally I wanted to give a quick overview on the different models on offer within the Claude family – when...
2026-05-06 (first published: 2026-04-27)
376 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