2016-04-13
1,201 reads
2016-04-13
1,201 reads
Dynamic Data Masking allows you to obscure your confidential data column values at the database engine level for both new and existing SQL Server data. Being able to alter the definition of an existing column to add a masking rule makes it very simple to obscure your existing column values without even changing your application code.
2016-04-07
4,873 reads
2016-03-21
1,338 reads
This stairway will examine Dynamic Data Data Masking, introduced in Azure SQL Database and SQL Server 2016. This should allow you to implement Dynamic Data Masking in your application, understanding the implications of the various masks used on different datatypes.
2016-03-15
4,028 reads
2016-03-08
1,148 reads
Greg Larson looks at how to hide the value of sensitive data by applying Dynamic Data Masking.
2016-03-01
5,302 reads
Dynamic data masking provides a simple way to implement obfuscation of private data. However it's important to understand the limitations, and to keep in mind that it is not true encryption and that the data cannot be protected in all scenarios. Aaron Bertrand explains.
2015-09-03
3,475 reads
2015-08-10
2,174 reads
SQL Server 2016 introduces a new security feature called Dynamic Data Masking (DDM). This tip describes its purpose, shows a brief example of how it works, lists some limitations, and notes how the feature has already changed since CTP 2.0 was first released in May.
2015-07-15
2,728 reads
By SQLPals
Why sys.fn_dblog Is Undocumented And Why It's Still There Why sys.fn_dblog...
When I put together the invitation for T-SQL Tuesday #202, I wasn't sure what...
By Steve Jones
My life has some crazy travel stretches for sure. Between speaking, office visits, customer...
Comments posted to this topic are about the item Implementing Type 4 Slowly Changing...
Comments posted to this topic are about the item The Disabled Index
Comments posted to this topic are about the item Server-Level Table sizes
I run this code on SQL Server 2022.
CREATE TABLE Drink
(
drinkid INT NOT NULL
CONSTRAINT DrinkPK PRIMARY KEY CLUSTERED,
drinkname VARCHAR(20),
rating NUMERIC(2, 1)
)
GO
INSERT INTO Drink
(
drinkid,
drinkname,
rating
)
VALUES
(1, 'Margarita', 4.5),
(2, 'Mojito', 4.3),
(3, 'Old Fashioned', 4.7),
(4, 'Martini', 4.4),
(5, 'Cosmopolitan', 4.2)
GO
ALTER INDEX drinkpk ON dbo.drink DISABLE
GO
SELECT * FROM dbo.Drink
GO
What is the result? See possible answers