Windows Azure introduced SQL Azure V12 which has support for Dynamic Data Masking. It seems like Window
Azure SQL Database versioning runs in parallel with SQL SERVR release
versions. There are some other new features that SQL SERVER 2014 has support for as well. One New SQL 2014 feature that is noteworthy is the ability to
create tables with no CLUSTERED INDEX and no identities columns.
SQL-Data Masking Feature built-in to Microsoft SQL Server and SQL Azure is a
feature that Oracle’s Database has had for a while. Checkout Oracle Database Data Masking which is feature that
Oracle had introduced years ago. Of course you might think these Data Obfuscation Engines being built-in to databases is somehow detrimental to our
software IDentity Jammer; but that’s actually not true; Oracle and Microsoft both
entering The Database Obfuscation Space brings visibility and validates the problem as an important issue that users have been facing. Of course there are
significant differences between IDentity Jammer and What the Database Engines Offer.
is capable of performing Ad-Hoc Data-Obfuscation on the Application User Interface. While SQL Server and Oracle Data Masking Engines must be configured
before-hand and typically cannot be run on production environments at a moment’s notice. Database Data Masking Engines are targeted toward advanced users
that have access to Data-Center Backend. Database Data Masking Engines are basically designed to be used by a DBA not a typical user who is not very technically savvy.
Figure 1: Architectural Differences between IDentity Jammer and Database Masking Engines.