Because
Because there’s nothing else I can do at the moment.
The post Because appeared first on Home Of The Scary DBA.
2016-06-14
533 reads
Because there’s nothing else I can do at the moment.
The post Because appeared first on Home Of The Scary DBA.
2016-06-14
533 reads
Post #6 of #entrylevel #iwanttohelp in support of Tim Ford’s (b|t) beginner’s initiative.
If you’re just getting started with SQL Server,...
2016-06-13
1,244 reads
The question came up, how do the constructs necessary for Elastic Query within Azure SQL Database affect your ability to...
2016-06-13 (first published: 2016-06-06)
2,156 reads
You want to start working with Azure and the Azure Data Platform, but getting started is not easy. Just knowing...
2016-06-10 (first published: 2016-06-02)
1,521 reads
The Azure Data Platform is taking off. I’m seeing more and more interest on the forums, at conferences and in...
2016-06-01
432 reads
While presenting at SQLDay in Wroclaw, Poland, on the Query Store, I was asked a pretty simple question, which takes...
2016-05-31
942 reads
While this is a personal blog, I try to keep it focused on either technical topics or personal development and...
2016-05-25
496 reads
In just a few weeks I’ll be doing the Buckeye Blitz. That is, a tour of user groups in Ohio...
2016-05-24
549 reads
I didn’t post an update last month, but I did do something more important: I elicited your feedback on a question...
2016-05-23
394 reads
I love questions. I recently received one about new plans in the Query Store (available in Azure SQL Database now and in...
2016-05-23 (first published: 2016-05-16)
2,722 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