What’s next?
As I’m sure a fair number of you already know I was told my position had been eliminated. They are ... Continue reading
2022-06-21
344 reads
As I’m sure a fair number of you already know I was told my position had been eliminated. They are ... Continue reading
2022-06-21
344 reads
I started to add a daily coping tip to the SQLServerCentral newsletter and to the Community Circle, which is helping me deal with the issues in the world. I’m...
2022-06-20
44 reads
There were a number of data platform announcements at Microsoft Build yesterday that I wanted to blog about. Everything announced at Build can be found in the Microsoft Build 2022...
2022-06-20 (first published: 2022-05-25)
255 reads
One of the new language features added in SQL Server 2022 is the GENERATE_SERIES function. This allows you to generate a SELECT * FROM GENERATE_SERIES(start=1, stop=7) This gives me...
2022-06-20
517 reads
SQL Server can run in any Virtual Machine that has the appropriate operating system (yes, I said that because I have some hope, that we will one day learn...
2022-06-20 (first published: 2022-06-03)
466 reads
I started to add a daily coping tip to the SQLServerCentral newsletter and to the Community Circle, which is helping me deal with the issues in the world. I’m...
2022-06-17
49 reads
Power BI field parameters are a new feature in Power BI Desktop, and it’s one of the best of the past months. In short, Power BI field parameters allow...
2022-06-17
133 reads
Knowing the days between events is a fairly common reporting request because a lot of reporting is created to track SLA’s (service level agreement) and other KPI’s (key performance...
2022-06-17 (first published: 2022-06-03)
297 reads
Background If you’ve been using Availability Groups, you’re familiar with the replica seeding (sometimes called initializing, preparing or data sychronization) process. Seeding is a size of operation-based data, copying...
2022-06-17 (first published: 2022-05-26)
345 reads
I’m very excited to announce I’ll be giving a session at the 15th edition of dataMinds Connect (in the beginning it was called SQL Server Day(s)). It will be...
2022-06-17 (first published: 2022-06-16)
30 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....
WhatsApp: 0817839777 Kw. Industri Pulogadung, Jl. Raya Bekasi Km. 21, Ruko No.A2/18-19, RW.3, Wil,...
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