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
it has been a year since i have not written much on the blog...
By Steve Jones
on tenderhooks – adj. feeling the primal satisfaction of being needed by someone, which...
By DataOnWheels
I have been active in the data community throughout my career. I have met...
Comments posted to this topic are about the item A Quick Restore
Comments posted to this topic are about the item Guarding Against SQL Injection at...
I have a quick question on Ola Hallengren Index Optimize Maintenance . Do we...
While doing some testing of an application, I wanted to reset my environment after doing some testing with this code:
USE DNRTest BACKUP DATABASE DNRTest TO DISK = 'dnrtest.bak' GO /* Bunch of stuff tested here */RESTORE DATABASE DNRTest FROM DISK = 'dnrtest.bak' WITH REPLACEWhat happens if this runs, assuming the "bunch of stuff" isn't anything affecting the instance. See possible answers