If you implement database partitions, you will typically need to run partition-based purges. But unlike the infrastructure-based purges described in this chapter, partition-based purges may not automatically delete the corresponding blob files.
Specifically, if you have separate database accounts for the primary user and schema owner, blob files for expired events are not automatically deleted. Therefore, to ensure that blobs are correctly deleted, you can either use a custom SP to invoke partition-based purges when an infrastructure-based purge runs, or you can use a third party scheduler. The recommended procedure depends on whether the primary user also owns the database schema:
You need to implement a custom SP to execute the wgn_roll_partitions procedure.
We recommend you use a third-party scheduler to run each step in the purge procedure.
If using a scheduler is not practicable, you need to implement a ‘no operation’ custom SP—this will prevent infrastructure-based purges from trying to delete the corresponding event records in the CMS database. This is necessary because these records may have been already removed by a partition-based purge.
|
Copyright © 2014 CA.
All rights reserved.
|
|