T-SQL Tuesday #81–Sharpening Skills
This is an interesting month for T-SQL Tuesday. The challenge is from Jason Brimhall to Sharpen Something, and learn something...
2016-08-09
1,144 reads
This is an interesting month for T-SQL Tuesday. The challenge is from Jason Brimhall to Sharpen Something, and learn something...
2016-08-09
1,144 reads
2016-08-09
1,027 reads
The complexity of tables makes modifying them over time a challenge, especially as data sizes grow.
2016-08-08
73 reads
This week Steve Jones looks at a new idea, rating the security of products publicly to try and shame vendors into more secure coding.
2016-08-08
89 reads
I’ll be traveling this week to SQL Saturday #550 in San Antonio. This is my first time traveling to this...
2016-08-08
443 reads
Too many failovers can cause problems, as can those that happen to often. Steve Jones says you need to consider whether you always need to failover in a sitaution.
2016-08-05
182 reads
I’ve had this idea for some time. It’s been bugging me, but I haven’t really been pressured to write, nor...
2016-08-05 (first published: 2016-07-26)
1,628 reads
I’m going to be speaking this fall at Visual Studio Live, Washington D.C. edition on Oct 3-6. This is my...
2016-08-05
460 reads
2016-08-05
1,430 reads
2016-08-04
232 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