Azure SQL DB – Login failed for user NT AUTHORITY\ANONYMOUS LOGON.
Now that I have your attention with a powerful title how about some context? It is quite common to get...
2018-06-26 (first published: 2018-06-15)
2,304 reads
Now that I have your attention with a powerful title how about some context? It is quite common to get...
2018-06-26 (first published: 2018-06-15)
2,304 reads
Forget about Adaptive Query Processing for a minute, what other feature have I been waiting for? SELECT INTO a specific...
2018-06-19
584 reads
Hello all – I am excited to announce that I will be doing a Stairway series on Azure SQL Database hosted...
2018-06-13
401 reads
In this first level, learn how to get started with Azure and Azure SQL Database.
2018-06-13
6,066 reads
You may (or may not) have a requirement to setup a linked server to Azure SQL Database from a locally...
2018-06-13 (first published: 2018-06-05)
1,861 reads
So what is the default isolation level for Azure SQL Database? I ran the following code to check it out....
2018-05-30
419 reads
I was creating some demo non-clustered indexes in one of my Azure SQL Databases and received the following warning when...
2018-05-30 (first published: 2018-05-22)
1,889 reads
Last year I wrote about Azure SQL Database extended events (https://blobeater.blog/2017/02/06/using-extended-events-in-azure/) and gave an example where I was capturing deadlocks...
2018-05-21 (first published: 2018-05-08)
1,429 reads
I do not always use the Azure portal to make database changes or to check for certain information. I use...
2018-05-14
324 reads
As a mini project I wanted to use Azure logic apps to pull tweets from my twitter account when people...
2018-05-02
339 reads
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...
By Steve Jones
Annabel retired from Redgate Software this week. Across most of my career at Redgate,...
Comments posted to this topic are about the item SQL Art, Part 4: Happy...
WhatsApp: 0817839777 Kw. Industri Pulogadung, Jl. Raya Bekasi Km. 21, Ruko No.A2/18-19, RW.3, Wil,...
WhatsApp: 0817839777 Jl. I Gusti Ngurah Rai No.8 A-B, RT.8/RW.6, Wil, Kec. Duren Sawit,...
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