Daily Coping 25 Jun 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-06-25
21 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-06-25
21 reads
Man does not live by work alone. Everyone needs a hobby, preferably in isolation from their daily work. There is not much to read in this post. As a...
2021-06-25
25 reads
For Pride this year, we’re highlighting queer nonprofits and charities. It’s more important than ever to support the queer community and raise awareness for those who do so all...
2021-06-25 (first published: 2021-06-15)
130 reads
I got a speaking rejection today. Well, not today, but the day I wrote this. Not really a big deal, but it was interesting that the event organizer included...
2021-06-25
39 reads
A customer recently was concerned about the time to run SQL Compare for a large database. They were synching with the command line, but at times they want to...
2021-06-25 (first published: 2021-06-11)
432 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-06-24
15 reads
Looking forward to speaking at Data ANZ 2021 this weekend. Data ANZ "is the data community event for the whole of Australia and New Zealand (and the world)"!
I'll be presenting...
2021-06-24
14 reads
It has been some time since I last wrote about Azure SQL Database. Although it has been more than three years since SQL Server 2017 was released, Microsoft have...
2021-06-23
60 reads
(2021-Jun-16) Recently, Google started to notify me that my blog website (http://datanrg.blogspot.com/) had been experiencing some ‘Server (5xx)’ errors. Nothing has been changed on my side, and I’m not sure how...
2021-06-23 (first published: 2021-06-16)
757 reads
Just a really quick FYI for the readers. If you are using Managed Instances in Azure (If not, why not?) and you connect vis SSMS (SQL Server Management Studio)...
2021-06-23
354 reads
By Steve Jones
It’s Prime Day. A few of my recommendations, since I want to do some...
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...
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