Setting Up Always Encrypted
In this post we're going to go through the steps to set up Always Encrypted and create an encrypted column. As with my last post we're looking at the...
2023-06-06
35 reads
In this post we're going to go through the steps to set up Always Encrypted and create an encrypted column. As with my last post we're looking at the...
2023-06-06
35 reads
At Tuesday 6th of June 2023, I’m giving an online version of my session “Analyzing Azure Cosmos DB Data with Azure Synapse Link” (which I presented at Techorama). It’s...
2023-06-05
22 reads
Unlike TDE, there is some extra CPU overhead when you take an encrypted backup as the data has to be encrypted before being written to disk – whereas with...
2023-06-05 (first published: 2023-05-22)
275 reads
Recently I was doing a cleanup of one model, and I used Best Practice Analyzer (BPA) in Tabular Editor as a helper. Later, I realized I forgot to set...
2023-06-05 (first published: 2023-05-22)
465 reads
jouska – a hypothetical conversation that you compulsively play out in your head – a crisp analysis, a devastating comeback, a cathartic heart-to-heart – which serves as a kind...
2023-06-02
959 reads
The invitation this month for #PGSqlPhriday comes from Dian Fay. The topic is pretty simple, database change management. Now, I may have, once or twice, spoken about database change...
2023-06-02
33 reads
I wrote recently about finding multiple backups in a file. This post looks at how to restore one of those. The one you choose. Another post for me that...
2023-06-02 (first published: 2023-05-17)
216 reads
One of the options that I completely missed with the new go-sqlcmd CLI tool is the ability to spin up a container running SQL Server. Let’s have a look...
2023-06-02 (first published: 2023-05-19)
503 reads
The PASS Data Community Summit is back in Seattle this November, the 14-17, 2023. It’s in person only, and if you can come, you should register today. Launch pricing...
2023-06-01
38 reads
Hello Dear Reader! Sorry this is so late, moving houses has gotten me a bit behind this week. I will do better next week!As you may have heard last...
2023-06-01
56 reads
By Arun Sirpal
Not every production incident is a database in RECOVERY_PENDING or a corrupted event (like...
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,...
Comments posted to this topic are about the item SQL Art, Part 4: Happy...
WhatsApp: 0817839777 Kw. Industri Pulogadung, Jl. Raya Bekasi Km. 21, Ruko No.A2/18-19, RW.3, Wil,...
WhatsApp: 0817839777 Jl. I Gusti Ngurah Rai No.8 A-B, RT.8/RW.6, Wil, Kec. Duren Sawit,...
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