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,367 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

Did You Really Name That Default?

By

Ten years (and a couple jobs) ago, I wrote about naming default constraints to...

Monday Monitor Tips: A New Analysis Page

By

We have multiple teams (8) working on Redgate Monitor. Some work on the Standard...

Case Studies: Real-World Success Stories of FinOps Implementation

By

Learning any kind of theory is easy, but adapting FinOps and watching it rescue...

Read the latest Blogs

Forums

The day-to-day pressures of a DBA team, and how we can work smarter with automation and AI

By Terry Jago

Comments posted to this topic are about the item The day-to-day pressures of a...

The Problem Isn't Always Your Query or Schema... Sometimes It's Hidden Assumptions

By dbruton95

Comments posted to this topic are about the item The Problem Isn't Always Your...

Identity Defaults

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Identity Defaults

Visit the forum

Question of the Day

Identity Defaults

What happens when I run this code?

CREATE TABLE dbo.IdentityTest
(
     id int IDENTITY(10) PRIMARY KEY,
     somevalue VARCHAR(20)
)
GO

See possible answers