What’s new in SQL Server 2025 CTP 2.0
Three years ago, when the first public preview of SQL Server 2022 (CTP 2.0) was announced, I was a few months in at the SQL Docs team, and had...
2025-05-23 (first published: 2025-05-19)
571 reads
Three years ago, when the first public preview of SQL Server 2022 (CTP 2.0) was announced, I was a few months in at the SQL Docs team, and had...
2025-05-23 (first published: 2025-05-19)
571 reads
I recently was privileged to speak at SQLDay in Wroclaw Poland… man, I love visiting Poland… Anyway… Great event. Worth your time to attend, and if you’re a speaker,...
2025-05-22
46 reads
Once again there were a number of Microsoft Build announcements related to data and AI, and some were very impressive. Below are my favorites. Everything announced at Build can...
2025-05-22
50 reads
You know I had to do it as soon as I found it was possible. Yes, I installed and enabled AI in the DBeaver Query Editor so I can...
2025-05-21 (first published: 2025-05-05)
261 reads
I had a suggestion from somone on a place where AI helps them and I decided to try it. The person had an AI summarize their work and if...
2025-05-21
31 reads
Disclaimer: this post is not sponsored by Redgate 🙂 For those who’ve missed it, the new version of SSMS is now generally available. It’s a big new version and...
2025-05-21
8,355 reads
I’m hosting T-SQL Tuesday this month and our topic is Managing SQL Agent Jobs. In this post, we’ll be taking a look at a very handy combination of dbatools...
2025-05-21 (first published: 2025-05-13)
411 reads
This Friday is the NYC DevOps Devour hour, which is actually 3 hours. Plus a happy hour. I’ll be there with Kendra Little and Erik Darling talking about DevOps...
2025-05-20
25 reads
Ollama SQL FastStart streamlines the deployment of SQL Server 2025 with integrated AI capabilities through a comprehensive Docker-based solution. This project delivers a production-ready environment combining SQL Server 2025,...
2025-05-19
53 reads
Redgate Monitor works with more than SQL Server. Some big changes were announced recently, and I’ll cover the highlights here. This post looks at Redgate Monitor and the additional...
2025-05-19
37 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