Maintaining a database includes that data records are regularly archived and reorganized (statistics, reports, messages etc.). The involved process has direct impact on the size of the AE database and positively affects the performance of your AE system.
For maintaining your data records, you can either use the utilities or partitioning with ILM. If you are not sure which method to use, you can compare the benefits of both methods.
Use Utilities when the following criteria apply:
-
You use one of the following databases:
-
MS SQL Server
-
Oracle
-
DB2
-
-
Low maintenance efforts are more important than keeping performance high during maintenance runs
With large amounts of records, the maintenance run can burden the AE system.
-
Your database is small
-
You want to configure clients individually
-
You want to keep the last n data records per object
-
You want to delete the reports before the execution data
Use ILM when the following criteria apply:
-
You use one of the following databases:
-
MS SQL Server
-
Oracle (Enterprise Editions with Partitioning Feature)
-
-
Keeping performance high during maintenance runs is important
ILM achieves short maintenance runs that are almost independent from the amount of data.
-
Your database is big
-
You want to keep the same configuration for all clients
-
You do no t want to archive data records, since partitions can be deleted quickly and easily
-
Keeping the last n data records per object is not necessary
-
You want to keep bot reports and execution data.
Reports are reorganized together with the corresponding execution data records because they are both in the same partition.
It is still necessary to run the utilities to reorganize object versions and deleted objects as they are not covered by partitioning with ILM.
Database Prerequisites for ILM
MS SQL and Oracle require additional permissions to work with ILM (Information Lifecycle Management):
-
MS SQL
- SQL Server requires the VIEW SERVER STATE permission
- SQL Database requires the VIEW DATABASE STATE permission in the database
-
Oracle requires the permission on USER_OBJECTS
See also: