Snooping
System administrators have a lot of power and temptation to use it. Steve Jones talks about the need to resist temptation and the need for oversight.
System administrators have a lot of power and temptation to use it. Steve Jones talks about the need to resist temptation and the need for oversight.
System administrators have a lot of power and temptation to use it. Steve Jones talks about the need to resist temptation and the need for oversight.
System administrators have a lot of power and temptation to use it. Steve Jones talks about the need to resist temptation and the need for oversight.
This weeks Database Weekly looks at a longtime leader for the Microsoft SQL Server development team leaving the company.
The Mojave Experiment is a marketing effort by Microsoft that is very interesting in looking at first impressions. Steve Jones comments.
This article describes an alternate use of CTEs for functional data processing.
Learn how to set up SQL Server Database Mail in SQL Server 2005. In this tip, you'll see how to configure Profiles and Accounts for sending mail.
Do you avoid certain SQL functionality because you have been told you should NEVER use it?
Do you avoid certain SQL functionality because you have been told you should NEVER use it?
Do you avoid certain SQL functionality because you have been told you should NEVER use it?
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