1191 How do upgrades to the SES database during an SES upgrade get propagated to a second non-clustered fail-over SES Database Server

  • Updated on Feb 6, 2026
  • 1 minute(s) read
  • VN
 Prev Next

How do upgrades to the SES database during an SES upgrade get propagated to a second non-clustered fail-over SES Database Server?


How do upgrades to the SES database during an SES upgrade get propagated to a second non-clustered fail-over SES Database Server?

Scenario:  A customer has SQL Database Replication setup, so that changes to Server A are propagated to Server B.  These databases are NOT in Cluster Mode - they're in a Publisher/Subscriber mirror relationship. The recovery scenario here would be that if Server A fails or goes down, the SES admin must manually make the SES DB hosted on Server B become the active version, and start SDConnex to point to the database on Server B.

The questions relating SES version updates in this scenario are:

  • Does the SES Admin need to individually upgrade the SES Database both on Server A and on Server B?
  • OR... will upgrading the SES database on Server A cause automatic propagation of all database (schema, table, column, index, trigger, stored procedure, etc) changes to the parallel database hosted on Server B (e.g. will online publish/subscribe changes automatically ensure the SES Database on Server B matches the database on Server A?)

Please read this Microsoft SQL article to understand the considerations for this scenario: 
https://msdn.microsoft.com/en-us/library/ms151870.aspx 

BEST PRACTICE RECOMMENDATION: 

Rather than leave to chance the poissiblity  For complete certainty (as well as protection against future SES changes that might make invalid a recommendation that all such changes would automatically propagate), the easiest and most certain solution would be to:

  1. Stop the mirroring between the primary and secondary SES server(s), prior to upgrading the SES database on the Primary Database Server
  2. Start the SES Upgrade, and allow the upgrade to complete all its changes to the SES Database schema (tables, columns, indexes, stored procedures, triggers, etc).
  3. Backup the now-upgraded SES database on the primary server
  4. Restore the backup onto the mirror site (secondary) server(s)
  5. Resume mirroring, and start SES Services (ADSync, SDConnex) and resume use of the SES Console...

... after which all future database changes will automatically be propagated from the primary server to the secondary server(s).