Database Purging or Clean Up Guidelines

Order Management System

OMS is provided with a purge script that can be used to clean up data about orders that are in a certain state, in a given date range. This can be used to purge order data at regular intervals and can also be run while the system is processing new orders, thus avoiding the need for an outage.

However, purging completely deletes the data about orders and associated objects such as plans, plan items and UDFs. If any of this information needs to be kept, then consider implementing an archiving strategy, where data is not purged, but copied to an archive. This will require some custom development.

Ensure that the business requirements around logging and archiving are properly captured and analyzed.

TDS and Orchestrator

Both these components can be configured to self-clean when an order reaches an end-state. Use these features to avoid having to cleanup TDS and Orchestrator. OMS should be seen as the database of record for orders and plans, and the backing stores for Orchestrator and TDS should just be for dealing with data about orders that are in-flight.