How to prevent unwanted sync changes in 9.2 upgrade

  • Updated

When upgrading to 9.2, UTC conversion is run on almost every row in the database. Since the conversion changes every row, eSync will take that into account on the next sync. If you have conflict resolution(see your sync profile) with remote set to win, this could mean that old content will never be overwritten on the destination side of the sync. New content could still sync to the destination, but any changes on the remote side prevent old content from moving.

  1. Before upgrading the sites and databases do one last sync. Cease content editing until the steps are completed.
  2. Backup the sites and databases to be upgraded.
  3. Run the site setup utility on your sites. Only upgrade the sites; make sure to cancel when it gets to the database update.
  4. Run this SQL on both the sending and receiving databases. This disables changes to the tracking changes when you modify content and other Ektron tables.

    EXEC sp_MSforeachtable @command1="ALTER TABLE ? DISABLE TRIGGER ALL"
    go

  5. Run UTC conversion exe on both databases.
  6. Check the datetime of both databases using this command(make sure nothing was updated).

    select content_id,last_change_datetime from content_tracking order by last_change_datetime desc

  7. Edit "C:\Program Files (x86)\Ektron\CMS400v9X\Utilities\SiteSetup\Database\cms400_upgrade_data.sql" and comment out the following lines.

    EXEC sp_MSforeachtable @command1="ALTER TABLE ? ENABLE TRIGGER ALL"
    GO
     
  8. Run the site setup database update
  9. Once complete check the triggers and disable them if enabled. 
  10. Check the datetime of both databases using this command(make sure nothing was updated).

    select content_id,last_change_datetime from content_tracking order by last_change_datetime desc

  11. Run a full sync with remote set to win.
  12. Check the datetime of both databases using this command(make sure nothing was updated).

    select content_id,last_change_datetime from content_tracking order by last_change_datetime desc

  13. Check the triggers to see if they are enabled. Click on the content table, click triggers, and look for a lightning symbol to show it's active and a red symbol to show it's inactive.

  14. If inactive, run this command.

    EXEC sp_MSforeachtable @command1="ALTER TABLE ? ENABLE TRIGGER ALL"
    go

  15. Subsequent syncs should work as they did before the upgrade.