How to purge the Service Management Automation database
Updated: November 1, 2013
Applies To: System Center 2012 R2 Orchestrator, Windows Azure Pack for Windows Server
In Service Management Automation, database purging is automatic, but you can adjust it to your needs.
To enable the automatic database purge, you must enable the SQL Server Agent (MSSQLSERVER) service for Automatic start. The service is not turned on by default, but it is frequently started by SQL Server database administrators for other tasks.
If the SQL Server Agent service is not running, the purge will not occur and eventually the customer will experience performance issues, first in the portal. and then with the back end.)
The job task that performs purge can be set up in the installer even if the customer is not running the SQL Server Agent service. But it will not do anything until the service is enabled.
The database purge job is automatic, but it can be regulated by the Service Management Automation administrator.
By default, the database purge job runs every 15 minutes, and it runs only if there are records to purge.
Records are purged only if they are older than the default duration of 30 days. This time is configurable by using the Set-SmaAdminConfiguration cmdlet and setting the –PurgeJobsOlderThanCountDays parameter.
If the total job record count exceeds the MaxJobRecords parameter set by the same Set-SmaAdminConfiguration cmdlet, then more job records will be purged. The default value for this parameter is 120,000 records.
For additional resources, see Information and Support for System Center 2012.
Tip: Use this query to find online documentation in the TechNet Library for System Center 2012. For instructions and examples, see Search the System Center 2012 Documentation Library.