Moving Encrypted Data to Azure SQL Database
Learn how you can move encrypted data from on premises SQL Server to Azure SQL Database.
2019-11-26
2,506 reads
Learn how you can move encrypted data from on premises SQL Server to Azure SQL Database.
2019-11-26
2,506 reads
Azure SQL Database can be patched without stopping the sqlsrvr.exe process. Quite a feat of engineering.
2019-10-08
189 reads
2019-08-15
755 reads
Cross database queries in Azure SQL Database aren't as straightforward as you might think, but they aren't hard to implement. Follow along to learn how to implement them.
2019-07-25
38,212 reads
The technologies that we see in other data platform products sometimes flow to SQL Server.
2019-06-20
257 reads
2019-05-16
584 reads
There are currently three deployment options for SQL Server Database on the cloud. Well, four, if you count Azure SQL Databases in elastic pool. But Azure SQL DB in...
2019-05-09
On Thursday 2 May 2019, Microsoft announced a new edition of SQL Server, targeting Internet of Things (IoT) edge devices. That means SQL Server can now run almost anywhere....
The...
2019-05-06
2019-04-29
746 reads
I have been using Terraform for the last week or so to create some infrastructure and decided to bring that knowledge back to a problem that I and others...
2019-04-17
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,...
By Tim Radney
As a SQL Server DBA with years of experience tuning production environments, I’ve seen...
Wa:0817781222 Jl. Otto Iskandardinata No.37, Karanganyar, Kec. Subang, Kabupaten Subang, Jawa Barat 41211
Wa:0817781222 Jl. Ir. H. Juanda No.118, Lebakgede, Kecamatan Coblong, Kota Bandung, Jawa Barat 40132
Wa:0817781222 Jl. Ahmad Yani No.9, RT.01/RW.05, Marga Jaya, Kec. Bekasi Sel., Kota Bks, Jawa...
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