Daily Coping 6 Jul 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-07-06
22 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-07-06
22 reads
I was recently asked what permissions were needed to force plans in query store. I’m sure I knew at one point, but at the moment I was asked, I...
2021-07-06
9 reads
I was recently asked what permissions were needed to force plans in query store. I’m sure I knew at one point, but at the moment I was asked, I...
2021-07-06
158 reads
Welcome back to the series “Server Review Essentials for Accidental and Junior DBAs.” So far in this series we’ve taken a look at how to set up your work...
2021-07-06
40 reads
I was speaking with one of my favorite people in the SQL Server community, Grant Fritchey (blog|twitter), on twitter today. ... Continue reading
2021-07-06
102 reads
Being heavily involved with Microsoft Azure and database technologies it was only a matter of time that I would enter the world of Azure Container Instances (ACI). The same...
2021-07-05
40 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-07-05
22 reads
In my last post I talked about reasons why your permissions might go missing. One of the reasons, and in ... Continue reading
2021-07-05 (first published: 2021-06-24)
239 reads
In the last few posts, I’ve written about using the SQL Compare command line for a specific object and shown how to get a report. This post will look...
2021-07-05
56 reads
After a very long work, a new version of www.SQLpassion.at was deployed last Thursday. It includes a brand-new corporate design, which is much more modern than the older version....
2021-07-05
13 reads
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...
By Arun Sirpal
Not every production incident is a database in RECOVERY_PENDING or a corrupted event (like...
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