Assigning a Default Schema to a New User–#SQLNewBlogger
I had to test something for a customer, and as a part of this there as a need to have a different default schema for a user. Since this...
2023-07-31 (first published: 2023-07-12)
284 reads
I had to test something for a customer, and as a part of this there as a need to have a different default schema for a user. Since this...
2023-07-31 (first published: 2023-07-12)
284 reads
fitzcaraldo – n. a random image that becomes lodged deep in your brain – maybe washed there by a dream, or smuggled inside a book, or planted during a...
2023-07-28
28 reads
Earlier this week the emails went out to speakers who submitted to the PASS Data Community Summit 2023 conference. These were acceptances and rejections, letting people know the results...
2023-07-28 (first published: 2023-07-13)
155 reads
I was having a conversation with some friends the other day and Jen McCown (blog|twitter) asked about SQL Server security ... Continue reading
2023-07-28 (first published: 2023-07-13)
314 reads
I stopped blogging late last year. I’ll be honest, I was tired. I had decided to take a month or ... Continue reading
2023-07-27
38 reads
It’s been a while, but I’m finally participating in T-SQL Tuesday again! This month Erik Darling (blog|twitter) is hosting. Ever ... Continue reading
2023-07-26 (first published: 2023-07-11)
366 reads
The invitation this month is from Erik Darling, and it’s a neat one. I like this thought, asking us to find code that impressed us or made us feel...
2023-07-26 (first published: 2023-07-11)
448 reads
Good morning dear reader, Long time no talk. It has been a jam-packed and chaotic first half of 2023 for my family and me. The first quarter of the...
2023-07-25
55 reads
Pain Point: Something bad happened and you need to restore a SQL Server database. Pain Point you didn’t know you had: The backup files are all corrupt due a...
2023-07-25
308 reads
Actually, this is a change for many products and software that connects to SQL Server. Updated drivers require us to now decide to trust the server certificate. I opened...
2023-07-24
132 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