SSIS Catalog Compare v2.0 Launch Event
Join the SSIS Catalog Compare v2.0 Launch Event on Tue, Mar 7 at 13:00 EST.
Join the SSIS Catalog Compare v2.0 Launch Event on Tue, Mar 7 at 13:00 EST.
Containers are valuable in many software domains. Are there places we, as data professionals, would like to use software containment?
If a successful IT career is just as much about tenacity, interest and retention as it is about brainpower, then how does one go about continuous learning?
No worries about dropping databases. Now we can search for its dependencies before the database dies. Part 1 of a 2-part article.
The SQL Server Luxembourg User Group invites you to join us at our next event in Microsoft’s Offices, at 6:00pm on Tuesday 7th March
Greg Larsen explains how you can use Dynamic Management Objects and stored procedures to return your worst performing T-SQL statements.
An open letter to Microsoft from the CEO of Mandriva Linux might not have been the best idea.
Today Steve Jones asks what default values you might choose for new columns in a table.
This article exlores the usage of CTEs as a replacement to cursors in order to generate additional data by applying logic to existing data.
Bhavesh Patel shows how to clone a SQL Server login onto another server while keeping the password the same.
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