Adios FlyClear
Last year I wrote about signing up for Clear, a registered traveler program. I've flown enough to make it useful...
2009-05-10
586 reads
Last year I wrote about signing up for Clear, a registered traveler program. I've flown enough to make it useful...
2009-05-10
586 reads
Fiction review this week. I recently read Patriot Acts by Greg Rucka, the continuation of the story that started in...
2009-05-07
286 reads
I'm just finishing up SQL Server 2008 Query Performance Tuning Distilled by Grant Fritchey and Sajal Dam and overall I've...
2009-05-07
494 reads
A few weeks back I wrote about trying out the LinkedIn Add-in and time has reinforced for me that it's...
2009-05-06
487 reads
As I've mentioned in earlier posts (Part 1, Part 2, Part 3) I've engaged speaking and networking Don Gabor to...
2009-05-05
410 reads
My friend Grant Fritchey recently posted in response to a quiz and at the end of that mentioned that he'd...
2009-05-04
584 reads
Just had a call with Ken Starnes last week and all is proceeding for a great two track event in...
2009-05-04
296 reads
If you haven't already, start with Part 1 and Part 2. In Part 2 I mentioned that I have hired Don to coach me on networking, and this week I'll share some results from our first 1.5 hour session.
2009-05-04
975 reads
I drove up on Friday night for the speaker dinner, getting there after a busy day trying to catch up...
2009-05-03
420 reads
I've been trying to feature a blog each month and for April (one day late!) it's Aaron Alton. HOBT stands...
2009-05-01
490 reads
With Fabric Mirroring, Microsoft is promoting a nice and appealing story for operational reporting...
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...
Comments posted to this topic are about the item SQL Art, Part 4: Happy...
WhatsApp:0817-866-887 Jl. Ahmad Yani No.31, Pattunuang, Kec. Wajo, Kota Makassar, Sulawesi Selatan 90174 (@bcakcumakassar)
Hi All I am trying to find 'bad' characters that users might type in....
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