Starting Conversations - Part 2
A week or so ago I posted a note about reading How to Start a Conversation and Make Friends (worth...
2009-04-15
385 reads
A week or so ago I posted a note about reading How to Start a Conversation and Make Friends (worth...
2009-04-15
385 reads
I happen to notice this in a class recently that I had the rare student - one that could take notes...
2009-04-14
400 reads
I've been writing a lot about networking lately and my efforts to learn/leverage LinkedIn, and along the way taken a...
2009-04-13
825 reads
I currently write the editorial for the PASS Connector which is published every two weeks as part of my role...
2009-04-13
291 reads
Time has flown by since my last update, busy time at work and struggling to get that done and find...
2009-04-13
392 reads
As I've covered in my two earlier posts I've been investing a little time to figure out how to make LinkedIn work for me. This time I wanted to talk about some extra tools they provide that you may find useful. One that I mentioned previously...
2009-04-13
3,192 reads
I currently write the editorial for the PASS Connector which is published every two weeks as part of my role...
2009-04-12
312 reads
Back in December 2008 I wrote up a quick review of Red Thunder, and then received Red Lightning as a...
2009-04-09
284 reads
Please consider this a not quite official announcement, look for that on the sqlpass.org site today or tomorrow.
You may have...
2009-04-09
1,212 reads
The OPENDATASOURCE command is used for adhoc access to other servers or files in a filesystem. MVP Andy Warren shows how you can quickly use this to access data in other sources.
2009-04-09
2,677 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...
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