What's Your Test Plan?
This week Steve Jones looks at the formal way in which you might verify changes to your system. Do you have a process?
2016-05-20
235 reads
This week Steve Jones looks at the formal way in which you might verify changes to your system. Do you have a process?
2016-05-20
235 reads
Branching code creates complexity to development and should be undertaken with caution.
2016-05-19
94 reads
Steve Jones notes that some features aren't fully developed, but that's not a reason to avoid releasing them.
2016-05-17
159 reads
2016-05-17
1,410 reads
Adding a release management tool to your software development is a sign of maturity.
2016-05-16
71 reads
The next version of SQL Server 2016 will be released on June 1, 2016, which means you can start planning those upgrades.
2016-05-16
107 reads
2016-05-16
1,084 reads
Redgate recently released SQL Monitor 5.2, which is the latest upgrade to our monitoring/alerting/troubleshooting product for DBAs. This was the...
2016-05-13
696 reads
2016-05-13
85 reads
2016-05-13
1,868 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