Helpful guidelines for improving the overall system performance when executing jobs.
- Choose the right level of comparison for your requirements. For example, schedule row counts for quick daily checks and full-row data checks once a week.
- Whenever possible, schedule comparisons to run after replication has finished.
- Configure the databases to optimize for select and order by statements.
- Preferably make sure that each table being compared has a single column primary key.
- Run your comparison using the database_hash option rather than the literal option.
- Generate a summary report instead of a column log for a job. Choosing a column log adds an extra database lookup for column values.
- Configure jobs to abort if there are too many differences.