After completing the other tasks and masking your data, you should create a job to certify your data on an ongoing basis. This alerts you if unmasked data is introduced to a masked database.

Certifying Data

  1. Create a Certify job, as described in Creating a New Certify Job below.
  2. Run the Certify job.
  3. Confirm that no unmasked data has been introduced.

For detailed information about certifying data, see Certifying Data.

Creating a New Certify Job

  1. Click Certify.
    The Create Certify Job window appears.  

    You will be prompted for the following information:

    1. Job Name — A free-form name for the job you are creating. Must be unique.
    2. Multi Tenant — Check box if the job is for a multi-tenant database.
    3. Rule Set — Select a rule set that this job will execute against.
    4. Generator — The default value is Delphix.
    5. No. of Streams — The number of parallel streams to use when running the jobs. For example, you can select two streams to run two tables in the ruleset concurrently in the job instead of one table at a time.
    6. Remote Server — (optional) The remote server that will execute the jobs. This option lets you choose to execute jobs on a remote server, rather than on the local Delphix instance. Note: This is an add-on feature for Delphix Standard Edition.
    7. Min Memory (MB) — (optional) Minimum amount of memory to allocate for the job, in megabytes.
    8. Max Memory (MB) — (optional) Maximum amount of memory to allocate for the job, in megabytes.
    9. Feedback Size — (optional) The number of rows to process before writing a message to the logs. Set this parameter to the appropriate level of detail required for monitoring your job. For example, if you set this number significantly higher than the actual number of rows in a job, the progress for that job will only show 0 or 100%.
    10. Prescript — (optional) Specify the full pathname of a file that contains SQL statements to be run before the job starts, or click Browse to specify a file. If you are editing the job and a prescript file is already specified, you can click the Delete button to remove the file. (The Delete button only appears if a prescript file was already specified.) For information about creating your own prescript files, see Creating SQL Statements to Run Before and After Jobs.
    11. Postscript — (optional) Specify the full pathname of a file that contains SQL statements to be run after the job runs, or click Browse to specify a file. If you are editing the job and a postscript file is already specified, you can click the Delete button to remove the file. (The Delete button only appears if a postscript file was already specified.) For information about creating your own postscript files, see Creating SQL Statements to Run Before and After Jobs.
    12. Delta Masking — Check this box to mask rows that are not masked and are identified as part of the certification process as polluted.
    13. Batch Update — (optional) Enable or disable use of a batch for updates. A job's statements can either be executed individually, or can be put in a batch file and executed at once, which is faster.
    14. Disable Trigger — (optional) Whether to automatically disable database triggers. The default is for this check box to be clear and therefore not perform automatic disabling of triggers.
    15. Comments — (optional) Add comments related to this certification job.
    16. Email — (optional) Add e-mail address(es) to which to send status messages.
  2. When you are finished, click Save.