Run T-SQL in Parallel
Writing CLR procedures to run T-SQL concurrently is not an extremely new idea. I have seen a lot of implementations...
2015-12-03
2,934 reads
Writing CLR procedures to run T-SQL concurrently is not an extremely new idea. I have seen a lot of implementations...
2015-12-03
2,934 reads
Writing CLR procedures to run T-SQL concurrently is not an extremely new idea. I have seen a lot of implementations and I have written and improved it many times...
2015-12-03
6 reads
Quite often, I output information through PRINT command. It works well only when message is shorter than 8000 bytes. When...
2015-11-26 (first published: 2015-11-19)
1,739 reads
I was always challenged when my customers asked me what tables and columns are referenced by a stored procedure which...
2015-11-19
1,559 reads
I was always challenged when my customers asked me what tables and columns are referenced by a stored procedure which was written many years ago by the guy who...
2015-11-19
11 reads
Quite often, I output information through PRINT command. It works well only when message is shorter than 8000 bytes. When the message is greater than 8000 bytes, extra-characters will...
2015-11-19
9 reads
Implementation of SoundEx function is changed in SQL Server 2012, described here. For an example, the result of SOUNDEX(‘Csomorova’) in...
2013-12-17
985 reads
Implementation of SoundEx function is changed in SQL Server 2012, described here. For an example, the result of SOUNDEX(‘Csomorova’) in SQL Server 2012 is C561 whereas the result of...
2013-12-17
6 reads
It seems like I am going to write another none SQL stuff again. No. This is a real life scenario....
2013-11-07
1,216 reads
It seems like I am going to write another none SQL stuff again. No. This is a real life scenario. I am writing an ETL for my customer to...
2013-11-07
8 reads
It is Friday, the queries are running, and nobody is watching the bill. That...
By Steve Jones
Annabel retired from Redgate Software this week. Across most of my career at Redgate,...
By Tim Radney
As a SQL Server DBA with years of experience tuning production environments, I’ve seen...
Comments posted to this topic are about the item What is the Cloud?
Comments posted to this topic are about the item Changing the Schema
Comments posted to this topic are about the item Index Fragmentation Explained: Page Splits,...
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