Daily Coping 15 Feb 2023
Today’s coping tip is to look for good in others, particularly when you feel frustrated. We all deal with conflicts with others throughout out lives. How we handle those...
2023-02-15
25 reads
Today’s coping tip is to look for good in others, particularly when you feel frustrated. We all deal with conflicts with others throughout out lives. How we handle those...
2023-02-15
25 reads
For the first workdays of this new year, I had the pleasurable task of resetting a bunch of passwords. The passwords belong to Azure AD users, service principals, SQL...
2023-02-15 (first published: 2023-02-01)
523 reads
When working in business intelligence, data engineering or data in general, there are some “mantras” that are being adopted by the larger community as “best practices”. For example, I...
2023-02-14 (first published: 2023-02-13)
45 reads
Today’s coping tip is to thank someone and tell them how they made a difference for you. I’ve had a lot of success in my life, as well as...
2023-02-14
14 reads
I’m excited to announce I’ve been selected again as a speaker for Techorama 2023. Techorama is one of the biggest Microsoft-focused events in the European mainland, and it’s always...
2023-02-14
24 reads
Today’s coping tip is to show an active interest by asking questions when talking to others. I listen more and more these days. I’m trying to input less and...
2023-02-13
18 reads
The question came up that someone wanted to monitor the queries impacting tempdb using Extended Events. Initially, I was pretty sure that there was no real way to do...
2023-02-13
30 reads
Hello Dear Reader! We had a great last week on Tales from the Field. This weekend was also a really nice one. On Saturday a group of friends gathered...
2023-02-13
32 reads
Tempdb is always a topic for me whether it’s in my sessions or blogs I have written. However, I’ve never been so excited about it then I am when...
2023-02-13 (first published: 2023-02-01)
2,854 reads
Today’s coping tip is to send a message to let someone know you’re thinking of them. I reached out a friend the other day, someone I know from the...
2023-02-10
30 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