Once you have configured what you want to run in the MaskingRules sheet, you are ready to run the MASK action. This will perform the Masking Rules you have defined.
The MASK action runs as follows:
Input: all the mandatory parameters are contained in C:\VIPTDM\SubsetCloneAndMaskRun\Mask\MySQL\Mask_2_Mask.cmd script . Copy and paste this into the arguments tab of the VIP Server Controller and edit any mandatory parameters required. See Masking Parameters for a full list and explanation of mandatory and optional parameters to define at this point.
Output: Masked Data in the Database, MaskReport.txt
Associated Files: C:\VIPTDM\SubsetCloneAndMaskRun\Mask\MySQL\Mask_2_Mask.cmd
Function: This step uses a command script to Mask the specified Data in the chosen Database
Once you have defined the Input, running the action using the VIP Server Controller.The MASK action produces the MaskReport.txt file contains a summary of the action. There is also a full log file in the DataMasking output folder -C:\VIPTDM\SubsetCloneAndMaskRun\Mask\SQLServer\Output.
The output of this action is the masked database which can be viewed using SQL Server Manager.
When running the MASK Action, If you receive an error message in your output dialogue or log, please refer to this troubleshooting article to troubleshoot common issues. You can also run your Action on debug mode for a more detailed log. If you still cannot find the problem, please get in touch with Curiosity by writing to email@example.com
After you have run the MASK action, check the results in the masked database.