Dynamic Data Masking is designed to obscure certain data when it is retrieved. This means that the data itself is not changed, only the display of the data.
This type of obfuscation is used when certain columns in tables can only be read/viewed by a limited group of people. In earlier versions of SQL Server, you could create a view and add or remove columns. It was also possible to encrypt individual columns, but this inevitably changes the data when it is saved and not just the display.
To define a "mask", the bosnia and herzegovina telegram screening columns we want to mask must be extended with another property. The masked with property is appended after the data type of the column definition.
In Fig.4 we see a table with five columns; four of them have masking defined. As seen above, there is the possibility to influence the masking function. The default function shows a standard output defined by Microsoft, which is automatically applied for the supported data types. In addition to these, there are the functions email , partial and random ; except for random , the functions are shown in Fig.4. These functions were extended and improved during the beta phase of SQL Server 2016. The limitations of the functions and supported data types can be found at Books Online.
As soon as the masking has been defined, the data is only obfuscated when it is displayed in a query, as in Fig. 4. The decision as to whether a user can see the obfuscated data is currently controlled at the database level. This means that a user can currently see either all obfuscated data in a database or none at all. The granularity of the authorization is therefore not yet fully developed. However, my hope is that Microsoft will allow permissions to be controlled down to the column level. It remains to be seen whether and how Microsoft will develop this authorization concept further.