Why Log Shipping is Better than Database Mirroring for Migrations
This topic has come up several times recently, so I feel the need to blog on it. As the person...
2017-05-05
1,137 reads
This topic has come up several times recently, so I feel the need to blog on it. As the person...
2017-05-05
1,137 reads
Thanks to everyone who attended my presentation for the 24 Hours of PASS event on May 3rd. This iteration of...
2017-05-04
723 reads
A small but nice little feature I have been using recently can be found within Query Store. Let’s say you...
2017-05-04
315 reads
7th Interview of #DataChannel is out 🙂
Very happy to have Mr.Steve Knutson, office servers and SharePoint MVP, share his knowledge...
2017-05-04
425 reads
Another post for me that is simple and hopefully serves as an example for people trying to get blogging as...
2017-05-04
793 reads
Last week Microsoft confirmed that the name of SQL vNext will indeed be SQL Server 2017. I was looking through...
2017-05-04 (first published: 2017-04-26)
2,584 reads
I like scripts. Scripts that help me do things.
Working in the financial industry, there are always things that you have...
2017-05-04 (first published: 2017-04-25)
1,471 reads
It’s been too quiet on this blog this year, especially with all the awesome things going on in the SQL PowerShell world! It’s all my fault I’ve been spending...
2017-05-04
19 reads
It’s been too quiet on this blog this year, especially with all the awesome things going on in the SQL PowerShell world! It’s all my fault I’ve been spending...
2017-05-04
14 reads
It’s been too quiet on this blog this year, especially with all the awesome things going on in the SQL PowerShell world! It’s all my fault I’ve been spending...
2017-05-04
2 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...
WhatsApp:0817-866-887 Jl. Ahmad Yani No.31, Pattunuang, Kec. Wajo, Kota Makassar, Sulawesi Selatan 90174 (@bcakcumakassar)
Hi All I am trying to find 'bad' characters that users might type in....
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