Remote Work
This is going to be the first time I’m working remotely today in over a year. I’m in Omaha, and while I’ve gone to a few cities, I haven’t...
2021-04-30
12 reads
This is going to be the first time I’m working remotely today in over a year. I’m in Omaha, and while I’ve gone to a few cities, I haven’t...
2021-04-30
12 reads
I started to add a daily coping tip to the SQLServerCentral newsletter and to the Community Circle, which is helping me deal with the issues in the world. I’m...
2021-04-29
11 reads
This is another in a group of several posts on modernizing T-SQL code with new features and functionality available in SQL Server. SQL Server 2016 gave us the STRING_SPLIT()...
2021-04-29 (first published: 2020-02-18)
1,240 reads
Disclaimer: The title is my assumption because I saw it in the past happening this way. This blog post aims to make you remember something: something that is obvious...
2021-04-29 (first published: 2020-02-21)
1,280 reads
Next Friday WITDC is having a Mental Health and Wellness Day virtual event and I’ll be speaking! I can’t tell ... Continue reading
2021-04-29
32 reads
My last post had a lot of information about the new .NET PowerShell notebooks including installation instructions. .NET Notebooks are Jupyter Notebooks that use .NET core to enable C#,...
2021-04-28 (first published: 2020-02-22)
261 reads
This series looks at the Advent of Code challenges. As one of my goals, I’m working through challenges. This post looks at day 4. I’m going to do this...
2021-04-28
18 reads
There comes a time when we heed a certain call. The call is to avoid dangerous undocumented DBCC commands in SQL Server, especially those that bypass built-in protections. I’m...
2021-04-28
16 reads
I started to add a daily coping tip to the SQLServerCentral newsletter and to the Community Circle, which is helping me deal with the issues in the world. I’m...
2021-04-28
7 reads
As I wrote last month, I went through a period of feeling personally and professionally deadlocked, and flailed about for some time before I found the answer of making...
2021-04-28 (first published: 2020-02-21)
383 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