Database

For performance reasons, we recommend putting the database into Simple Recovery mode before masking, this reduces the size of the log files that will be generated.

We recommend that you monitor the growth of the log files during a masking run and for subsequent runs ensure that sufficient space is allocated before the run as log file growth will slow masking performance. 

On Azure/AWS

Data Masker, by default, will be doing a lot of writes so allocating higher-throughput (high IOPS) storage will give you better masking performance but we recommend trying with the defaults first and then increasing the IOPS as required. 

TempDB Files

We recommend that you monitor the space allocated for TempDB during a masking run. For optimal performance, you want to allocate enough TempDB space to prevent it from needing to grow.

We recommend allocating TempDB to be 15% of the overall database size and monitor for any growth during a run. If you find that growth has occurred increase the TempDB size allocation to 20% larger.

On Azure/AWS

Data Masker, by default, will put pressure on the TempDB so allocating higher-throughput (high IOPS) storage will give you better masking performance but we recommend trying with the defaults first and then increasing the IOPS as required.