What recommendations can HP provide for database maintenance and Microsoft SQL Server?
Please refer to the OO 10.20 Database Guide and section 'Creating a Maintenance Plan' beginning page 19.
HP OO provides a set of scripts for index maintenance, statistics maintenance, and history purging. These scripts create stored procedures that you can tune and schedule to run periodically. Please note that it is recommended to use these procedures but you can also use other methods in accordance with company policy as long as indexes and statistics are kept in good shape.
Note that index rebuilding online (without HP OO system downtime) requires an enterprise grade database. Make sure you are running an enterprise version of Microsoft SQL Server before attempting online index rebuilding. Also, note that maintenance activity usually consumes additional resources from the database. This is why it is important to schedule maintenance activity at the times when HP OO is least active.
Also, take a look at the HP OO 10.20 Database Maintenance Procedures document beginning page 6, section 'Microsoft SQL Server Database Maintenance'.
Please keep in mind that the HP Solutions [1.3.0] content (/Library/Integrations/Hewlett-Packard/Operations Orchestration/10.x/Database/] including Purge Audit Records, Purge Debug Events, and Purge Execution Summary flows may be used to audit records, debug events, and execution summaries.
Regarding purge audit records... If auditing is enabled, you can use the purge audit records operation to purge audit records. OO gives you the option to audit events so that you can track security breaches. Auditing lets you track actions that took place on Central, such as logins, triggering flows, creating schedules, editing configurations, and so on.
Regarding purge debug events (for remote-debug executions)... The flow can be used for keeping the database clean from debugger events which become useless after executions have completed and also affect the size and memory the database occupies.
Regarding purge execution summaries... You can run the Purge Execution Summary operation to purge execution summaries which will include the execution summary, detailed objects with data about the execution.
Use the purge scripts to delete flow history.
The order of running the database purging flows does not matter. It is recommended not to run these flows simultaneously though.
HP recommends to start from running only the Purge Execution Summary flow once a day and optionally raise the frequency to twice a day. Purge Debug Events flow is only needed if there is heavy remote debugging activity by Studio users. Purge Audit Records should only be used if audit is enabled and can be much less frequent.