Daily Coping 8 Mar 2023
Today’s coping tip is ask someone how their day is going and really listen to them. I had the chance to do this with one of the kids I...
2023-03-08
19 reads
Today’s coping tip is ask someone how their day is going and really listen to them. I had the chance to do this with one of the kids I...
2023-03-08
19 reads
Originally, I was going to write a post on troubleshooting SQL Server. This is because I’m writing up and reviewing a lot of documentation at my current job. I’ll...
2023-03-08 (first published: 2023-03-01)
454 reads
I missed T-SQL Tuesday last month. I got busy and distracted with some travel. For #159, Deepthi Goguri hosted. I’ve enjoyed watching her blog and grow her knowledge the...
2023-03-08
77 reads
Today’s coping tip is give positive comments to as many people as possible today. On a travel day, I made an effort here. Those are always better for me,...
2023-03-07
21 reads
Azure Synapse Analytics is not just “another service” in the Azure. It’s very comprehensive set of tools rather than one-goal-tool (like Azure Key Vault or even Storage Account). On...
2023-03-07
45 reads
Today’s coping tip is to make plans with a friend and catch up with them. I decided to reach out to a friend and make time to catch up....
2023-03-06
23 reads
In the last post I hadn’t found the breakdown of questions for the exam. The Open Group does publish the TOGAF 9 Certified Study Guide (link goes to the...
2023-03-06
59 reads
When I teach the ISACA Certified Information Systems Auditor (CISA) course, one of the things I walk candidates through is how the test is structured and how much each...
2023-03-06 (first published: 2023-02-28)
296 reads
Last week I posted the results from using Extended Events to snoop on what happens inside an AWS RDS database. This week, I’m taking a look at what happens...
2023-03-06 (first published: 2023-02-27)
430 reads
Well, for those who don’t know me, I’m just barely started on my PostgreSQL journey. So, what the heck can I contribute to this conversation? Not much, but I...
2023-03-03
31 reads
With Fabric Mirroring, Microsoft is promoting a nice and appealing story for operational reporting...
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...
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