Currently we storeProvisioningTransaction for 1 month. We want to know what are the downside of increasing it for 1 year

IdentityIQ (IIQ) IIQ Discussion and Questions
1

Which IIQ version are you inquiring about?

[8.5p1]

As per audit requirement, we are looking to increase retention period of ProvisioningTransactions from 1 month to 12 months. I am checking to see if anyone has faced similar issue and the impact on the performance, logs, search, etc.

Thank you

2

@nthapaG We’ve been storing ProvisioningTransactions for 3 months and haven’t seen a significant impact on other module performance. However, increasing the retention period from 1 month to 12 months does come with some considerations you should be aware of:

  1. Database Growth: ProvisioningTransaction records are one of the primary contributors to database size growth in IIQ. Extending retention to 12 months will cause the spt_provisioning_transaction table to grow substantially — roughly 12x your current volume. Make sure your DBA team is prepared for the additional storage requirements and monitors tablespace/disk usage accordingly.

2. Search & UI Performance Searching provisioning transaction history through the IIQ UI or API will become slower as the number of records increases. If your team frequently searches or filters provisioning transactions, expect longer query response times.

3. Performance Maintenance Task Duration The IIQ Performance Maintenance task (or any custom pruning task) that cleans up old ProvisioningTransaction records will take longer to execute, since it will be processing a much larger dataset during each run.

4. Backup & Restore Times Larger database size means longer backup windows and restore times, which could affect your disaster recovery SLAs.