SQL DB in Server Upgrades Best Practices
Schema Upgrade for User-Managed SQL DB
Most quarterly upgrades change the database schema to accommodate new features. A schema migration is done automatically the first time the Alteryx Server service is started after your upgrade. While this is automatic, any issues in this process prevent the Server from properly starting.
Check the Alteryx Pre-Upgrade Checks as they are the best way to ensure your SQL database schema is ready to migrate without error.
To confirm the schema migrated to the expected version after starting the Alteryx Server service, review the end of the migration log and compare it to the correct schema for your Server version: C:\ProgramData\Alteryx\Gallery\Logs\alteryx-migration.csv
For more information about SQL DB schema, check the SQL DB Schema Reference help page.
Determine if Your SQL Database Version Needs to Upgrade
The SQL DB Schema Reference lists the "Supported SQL DB Version for User-Managed Instances" for each Server version.
User-Managed SQL DB
You'll notice that multiple SQL DB versions are supported for each version of Server. Determine if you are required to upgrade your database or if it's optional.
Version Upgrade for Different Types of SQL DB
If you determine above you must or wish to upgrade your On-Prem User-Managed SQL DB, you should do so independently of your Alteryx Server upgrade. Don't upgrade both at the same time without thoroughly testing your Server after upgrading the application.
To upgrade On-Prem User-Managed SQL DB:
Stop the AlteryxService.
Back up your SQL DB.
Follow SQL’s recommendations for upgrading, which might require pit stops. For more information about SQL Server backup and upgrade, use the Microsoft documentation Upgrade SQL Server and Back Up and Restore of SQL Server Databases.
Start SQL DB.
Start AlteryxService.
Test that Server and workflows are running as expected.
For more information refer to these articles: