Stairway to Database Containers Level 2: Persisting Storage in Containers
The second level of the Stairway to Database Containers looks at the basics of persisting storage in your containers.
The second level of the Stairway to Database Containers looks at the basics of persisting storage in your containers.
In this next level of the Stairway to Database Containers learn how to customer a container and save the changes to a new image.
You know I have to say something about Crowdstrike. How could I not? Recovery for most people seems to be well in hand, but there are still places dealing with it. I was personally impacted because I was trying to fly home last Friday. While my airline and the airports I was flying through were […]
Normalizing or UNPIVOTing data may be improved by using this lesser known approach in SQL Server 2008 or later.
Table variables have been fixed in SQL 2019, so now I have to decide if I will use them again.
Learn about various options to migrate an entire SQL Server database to a PostgreSQL database.
Steve is thinking about technology today, inspired by a developer/architect that asks some philosophical and moral questions of software.
In my previous article (What is Microsoft Fabric All About) I explained what Microsoft Fabric is, how it came about and whether it brings anything new to the data insights domain.
Learn how to get a Failover Cluster Instance set up and configured with Windows and SQL Server. This is part of a series showing how to combine a Failover Cluster Instance of SQL Server with an Always On availability group.
This is Part 4 of a series on Always On and FCI integration in SQL Server. In this article we will learn how to add the iSCSI disk storage to our SQL Server nodes and build the cluster.
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