Previous Topic: Overriding the Default Retention PeriodNext Topic: Public SPs

Database Guide › Infrastructure-Based Purging › Purges and Stored Procedures

Purges and Stored Procedures

For both SQL Server and Oracle databases, CA DLP supports two types of stored procedures (SPs):

Public SPs

These are provided by CA DLP and provide default purging functionality. Public SPs can be overridden.

Custom SPs

These do not exist by default, but can be created by DBAs on demand.

The diagram below shows SPs are invoked when the CA DLP infrastructure runs a database purge:

database purges process

When the CA DLP infrastructure runs a database purge, it does the following:

  1. It checks for, and invokes, any pre-purge SPs.
  2. The Stub SP checks for, and invokes, a Custom SP.
  3. If no Custom SP is defined, the Stub SP invokes the Default SP containing the default purging functionality.
  4. When the purge completes or terminates, the infrastructure checks for, and invokes, any post-purge SPs.