Purge Notifications in Clarity - Best Practices

Products

• Clarity PPM SaaS
• Clarity PPM On Premise

Issue/Introduction

What are the best practices to ensure the Clarity system is stable and CLB_NOTIFICATIONS table is performing optimally. How to schedule the Purge Notifications job? 

Also applicable when you are seeing slowness on CLB_NOTIFICATIONS table and many million records in this table

Environment

All Supported Clarity Releases

Resolution

Regular Maintenance Best Practices

1. Connect to Clarity - Classic - Reports and Jobs 
2. Schedule the job Purge Notifications to run regularly (at least once weekly is recommended) 
3. You can add multiple different jobs per Notification Type or use the same job instance
4. Ensure all the Notification Types are covered and your job is scheduled regularly to deal with any extra records

Addressing Large Backlogs (Over 1M Records)

If you have not run this job for a long time and have over 1M records in CLB_NOTIFICATIONS: 

1. Collect information from DBA on amount of records per date per Notification Type in CLB_NOTIFICATIONS 
2. Using this data as parameters, ensure you batch the job to remove about 100K at a time to avoid load on BG
3. You can schedule the job on a lower environment and check for any performance impacts before running for the same amount of records on Production
4. Avoid running the purge job during work hours, schedule it outside of any important activity
5. Once you have addressed the large overheads, schedule the job regularly as per the Regular Maintenance Best Practices above