The ITPAM database mdf file along with the transaction log can become large.
ITPAM makes heavy use of the database, it is not unusual for production usage to utilize gigabytes of database space in a relatively short amount of time, and we have seen IT Process Automation utilize over 500GB of disk space in production environments.
Understanding how ITPAM utilizes the database can help you prepare for, as well as minimize, this usage as much as possible.
Process Automation v4.2.x and up
ITPAM has three distinct schemas.
Library:
Administrators can delete them from the configuration browser or through other direction SQL means.
To keep things small, it is important to understand what is growing:
Queues:
Reporting DB:
oasis.disable.reporting.manager=true
and restart the Orchestrator(s)
This will save space and processing.
For SQL Server:
Please also see the SQL Server technical documentation. Please discuss the below with your DBA first.
Turn the DB recovery model from full to simple
Shrink the DB (using the "Shrink a Database" topic detailed in SQL Server technical documentation mentioned above)
Issue "checkpoint" command (commit)