[8.3p4]
[We have over 54 million ProvisioningTransaction records, some of which goes back to 2017. My question is twofold. Does having all of those on the DB cause a performance issue? Secondly, is there any negative fallout from deleting all of these old records? Finally, they seem to be unconnected with any outstanding Task or WorkflowCase.]
yes, it will impact the performance while searching the provisioning trasnsaction history.
better to prune like only maintain data for last 2 years. rest you can move in some other db if needed in future.
some doc that will be helpful for pruning Data pruning best practices - Compass
Thank you for your quick answer! We are moving forward with our plan.
I do have a follow-up question here. Many of our records are “stuck” in a pending status, again from years ago. Could these be slowing down our system? Do they get looked at as a potential for execution? We are hoping to help (even a little bit) with our performance.
@s_scovill thanks for follow-up, IdentityIQ maintains a provisioning queue where each provisioning transaction is stored with a status (e.g., pending, committed, failed). The Provisioning Engine periodically scans this queue to: Retry failed or pending transactions. Trigger retries if the connector or target system becomes available again.
better to prune on certain days like after 365 days. if you need then you can get from backup db instance.