A new neat feature in SQL Server 2012 is THROW
In SQL Server 2005 we got the TRY…CATCH construct which was a big help for developers to effectively handle errors...
2012-05-31
3,340 reads
In SQL Server 2005 we got the TRY…CATCH construct which was a big help for developers to effectively handle errors...
2012-05-31
3,340 reads
How to synchronize the data from the Production environment to Development, Testing and Staging Environments for SQL Server? (Republished)
One of...
2012-05-31
6,567 reads
When asked about how to plan the ideal dev, test, staging and production SQL Server environments it’s easy to get...
2012-05-31
3,844 reads
One of the most common DBA task is to synchronize data to Development, Testing, and Staging environments. Normally this is...
2012-05-23
50 reads
When asked about how to plan the ideal dev, test, staging and production SQL Server environments it’s easy to get...
2012-05-22
24 reads
2010-12-21
3,222 reads
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...
Comments posted to this topic are about the item What is the Cloud?
Comments posted to this topic are about the item Changing the Schema
Comments posted to this topic are about the item Index Fragmentation Explained: Page Splits,...
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