Daily Coping 22 Nov 2021
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-11-22
17 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-11-22
17 reads
Hello and welcome back… It has been a few months since I have published a blog post. More like 126 days, to be exact. Unfortunately, I have been dealing...
2021-11-22 (first published: 2021-11-16)
661 reads
If you have been following me for a while you will know that I really like the Fail over groups within Azure SQL DB and it is no different...
2021-11-22
26 reads
Another post for me that is simple and hopefully serves as an example for people trying to get blogging as #SQLNewBloggers. In every language I’ve coded in, there is...
2021-11-22
99 reads
SQL Server 2022 is still in private preview (Microsoft MVP folks have access to it), but you can now read about the new release before it is released: SQL...
2021-11-22
3 reads
SQL Server 2022 is still in private preview (Microsoft MVP folks have access to it), but you can now read about the new release before it is released: SQL...
2021-11-22
192 reads
I noticed the docs for STRING_SPLIT now show that there is a third parameter. This brings us an ordinal for the positioning of the data. The format is now:...
2021-11-22 (first published: 2021-11-17)
1,609 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-11-19
49 reads
If you’d asked me 5 years ago if I would ever speak at Summit, I’d have said “no way, not possible.” I didn’t even think I was able to...
2021-11-19
10 reads
I attended the three main days this year and wrote notes as I went. As I sat down to type them up I started by going back to look...
2021-11-19 (first published: 2021-11-14)
338 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