IIQ: HA options for IIQ database

IdentityIQ (IIQ) IIQ Discussion and Questions
1

Which IIQ version are you inquiring about?

8.4

Is it supported to run IIQ database on a Microsoft SQL Server AlwaysOn installation?

If not, what is the preferred HA alternative?

/Andreas

2

hi @andkar01

IdentityIQ doesn’t officially support SQL Server AlwaysOn Availability Groups, but it can run in such environments if configured correctly—especially the JDBC connection for failover.

For HA, common alternatives include SQL Server clustering or mirroring, depending on your infrastructure and recovery goals.

Hope this helps

Does SailPoint IIQ support Always ON Multi-Subnet? - IdentityIQ (IIQ) / IIQ Discussion and Questions - SailPoint Developer Community

3

Hi,

Thank you for your reply.
Can you elaborate on the following.

”but it can run in such environments if configured correctly—especially the JDBC connection for failover”

Regards

Andreas

4

hi @andkar01

Thanks for following up.

When using SQL Server AlwaysOn with IdentityIQ, the JDBC connection string must be configured to support failover across multiple subnets. This typically involves using parameters like multiSubnetFailover=true and specifying the availability group listener in the connection URL.

Proper configuration ensures that IdentityIQ can reconnect seamlessly if the primary replica fails over to a secondary one.

5

Hi @haideralishaik ,

I found the following information

”Only “High Performance” (asynchronous) mirroring mode is supported for use with IdentityIQ. The “High Safety” (“synchronous”) mode of SQL Server mirroring is not a supported configuration for use with IdentityIQ. The “High Safety” mode causes SQL Server to operate in a 2-phase-commit type of operation that is shown as not-supported in the following guide: (Recommended IdentityIQ Deployment Architectures ).”

Is this still correct?

Do we have any updated official documentation from sailpoint?

Regards

Andreas

6

Yes, the guidance you found is still correct. SailPoint IdentityIQ supports only “High Performance” (asynchronous) mirroring mode—not “High Safety” (synchronous) mode—for SQL Server mirroring.

Here’s the latest clarification based on current SailPoint documentation:

  • “High Safety” mode is not supported because it introduces a 2-phase commit behavior that can interfere with IdentityIQ’s transaction handling and performance expectations.
  • The official SailPoint guide on Recommended IdentityIQ Deployment Architectures
    still reflects this limitation.
  • Additionally, the SQL Server Mirroring Configuration Guide reinforces the need for asynchronous mirroring and highlights the importance of using READ_COMMITTED_SNAPSHOT isolation for compatibility and performance.

As of now, no updated documentation has reversed or expanded support for synchronous mirroring. If SailPoint updates this guidance in future releases, it will likely be reflected in the Compass community or official release notes.

7

Microsoft states the follwing for asynchronous database mirroring
*
”This feature will be removed in a future version of SQL Server. Avoid using this feature in new development work, and plan to modify applications that currently use this feature. Use Always On availability groups instead.”*

If i am not mistaken asynchronous mirroring always comes with the downside of potential dataloss in a failover scenario.

Regards

Andreas

8

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.