Dynamic masking functionality is new to SQL 2016. It is applied on columns.

https://docs.microsoft.com/en-us/sql/relational-databases/security/dynamic-data-masking

Great for DEV and UAT environments where data obscurity is required.

CREATE TABLE Membership

(MemberID int IDENTITY PRIMARY KEY,

FirstName varchar(100) MASKED WITH (FUNCTION = 'partial(1,"XXXXXXX",0)') NULL, *ignore these

LastName varchar(100) NOT NULL,

Phone# varchar(12) MASKED WITH (FUNCTION = 'default()') NULL,

Email varchar(100) MASKED WITH (FUNCTION = 'email()') NULL);

Ideally we need this ignored in SQL Compare and SQL Source control comparisons so it is not accidentally deployed to production.