Redgate SQL Data Masker Refreshing Schema from Blog Posts – SQLServerCentral

This is a quick blog to help me remember what is going on with the Data Masker product. This is for the SQL Server version, but I believe the Oracle one is very similar.

I added a new column to a table, and I had a masking plan already built. How do I get my masking plan to show the new column?

Here is my masking plan:

I added a new column to the DCCheck table, which is under rule 01-0026.

If I open that mask and add a new column, I get this, but I can’t expand the dropdown. All the columns in this table are masked, and data masker doesn’t know about the new one.

I need an updated schema, as the rules do not update in real time. To get this to work, I need to return to the masking plan and double click the controller at the top. This is the schema manager for my set of rules.

Note: If I mask different schemas, I need different controllers.

Once this opens, I can see my connection to a database. In my case, I’m building this in dev areas, so it’s pointed to the QA environment.

If I click the “Tools” tab at the top, I see lots of options, one of which is to refresh.

Once I pick that one, I have a bunch of more options, which gets confusing, but I can click the “refresh all tables” at the top, leaving everything alone. Once that’s done, I get a note.

Once I get this, I can return to my rule, and when I add a new column, and I see it listed.

This isn’t the smoothest flow, but data masker isn’t something that is likely to be in constant use. For many of us, adding new schema items is relatively rare, so we can adjust our plans as needed.

The one good thing is that I can easily find where I need to add a column, as opposed to digging through a number of .SQL scripts.

The post Redgate SQL Data Masker Refreshing Schema appeared first on SQLServerCentral.