Question
Nationwide Building Society
GB
Last activity: 10 Jan 2024 10:39 EST
Deployment takes more time after DB upgrade
Dear Team,
Kindly advise on the below.
We are using on-premise Pega Smart Dispute application on 8.8. We have recently upgraded our on-premise database from SQL 2014 to SQL 2019. Our current SQL DB has 4 nodes, one primary, two secondary synchronised, one secondary non-synchronised.
When we upgrade the smart dispute product from 7.41 to 8.8.2, we have observed that the time taken is more since the changes are getting updated into Primary node and as well as two secondary synchronised nodes.
Is there any guidelines on how to avoid or minimise the delay?
One option is to make the secondary nodes non-synchronised before the deployment and revert it to synchronised after the deployment. Is this a safe consideration?
Are there any other options recommended? Please advise.
Thanks for your kind support.
Regards,
Guhanathan Vijayanarayanan
Accepted Solution
Updated: 10 Jan 2024 10:39 EST
Pegasystems Inc.
IN
@GuhanathanV4521, The approach mentioned above is a safe is approach and can be followed "One option is to make the secondary nodes non-synchronised before the deployment and revert it to synchronised after the deployment"
Accepted Solution
Updated: 10 Jan 2024 10:39 EST
Pegasystems Inc.
IN
@GuhanathanV4521, The approach mentioned above is a safe is approach and can be followed "One option is to make the secondary nodes non-synchronised before the deployment and revert it to synchronised after the deployment"