Hello fellow members,
I am seeking your help regarding one persistent issue we are facing with our IIQ implementation.
Every weekend when the full identity refreshes and other major tasks run, tempdb tends to get full on most weekends and we have to manually restart the sqlserver services to free it up. What can I do to fix this?
Apart from pesky IQService that needs it's own server, it feels very low effort in comparison to conventional deployments.
How are other people experiencing this?
📍 Location: Irving, TX / Iselin, NJ / Charlotte, NC (3 Days Onsite)
📄 Type: Long-Term Contract (W2/C2C | No GC on C2C)
🎯 Experience: 10+ Years
🏦 Banking Domain Experience: Must
We are looking for experienced SailPoint IIQ Architects with strong background in large-scale enterprise implementations.
𝐌𝐚𝐧𝐝𝐚𝐭𝐨𝐫𝐲 𝐒𝐤𝐢𝐥𝐥𝐬:
• SailPoint IIQ (Architecture, Design & Implementation)
• Large-scale implementations (100k+ users, 1000+ apps)
• Java / J2EE & custom connector development
• Integrations (AD, Workday, Entra ID, SAP, Oracle, etc.)
• RBAC, SoD, High Availability & DR
⚠️ 𝐈𝐌𝐏𝐎𝐑𝐓𝐀𝐍𝐓 – 𝐏𝐋𝐄𝐀𝐒𝐄 𝐑𝐄𝐀𝐃 𝐂𝐀𝐑𝐄𝐅𝐔𝐋𝐋𝐘 𝐎𝐍𝐋𝐘 𝐀𝐏𝐏𝐋𝐘 𝐈𝐅 𝐘𝐎𝐔 𝐇𝐀𝐕𝐄 𝐒𝐓𝐑𝐎𝐍𝐆 𝐇𝐀𝐍𝐃𝐒-𝐎𝐍 𝐒𝐀𝐈𝐋𝐏𝐎𝐈𝐍𝐓 𝐈𝐈𝐐 𝐄𝐗𝐏𝐄𝐑𝐈𝐄𝐍𝐂𝐄 𝐀𝐍𝐃 𝐑𝐄𝐂𝐄𝐍𝐓 𝐁𝐀𝐍𝐊𝐈𝐍𝐆 𝐃𝐎𝐌𝐀𝐈𝐍 𝐁𝐀𝐂𝐊𝐆𝐑𝐎𝐔𝐍𝐃.
📩 Please comment "interested" or DM me.