MSSQL In place upgrade with AOAG 2017 to 2019
search cancel

MSSQL In place upgrade with AOAG 2017 to 2019

book

Article ID: 195278

calendar_today

Updated On:

Products

CA Process Automation Base

Issue/Introduction

Is an in-place upgrade from an older MS SQL with SQL Always On to a later version of MS SQL with SQL Always on supported with ITPAM?

Environment

Release : 4.3 SP05 and higher

Component : Process Automation

Resolution

The short answer is yes, this is fully supported with ITPAM.

We have tested ITPAM with SQL AOAG (Always On Availability Group) in place upgrade in-house and below are the observations and summary of testing.

Installed ITPAM 04.3.05 cluster with SQL AOAG Database (2017). Provided Availability Group Listener for ITPAM Database connection
Verified that ITPAM is working fine with AOAG switching (with manual failover).

Now upgraded SQL Server to 2019 for both the SQL nodes.

ITPAM is working fine even after SQL upgrade to 2019 and also during AOAG switching (with manual failover) without any issues 

Additional Information

Please note that there can be downtime to ITPAM during SQL in place upgrade.This can be avoided by following recommended steps during SQL upgrade without application downtime.
But, overall ITPAM will not be affected as long as the SQL endpoint is up and running (before , during and after the upgrade) .