Daily Coping 31 Jan 2023
Today’s coping tip is to take a small step towards and important goal. One of my goals this year was to work on a way to score myself with...
2023-01-31
8 reads
Today’s coping tip is to take a small step towards and important goal. One of my goals this year was to work on a way to score myself with...
2023-01-31
8 reads
In a previous post, I set up the basic databases for the PoC project I’m working on. In this next post, we’ll get the Flyway Desktop projects set up...
2023-01-31 (first published: 2023-01-30)
32 reads
Hello Dear Reader! It's been a while since I had time to sit down and write out a Monday re-capThis past week was my birthday week. With all the...
2023-01-31
23 reads
Today’s coping tip is to plan something fun and invite others to join you. The fun thing is actually skiing today. My wife and I wanted to get some...
2023-01-30
15 reads
EightKB is back! The biggest online SQL Server internals conference is back in 2023…happening on May 24th. We’ve open our call for speakers, you can submit here: – https://sessionize.com/eightkb-may-2023/...
2023-01-30 (first published: 2023-01-23)
163 reads
I have a Logic App that reads out a SharePoint library and stores all the documents found into Azure Blob Storage (ADF only supports Lists). I was trying to...
2023-01-30 (first published: 2023-01-18)
80 reads
When encrypting a database with Transparent Data Encryption (TDE), a vital consideration is to make sure we are prepared for the scenario where something goes wrong. For instance, if...
2023-01-30
26 reads
Over the last year, at work and after work, I’ve been teaching myself a lot of brand new technologies. As such, I’m reliant on others to have put together...
2023-01-30
19 reads
My new course “Securing Azure Kubernetes Service (AKS) Clusters”, co-authored with my good friend and colleague Ben E. Weissman, is now available on Pluralsight here! If you want to...
2023-01-28
27 reads
Today’s coping tip is to try something new to get out of your comfort zone. I did two things here. First, I’ve been participating in a Jan American Cancer...
2023-01-27
17 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