Dynamic Data Masking

SQLServerCentral Article

6 steps to a more secure SQL database

  • Article

Security is often something people think about only after they have had a problem. Given that the average cost of a data breach is $3.92 million (SecurityIntelligence 2019) and ransomware attacks have increased 97% over the past 2 years (PhishMe 2019), the "if it's not broke, don't fix it" approach can clearly be catastrophic. Here […]

(2)

You rated this post out of 5. Change rating

2019-10-07

9,361 reads

External Article

Using SQL Compare with Dynamic Data Masking

  • Article

Dynamic Data Masking is an exciting new feature in SQL Server 2016, allowing DBAs to centrally set a mask that is returned for a table column instead of the actual data, limiting what information is returned to certain users in a consistent and reliable way. What’s more, Redgate SQL Compare safely and reliably handles your DDM changes. Data Platform MVP Steve Jones explains more.

2016-07-21

3,492 reads

Blogs

Tech Conferences and Expanding Your View

By

Tech conferences aren't just for networking and learning how to address a problem you're...

Managing subscribers, creating newsletters

By

When I created the website on WordPress, I was expecting all the features I...

Finding the Last Last Name in SQL: #SQLNewBlogger

By

I wrote a piece on the new SUBSTRING in SQL Server 2025 and got...

Read the latest Blogs

Forums

Getting the Schema for Tables

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Getting the Schema for Tables

An Unexciting Exciting Release

By Steve Jones - SSC Editor

Comments posted to this topic are about the item An Unexciting Exciting Release

UNLOGGED Tables in PostgreSQL: When Speed Matters More Than Durability

By Chandan Shukla

Comments posted to this topic are about the item UNLOGGED Tables in PostgreSQL: When...

Visit the forum

Question of the Day

Getting the Schema for Tables

What happens when I run this on SQL Server 2022 in the AdventureWorks2022 database?

SELECT OBJECT_DEFINITION (OBJECT_ID(N'Person.Person')) AS [Object Definition]; 
GO 

See possible answers