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.
SQL Server – Dynamic Data Masking Performance Overhead
dynamic-data-maskingsql serversql-server-2016
Related Question
- Sql-server – How to script a table with dynamic data masking via SSMS
- SQL Server – Best Practices for SSIS Project Deployments
- SQL Server – Returning a Variable from Dynamic SQL
- Sql-server – Capturing Column Names in Dynamic SQL Statement
- SQL Server – Dynamic Auditing Trigger Without Temporary Tables
- SQL Server – How to Limit Dynamic Data Masking with WHERE Clause
Best 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: