SQL Saturday 97 has ended
Well it isn’t quite over for me just yet, I still have a flight home tomorrow and can’t wait to...
2011-10-02
473 reads
Well it isn’t quite over for me just yet, I still have a flight home tomorrow and can’t wait to...
2011-10-02
473 reads
I flew into Austin Texas today and got to spend time with a lot of great people. The journey started...
2011-10-01
526 reads
Truck is loaded up and heading to the airport to make an appearance at SQL Saturday #97 in Austin TX...
2011-09-30
1,312 reads
I love wearing all my SQL Saturday speaker shirts. Here lately the trend has been nice golf or running shirts...
2011-09-30
1,429 reads
This is post is going to be very simple but it is something I come across ever so often and...
2011-09-28
5,014 reads
This morning I was working on getting all new inherited SQL Servers patched to current levels of service packs when...
2011-09-27
1,477 reads
All the planning, stressing, and freaking out about SQL Saturday #89 came to and end this past weekend. We had...
2011-09-23
411 reads
With a late cancellation with one of our speakers a hole was opened on our speaker lineup. I reached out...
2011-09-14
424 reads
The schedule for SQL Saturday 97 has been posted and I was selected to give my “It’s TempDB, Why Should...
2011-09-08
466 reads
I just 10 short days Atlanta GA will be hosting the most stellar lineup of speakers SQL Saturday has ever...
2011-09-07
450 reads
If you’ve been watching AI roll through the data community and thinking, “this seems...
By Arun Sirpal
Not every production incident is a database in RECOVERY_PENDING or a corrupted event (like...
It is Friday, the queries are running, and nobody is watching the bill. That...
Comments posted to this topic are about the item SQL Art, Part 4: Happy...
Hi All I am trying to find 'bad' characters that users might type in....
Comments posted to this topic are about the item Extreme DAX: Take your Power...
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