Hi All, in my case
the primary key sequence for broad Log schema is near to exhaustion exhaust
please help to provide a monitoring techincal workflow if anyone created to monitor the sequences
Hi Shrutii,
I'm not sure about a specific workflow to monitor the sequences. However, I recommend the two articles below to ensure that sequence hygiene practices are followed.
Unless you are processing a massive amount of data daily, with best practices being followed, it should be pretty hard to hit sequence exhaustion.
Specifically, you should:
1) Limit the amount of log data that is being kept to the bare minimum (reduce the purge range in the deployment wizard)
2) Ensure that the DB Cleanup workflow is running daily and completed, as it removes old data and frees up IDs
3) Do not use the out-of-the-box xtkNewID sequence; configure custom sequences (especially for heavily used tables such as the broadlogrcp table)
4) Do not share sequences
5) If you are still churning through IDs, you may want to consider implementing negative ids which effectively doubles the amount of IDs available but can have drawbacks.
Data model best practices
Office Hours which covers handling sequences
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.