SQL Saturday #285 Atlanta
It’s been a couple of months since my last SQLSaturday and it’s time! Atlanta is my third SQL Saturday that I’ll...
2014-02-15
456 reads
It’s been a couple of months since my last SQLSaturday and it’s time! Atlanta is my third SQL Saturday that I’ll...
2014-02-15
456 reads
It’s been a couple of months since my last SQLSaturday and it’s time! Atlanta is my third SQL Saturday that I’ll...
2014-02-15
212 reads
The year of SQL Saturdays!
Tampa is the second SQL Saturday that I’ll be speaking at this year. For the...
2014-02-04
517 reads
The year of SQL Saturdays!
Tampa is the second SQL Saturday that I’ll be speaking at this year. For the...
2014-02-04
222 reads
SSDT 2010, 2012 with TFS integration brought about a couple of different options when you are looking to version your...
2014-01-30
2,061 reads
So by now this is no longer a new issue and not too difficult to find a fix for. However,...
2014-01-16
530 reads
SQLSaturday #272 Nashville here I come! Looking forward to having an opportunity to speak and network in Nashville. I am...
2014-01-11
354 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