AI in the DBeaver Query Editor
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
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,349 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
I was lucky enough to attend SQL Saturday Austin 2025 a little over a week ago in conjunction with some work at the Redgate office. The opening keynote at...
2025-05-19 (first published: 2025-05-12)
959 reads
pg_cron is a simple cron-based job scheduler for PostgreSQL that runs inside the database as an extension. It allows you to schedule PostgreSQL commands directly from your database, similar...
2025-05-19 (first published: 2025-04-24)
387 reads
On May 8, 2025, we hosted our first official event in Switzerland at Prime Tower, Zurich. The gathering marked an important step in our journey to support organizations as...
2025-05-16 (first published: 2025-05-15)
33 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