How can we help you today? How can we help you today?
Eddie Davis
Hi Elise, Thank you for your forum post. I am not aware of documentation specific to best practices. To answer your questions, I hope the following documents help you: What strategies or features have you found most effective for masking or anonymizing sensitive data? This document is an explanation of the Anonymizer tool and the 3 steps, Classify, Map and masking:  Classify to identify sensitive data which generates a classification file.  Using the classification file to Map a set of instruction for masking which generates a masking file.  Finally Masking which uses the masking file to run the anonymization process. This document explains the Deterministic Data Masking process. This document is how to get started with cloning in Test Data Manager. How do you automate test data refreshes across development and QA environments? Using the Anonymizer and redgate Clone, both include a CLI.  You can then run commands via a scheduler to refresh environments. Are there any pitfalls or best practices you can share for staying compliant? As I highlighted above at the beginning of my reply, there are no best practices documentation. The links I provided above will help in regards to best practices.  Plus there is the help documentation for Test Data Manger, redgate Clone and Product Learning resources. I recommend that you contact your Redgate Sales AE if you need help setting up your POC or require product training or guided installation via Redgate's Professional Services team. Or if you have encountered a technical problem you need help upon, please submit a support request via the support portal or email support@red-gate.com. Many Thanks Eddie Davis Senior Product Support Engineer Product Support Team Redgate Software Limited   / comments
Hi Elise,Thank you for your forum post.I am not aware of documentation specific to best practices. To answer your questions, I hope the following documents help you:What strategies or features have...
0 votes
Hi, The THREADCOUNT parameter specifies the number of threads the backup job will use when creating the backup file.  In background when SQL Backup issues the backup command to SQL Server, it creates the Virtual Device Interface (VDI) and waits for SQL Server to respond.  The number of VDI's created is dependent of the THREADCOUNT value.  This process actually creates a corresponding number of sqb files, which are then wrapped up into a single *.sqb file.  The THREADCOUNT value used to create the backup is stored in the *.sqb file header. The restore process will unwrap the single *sql file, back in multiple sqb files and generate the corresponding VDI's to perform the restore, matching the number of VDI's configured for the backup job. Using your example THREADCOUNT = 7, this will create backup job with 7 VDI created, then wrapped up into a single *.sqb file.  The restore process will create 7 VDI's to perform the restore. Valid integer values are between 2 and 32 inclusive.  However, you also need to be aware of the total number of CPU cores available.  As specifying a THREADCOUNT value higher than the total number of CPU cores will affect the performance of the backup task badly. The ideal value for the THREADCOUNT parameter is: (Total number of CPU Cores) - 1.  For example Total number of CPU Cores = 8, so 8 minus 1 = 7, set the THREADCOUNT parameter = 7. Unlike the backup task, the user cannot set the THREADCOUNT parameter for the restore job. The THREADCOUNT value is stored in the backup file header and the value stored here is used for the restore process.  If the total number of CPU cores of the server is less than the THREADCOUNT value, the performance of the restore job will be badly reduced.  So if restoring the backup file to a different server, ensure the hardware specification for the CPU of the restoring server at least matches the hardware specification for the server that created the backup. I hope the above answers your question. Many Thanks Eddie Davis Senior Product Support Engineer Redgate Software Limited / comments
Hi,The THREADCOUNT parameter specifies the number of threads the backup job will use when creating the backup file.  In background when SQL Backup issues the backup command to SQL Server, it create...
0 votes