SailPoint Database version upgrade from SQL server 2019 to 2022

Which IIQ version are you inquiring about?

IdentityIQ 8.4p2

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.

Database team is planning to upgrade the SailPoint SQL server from 2019 to 2022. As per the SailPoint IIQ 8.4 installation guide, SQL 2022 is a supported version.
However, I just need clarification of few queries:

  1. Have anyone done SQL upgrade from 2019 to 2022 in their SailPoint env.
  2. Did you face any challenges during upgrade ?
  3. Is there anything we need to take care of while DB team is performing the upgrade.
  4. Any manual actions needed by SailPoint team ?

Thanks & Regards,

Milina Phalke

@milinaphalke With regards to 2022, i don’t think you’ll face any compatibility issues. You might want to review the jars, review any DB jobs configured if they can work in 2022 version.

If you have multiple environments, you can start with the lower environments, do the upgrade and execute the modules in IIQ to make sure they all are working fine.

hi @milinaphalke
Yes, SQL Server 2022 is supported with IdentityIQ 8.4p2, so from a compatibility standpoint you should fine.

To your questions:

1. Has anyone done this upgrade?
It’s generally a straightforward in‑place DB upgrade.

2. Challenges faced?
No major IIQ‑specific issues are typically seen. Most problems (if any) are standard SQL upgrade items like:

  • Compatibility level changes

  • Query plan differences (rarely impacts IIQ)

  • Post‑upgrade index/statistics health

3. What to take care of during DB upgrade?

  • Ensure a full DB backup before the upgrade

  • Verify SQL compatibility level after upgrade (keep it aligned with SQL 2019 initially, then raise later if needed)

  • Confirm SQL Agent jobs, maintenance plans, and permissions remain intact

  • Validate JDBC driver version (Microsoft driver compatible with SQL 2022)

4. Any manual actions needed from SailPoint team?

  • Generally no application redeploy is required

  • Run a quick smoke test post‑upgrade:

    • Login

    • Aggregation

    • Provisioning

    • Certification access

  • Monitor logs for any SQL warnings or performance anomalies

Overall, if this is a DB‑only upgrade, SailPoint involvement is minimal and mostly validation-focused.

Thanks @neel193 @haideralishaik for your inputs.

Yes, we will be taking a backup. In our case, it is completely a new WINDOWS server where SQL server 2022 is installed and SailPoint IIQ will now point to new servers.

We are seeing performance issue while running the Database Performance task. Support team suggested few things, but DB team mentioned its already in place.

We are currently using SQL server driver mssql-jdbc-13.2.0.jre11.jar and the latest driver available is mssql-jdbc-13.4.0.jre11.jar.
Other env details are as follows:

JAVA version: open JDK version 11.0.13
App server version: 9.0.56

Do you recommend to upgrade the driver to latest ?

Thanks & Regards,

Milina Phalke

hi @milinaphalke
Thanks for sharing the details.

Yes, I would recommend upgrading the Microsoft SQL JDBC driver from 13.2.0.jre11 to 13.4.0.jre11, especially since:

  • You have moved to a new SQL Server 2022 instance

  • Your experiencing performance issues (DB Performance task is a good indicator)

The newer JDBC drivers include:

  • Better SQL Server 2022 compatibility

  • Performance optimizations

  • Bug fixes related to connection handling and metadata queries

With Java 11 and Tomcat 9, upgrading the driver is low-risk and fully supported.

Suggested approach:

  1. Test the new driver in a lower environment first

  2. Replace the JAR in Tomcat’s library

  3. Restart the app server

  4. Re-run the Database Performance task and compare results

No other SailPoint changes are typically needed. If performance improves, you’re good to roll forward. If not, it at least helps rule out the JDBC layer and focus further on SQL tuning (indexes, IO, CPU, memory).

@milinaphalke Could you please elaborate what issues your are facing with DB performance task?

@milinaphalke - Hi Milina,

I think the overall upgrading to SQL Server 2022 for IIQ 8.4p2 is a well-supported path. The key to success lies in planning, thorough preupgrade backups, careful post-upgrade validation (especially of compatibility levels and JDBC drivers), and comprehensive testing of your IdentityIQ environment. By following step by step approach, can confidently move forward with your database upgrade.

Check the → IdentityIQ 8.4 Supported Platforms

Regards,

Kannan

Hi
Following points you might consider.

  1. Make sure your SQL jars are updated in IIQ envrionment.

  2. If you have any JDBC connector using MSSQL DB then plan for some testing before hand to make sure you don’t have any suprises in production.

  3. Plan for some overall regression like 1-2 test case for each feature.

  4. Ask DB team to take back up before performing actual upgrade.\

  5. Make sure new DB version is compatible with IIQ version you are running.

No specific config changes are required unless they are building a brand new DB server for you

Hi @pradeep1602,

New windows servers are procured and SQL server 2022 is freshly installed on it and then the data is copied from old database server (SQL server 2019) to the new database (2022) on new server.

I see you mentioned “No specific config changes are required unless they are building a brand new DB server for you.” So, in our case it is a brand new DB server. So, does it mean any specific config changes are needed?

Thanks & Regards,

Milina Phalke

Hi @milinaphalke
Yes in that case you need to update your iiq.properties file to point to new DB servers.

Also if any coding is done inside or outside IIQ which is using DB server details must be updated accordingly.

No specific code in Rules/workflows needs to be updated.

@milinaphalke Major work is at DBA end. As you are using Microsoft SQL, you might want to check how DR setup is configured, normally you setup Always On Availability which keeps your servers synchronized. If there are any DB jobs you have written, you need to update them as well.

On IIQ front, you need to update iiq.properties if there are any change to the DB URL, other wise that’ll not needed.

Based on your previous posts, you mentioned that you decided to go for upgrade due to some performance issues. Could you please specify what are those?

Thanks @haideralishaik We have placed the latest sql server jar (mssql-jdbc-13.4.0.jre11.jar), still the DB performance test results are not within the benchmarks given by SailPoint.

Hi @neel193 I was referring to the OOB task “Database Performance Task” which runs DB queries with 1K, 4K and 8K dataset.
https://community.sailpoint.com/t5/Other-Documents/IdentityIQ-Database-Performance-Tests/ta-p/78060

@milinaphalke I am still curious.. This task helps you figure out if you have issues with your DB transactions via IIQ but this should not be the only factor to decide if you need to upgrade or not. Please evaluate carefully to decide if upgrade is really going to help you with your concerns or not.

Could you please specify what all additional things you have tried so far.

Hello @neel193 Sorry for the confusion if any due to above communication. DB version upgrade from 2019 to 2022 is not done by SailPoint team. It is an intiative by DB team where they are upgrading all their SQL server 2019 env to SQL server 2022. We as SailPoint team are just performing testing to see there is no impact on SaiPoint application.

@milinaphalke Thanks for clarifying. Could you please re-run the DB task and share the result here?

Hi @neel193

@milinaphalke From the screenshots, it looks like in v2022 it is worse than v2019. Do you know other than upgrade, if there is any other change being made to infra: at application server, DB server, network, firewall, or any other thing?

Hi @milinaphalke We had faced similar issue in past and raising a sailpoint support helped us.

They helped us optimize some parameters to improve performance.

Would recommend you to reach out to Sailpoint Support

Hi @pradeep1602
I had already raised a ticket with support team, but they suggested tuning on DB end.

No tuning suggested in SailPoint except using the latest ms-sql driver jar which we did.

Can you please share what tuning was suggested to you?