Power BI with Narrative Science: Look Who's Talking (Part 3: On or Off premises)
[2017-May-08] Listening to a car radio with many different talk shows available, it comes more often to my mind, that...
2017-05-08
680 reads
[2017-May-08] Listening to a car radio with many different talk shows available, it comes more often to my mind, that...
2017-05-08
680 reads
I was eating dinner with Hugo Kornelis and we started talking about query hash values. You know, like everyone does...
2017-05-08 (first published: 2017-04-24)
1,313 reads
As promised, here are the slides for my two presentations from SSWUG’s 2017 Spring Virtual Conference:
SSWUG_Spring_Building an Auditing Framework for...
2017-05-08
326 reads
This will be year #9 of sql saturdays in Louisville. Every year (starting with 3rd or 4th), it has been...
2017-05-08
444 reads
I got bored (really bored) one weekend I decided to challenge myself. I had corruption within a specific table (localised...
2017-05-08
409 reads
I have upgraded the ssdt dev pack to support visual studio 2017 and fixed a couple of minor annoyances and...
2017-05-08
49 reads
I have upgraded the ssdt dev pack to support visual studio 2017 and fixed a couple of minor annoyances and have started to think about how to improve it...
2017-05-08
6 reads
I have upgraded the ssdt dev pack to support visual studio 2017 and fixed a couple of minor annoyances and...
2017-05-08
61 reads
I have upgraded the ssdt dev pack to support visual studio 2017 and fixed a couple of minor annoyances and...
2017-05-08
1,002 reads
I have upgraded the ssdt dev pack to support visual studio 2017 and fixed a couple of minor annoyances and...
2017-05-08
17 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