I'm thinking of using the new dynamic data masking that has been introduced with SQL Server 2016 as part of our GDPR project . Does anyone else have experience of it? I am particularly interested if there is a performance overheard.
-
This article will give you head start about writing your own test harness.– SqlWorldWideAug 7, 2017 at 14:07
-
Also see Understand the Limitations of SQL Server Dynamic Data Masking - this doesn't address performance, but might identify potential issues with this technology that you haven't considered.– Aaron BertrandAug 7, 2017 at 17:29
Add a comment
|
1 Answer
No, there is no overhead involved (not heard of any yet). I have used it in my Azure SQL Database and works like a charm.
Data Masking is a quick solution for data security as you can control the users who can view the data, but on a broader aspect this cannot be the sole security solution.
Please read below links for better understanding:
- Dynamic Data Masking (Microsoft documentation)
- Encrypting SQL Server: Dynamic Data Masking by Robert Sheldon
answered Aug 7, 2017 at 14:18
-
Thanks for that. I'm aware its a bit of a quick fix but we are looking at other options. We decided on this route because we felt column level encryption wasn't an option Aug 8, 2017 at 8:39