Best Practices for Upgrading Decisions v8 Database from SQL Server 2017 to SQL Server 2022

MalikB_Decisions

We’re migrating to Decisions v8, currently running on SQL Server 2017. Our database team plans to upgrade all SQL servers to SQL 2022. Is it safe to do an in-place upgrade from SQL 2017 to SQL 2022 with Decisions v8, or should we create a new SQL 2022 instance and restore the database? Will we need to reinstall Decisions v8 after the upgrade, and are there any backup or restore considerations we should be aware of?

MalikB_Decisions

It is generally safe to perform an in-place upgrade from SQL Server 2017 to SQL Server 2022 for Decisions v8, as Decisions supports SQL Server 2017 or newer. You do not need to reinstall Decisions v8 after the SQL upgrade.

However, as a best practice, consider spinning up a new SQL Server 2022 instance, restoring your Decisions database, and testing Decisions v8 in this environment. This approach allows for easier rollback if any issues occur.

Key Recommendations:

1. Back up your Decisions database, Settings.xml, Keys.dat, and FileStorage folder before making any changes.
2. Test thoroughly after the upgrade or migration to ensure all functionality works as expected.
3. No special backup/restore issues are expected when moving from SQL 2017 to SQL 2022 but always validate your backups and test the restored environment.