Masking Your On-Premises Database With SQL Data Mask

things move fast in foundry, redgate’s research and development division. in our last update three weeks ago, we announced our intention to build a version of sql data mask that would mask on-premises sql server databases, as well as azure sql databases. we’re pleased to say this version is now available.

we’re working closely with a select group of people who are helping us test and iterate this solution; our goal is to make sure sql data mask is able to satisfy your masking requirements.

how does it work?

if you’ve previously tried sql data mask, you’ll know that it’s available from redgate foundry (as with all our prototype tools). this is also the starting point for masking an on-premises sql server database.

now when you log into redgate foundry and open sql data mask, you’ll see the option to download the on-premises version:

once installed, sql data mask will launch automatically and look very similar to the web version (we’ll talk more about how we’ve done this soon). simply log in to the application in the same way that you log in to redgate foundry .

logging in helps us work more closely with users so we can develop sql data mask with your help (in fact, you can talk to us in-app by clicking the red bubble in the bottom-right corner any time).

the first time you use sql data mask, you’ll need to grant it permission to access your azure or microsoft account:

choose the sql server and database you want to mask and specify where you want the new masked database to be created:

the server list gets populated by auto-discovering the servers in the network available to the machine where sql data mask is installed. also, notice that you have the ability to use sql server authentication if you prefer.

sql data mask will scan your database for sensitive data and if a table contains columns with data it thinks should be masked, it will identify it with an icon:

select the table to view the column masks being applied, and modify them if necessary:

once you’re happy, hit start masking and let us know how you get on!

what next?

naturally, we’ll continue to make sql data mask more robust, capable, and flexible, but we’re also interested to know more about where data masking fits into your workflow.

do you need to share information about the masking choices you made in order for colleagues to be able to reuse it? would those choices change over time, or would they likely stay true forever? send us and let us know.

in the meantime, head over to redgate foundry and try sql data mask now — we’d love to hear how well it masks your database for you.