Determining Default Trace Location
While working on some scripts against SQL Server’s default trace, I wanted to develop a sure fire way to find...
2013-01-09
1,814 reads
While working on some scripts against SQL Server’s default trace, I wanted to develop a sure fire way to find...
2013-01-09
1,814 reads
In the past couple weeks, I’ve gotten a couple reports of issues with sp_indexanalysis. The update today fixes those issues....
2013-01-08
756 reads
It’s been a while since I mentioned anything about the SQL Saturday in Fargo. So I thought I would let...
2013-01-08
579 reads
Today is the first Monday of 2013. Do you know if your servers are ready to take on the first...
2013-01-07
684 reads
Throughout the week, I like to tweet links to the things that I’ve been reading. Since they all come out through out...
2013-01-07
909 reads
Welcome to this Friday’s reblog summary post. The aim of these posts is to bring some old posts that newer...
2013-01-04
1,040 reads
Throughout the week, I like to tweet links to the things that I’ve been reading. Since they all come out through out...
2012-12-31
1,731 reads
Last year, I did a wrap up post of the year to see where I landed from where I wanted...
2012-12-31
1,631 reads
Last week I mentioned that I had put up a few new versions of my index analysis script. Turns out...
2012-12-28
706 reads
Last week, I presented on extended events at the Minnesota SQL Server user group (PASSMN). The turnout was quite excellent...
2012-12-28
742 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