Which IIQ version are you inquiring about?
[Replace this text with your version of IIQ. The more specific you can be (7.1, 8.3, 8.X), the more people can help. If you do not know, put Unsure.]
Identity IQ 8.3 p3 using Microsoft SQL server
Please share any images or screenshots, if relevant.
[Please insert images here, otherwise delete this section]
Please share any other relevant files that may be required (for example, logs).
[Please insert files here, otherwise delete this section]
Share all details about your problem, including any error messages you may have received.
[Replace this text with the problem that you are facing]
Hi All,
Facing a recurring issue with the IdentityIQ/SQL Server TempDB—it keeps growing and hitting full capacity roughly every one - two days. This has been happening consistently over the past few weeks.
After discussions with our DB team, found that numerous idle sessions are lingering in the system for more than 6 hours. The recommendation from the DB side is to clear these sessions, but the challenge is that not able to map these sessions back to specific SailPoint IdentityIQ queries, tasks, or workflows.
Has anyone dealt with a similar situation? Specifically:
- How can we trace IdentityIQ queries back to the workflows or tasks that are generating them? (The queries that we can get from DB team are not understandable)
- Are there any tools or logs within IdentityIQ that can help identify long-running or idle processes?
- What’s the best way to monitor and clean up these sessions to prevent TempDB overload?
Have gone through this article in community page - Growth of tempDB in Microsoft SQL server - Compass
Any insights or suggestions would be a huge help. Thanks in advance!