2016-04-13
1,191 reads
2016-04-13
1,191 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,334 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
3,988 reads
2016-03-08
1,139 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,157 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 Vinay Thakur
Continuing from Day 3 where we covered LLM models open/closed and their parameters, Today...
By Steve Jones
One of the nice things about Flyway Desktop is that it helps you manage...
By HeyMo0sh
Microsoft Fabric (not to be confused with the more general term “fabric” in DevOps)...
I'm fairly certain I know the answer to this from digging into it yesterday,...
Hi Team, I am trying to refresh the Azure Synapse Dedicated pool from production...
hi everyone I am not sure how to write the query that will produce...
I have some data in a table:
CREATE TABLE #test_data
(
id INT PRIMARY KEY,
name VARCHAR(100),
birth_date DATE
);
-- Step 2: Insert rows
INSERT INTO #test_data
VALUES
(1, 'Olivia', '2025-01-05'),
(2, 'Emma', '2025-03-02'),
(3, 'Liam', '2025-11-15'),
(4, 'Noah', '2025-12-22');
If I run this query, how many rows are returned?
SELECT *
FROM OPENJSON(
(
SELECT t.* FROM #test_data AS t FOR JSON PATH
)
) t; See possible answers