Scheduling Audits with DrAuditor
So, you have created some audits with tables that are important to you, now what? The design of DrAuditor was to make auditing the Data Repository simple, quick and most of all to save you time. Scheduling your audits to run at specific times is probably one of the best ways to save time.
When an audit is scheduled to run on a daily, weekly, or even monthly basis, DrAuditor keeps statistical and historical information about the audit results. This can be helpful in figuring out when something was fixed or if a change has caused your Data Repository tables to become less accurate. When a scheduled audit re-runs “samples again” it truncates the examples of missing rows and column discrepancies but it keeps the statistics (rows sampled, number missing rows found and column issues). Re-running an audit can be more beneficial than creating a new audit because it will save space in SQL by truncating and repopulating the disparate data.
Scheduling audits to run removes the manual process of starting audits which can be a significant time saver. When scheduling your audits to run it’s a good idea to stagger them so that they run at different times. This will help with the load on the DrAuditor machine as well as MEDITECH and SQL. Although there are rules built into DrAuditor preventing you from starting too many audits per MEDITECH filer server at a time, it’s still good practice to stagger the run time of your audits if possible. Scheduling them makes this much easier. But don’t be concerned if an audit has not completed before a different audit is scheduled to start.
DrAuditor uses the Windows Task Scheduler for automating the process of starting unattended audits. The Windows Task Scheduler allows for simple and complex schedules to be created for starting an audit. DrAuditor will launch the Windows Task scheduler when you modify a schedule for an audit.
The link below goes through a step by step process to create audits.