This section contains maintenance information as a best practice for the following Microsoft Provisioning System (MPS) database components:

  • Audit Log
  • Transaction Log

For information about tools designed to enable you to perform routine maintenance on the Resource Manager database, see Resource Manager SQL Maintenance Jobs.

Audit Log File Management

Because MPS does not perform any maintenance against the Audit log, you should create a plan for managing the Audit log file. One way to manage this log is by setting the Audit Level property in the Provisioning Server Microsoft Management Console (MMC). You can access this property by using the Provisioning Engines option, and then you can configure which transactions are saved to the Audit log and what kinds of data is passed for these transactions.

You should back up the Audit database before clearing out its tables. The easiest method is to use a Microsoft SQL Server script to periodically delete older rows from the requests table in the MPFAudit database. You can achieve this with a SQL Server command such as:USE MPFAudit DELETE FROM Request WHERE LastUpdated < 'MM/DD/YY hh:mm:ss' Replace the MM/DD/YY hh:mm:ss in the example above with the date and time before which you wish to delete older rows.

Transaction Log File Management

MPS temporarily stores data in the Transaction log. MPS uses this information to perform a transaction rollback in the event of a failure. Approximately once a minute, the MPS Provisioning Audit and Recovery Service moves failed transaction information to the Audit database. Once a transaction completes, an auditing and recovery manager either deletes the transaction (if it is not marked for audit) or moves the transaction to the audit log (if it is marked for audit).