Deploy Security Changes with Copy-SqlLogin
Moving security changes between server instances can be a cumbersome process, but it doesn't need to be with the PowerShell cmdlet, Copy-SqlLogin.
2016-11-01
2,300 reads
Moving security changes between server instances can be a cumbersome process, but it doesn't need to be with the PowerShell cmdlet, Copy-SqlLogin.
2016-11-01
2,300 reads
2016-10-31
59 reads
The release of Analysis Services in Azure means the platform has a future.
2016-10-31
73 reads
One of the things I struggled with a bit was getting test results to appear in VSTS from my builds....
2016-10-31 (first published: 2016-10-18)
1,001 reads
2016-10-31
1,168 reads
Not all selfies, and not enough, but lots of changes to meet people at the Summit this week.
The other Steve...
2016-10-28
876 reads
2016-10-28
899 reads
Tonight is the #RedgateRocks party at 1927 Events in Seattle. You’ll need to get a wristband from the Redgate Software...
2016-10-27
489 reads
Things at work that waste your time are impediments to actually getting work done. Management ought to be in the business of removing as many of these things as possible.
2016-10-27 (first published: 2012-10-11)
419 reads
2016-10-27
1,000 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