Skip to main content

. SQL Server.

To configure Microsoft SQL Server for data masking

  1. Login to the server hosting the database you want to mask in as system administrator.

  2. Navigate to the PK Protect scripts folder located at this location:

    /opt/Dataguise/DgSecure/IDPs/DgMaskerIDP/expandedArchive/WEB-INF/classes/com/dataguise/Worker/Masker/PrerequisiteFiles/Scripts/SQL

  3. Execute the script file SQL_Init_Query.sql. This creates a database for the work tables and a user that can access both the work database and the target databases.

  4. Configure the SQL Server environment.

  5. Navigate to the PK Protect scripts folder located at:
    Opt/Dataguise/DgSecure/IDPs/DgMaskerIDP/expandedArchive/WEB-INF/classes/com/dataguise/Worker/Masker/PrerequisiteFiles/Scripts/SQL

  6. Copy the script file SQL_Init_Query.sql to your computer.

  7. Adjust the parameters in the SQL script file. Open SQL_Init_Query.sql in the text editor of your choice and locate the Parameters section near the top of the file. The following parameters are displayed along with their default values.

  8. Replace the DB_NAMES_TO_MASK default value with a comma-separated list of the databases you plan to mask. Keep the default values for the rest of the parameters or change them as you see fit.

*Note: Do not delete the single quotes that surround most of the parameter values save the file.

  1. Log on to the SQL Server using a sysadmin account (sa by default). Execute the script file to:

  2. Create and configure the Masker work database.

  3. Create a user that can access the work database and each target database.

  4. The username and password are the values you supplied for DG_USER and DG_USER_PASS. (The default is dguser for both the username and password). Supply this login information when you create a connection to the server using the PK Protect Connection Manager. For information about the Connection Manager, see the PK Protect User Guide or the online help.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.