The Basics of Dynamic Data Masking - Step 1 of the Stairway to Dynamic Data Masking
Learn the basics of how Dynamic Data Masking can be used to obfuscate data in SQL Server 2016+.
Learn the basics of how Dynamic Data Masking can be used to obfuscate data in SQL Server 2016+.
New solution allows developers and teams to “buy the base and rent the peak” when provisioning for variable workloads without wastage or performance tradeoffs
Or perhaps another way to phrase that is, Microsoft is up to something with parallelism. I don’t know how long it’s been this way – could even be since the launch of Azure SQL DB Serverless – but I just now noticed it while helping a client with a slow query.
When we need to be heroes in IT on a regular basis, that's a problem for Steve.
This article will show the basic outline for how Python scripts can access and work with data in SQL Server.
I’ve quietly resolved performance issues by re-writing slow queries to avoid DISTINCT. Often, the DISTINCT is there only to serve as a “join-fixer,” and I can explain what that means using an example.
Speed of delivery and protecting data can often feel incompatible, but there are industry-proven database DevOps practices that bring them together in harmony.
Across each of these five key practices, there’s a theme of removing barriers and cognitive load for teams; but crucially, they are also putting safeguards in place to reduce the risks to production environments.
William Shakespeare once wrote in the play Romeo and Juliet: “What's in a name? That which we call a rose, by any other word would smell as sweet.” It is a beautiful sentiment in that context, and even still you might say that there is some truth to this saying in a lot of ways. […]
Learn how you can configure an Azure Data Factory pipeline that is triggered by an email being sent to an address.
Today Steve looks at the case when one software developer finishes their work, but another doesn't. The challenge of reordering work is something that happens more and more as teams struggle to coordinate their efforts.
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,...
By Tim Radney
As a SQL Server DBA with years of experience tuning production environments, I’ve seen...
Comments posted to this topic are about the item What is the Cloud?
Comments posted to this topic are about the item Changing the Schema
Comments posted to this topic are about the item Index Fragmentation Explained: Page Splits,...
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