How to: Upgrade a Rollup Core environment that's using SQL Replication

Version 2

    Verified Product Versions

    Endpoint Manager 9.6Endpoint Manager 2016.xEndpoint Manager 2017.xEndpoint Manager 2018.x

    Description: SQL Replication is the new technology that Rollup Core's are using in LDMS 9.6 and LDMS 2016. Due to the way this technology works special attention needs to be given if the rollup core needs to be upgraded. It's also important to understand what happens when a client core that's using replication is upgraded.


    Replication Terminology:

    Publisher = A client core database that is sending data (through replication) to the rollup core database.

    Subscriber = The Rollup Core database.

    Schema = The database structure


    General Information: In a SQL Replication environment the database schema (structure) of all Publisher databases is evaluated at the time it's setup and configured. This is done to find the lowest version database. Database views are then created on each publisher and are used to access the data and not disturb the product tables themselves. For example: If you are rolling up the following 3 cores the LDMS 9.6 database schema will be used because it's the lowest version database. (LDMS 9.6, LDMS 2016, LDMS 2016)


    Case 1: The Rollup Core needs to be upgraded.


    Resolution: This depends on the database version of the publishers. For example if all the publishers are LDMS 2016 and the Rollup Core (Subscriber) is 9.6 then you can proceed with disabling SQL Replication and updating the Rollup Core. However, if publishers are going to be upgraded as well then they should be upgraded first with the Rollup Core upgrade happening last. The reason for this is in the General Information above. The database schema is based on the lowest database version. Upgrading children won't break SQL Replication as existing tables will continue to replicate. New tables however, won't replicate until the Rollup Core is upgraded. Once the Rollup Core is upgraded then the SQL Replication Utility (landesk.database.replication.exe) can be executed and SQL Replication can then be setup again from scratch. This will create new database views as well as generate new snapshots of all publisher databases and take into account new tables as needed.


    Case 2: Client cores need to be upgraded who are participating in a Rollup SQL Replication environment.


    Resolution: The child cores can be upgraded at will. The main concern is noted above. SQL Replication when it was setup and configured was designed around the lowest version database. SQL Replication should continue to operate but the database views on the publishers will only be replicating the older version. If the newer data is needed or after all child cores have been upgraded then the SQL Replication Utility (landesk.database.replication.exe) can be run again so that it will setup and configure SQL Replication from scratch. This will generate new snapshots of all the publishers (child cores) and start replicating new tables.