Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support for assistance.
How to combine multiple Continuum DBs into one DB
Multiple Continuum site databases need to be combined into a single site database
Guideline for combining Multiple sites to one Database
Executing this procedure requires a technician who thoroughly understands Continuum and how it works with SQL Server.
This procedure does not encompass BACnet controllers.
There is a multitude of decisions related to efficiencies and site preferences that are not documented here. The following procedure is intended for use as a guideline for combining multiple databases.
This work must be done offline on a development database and validated on a test bench before
Note:Before proceeding with this procedure you must do the following.
- Backup the Continuum database in SQL.
- Backup all the files and folder structure under New Graphic Files. Note that these files may be on the SQL Server or elsewhere on a mapped drive.
- Back all Cyberstation Profiles.
Steps 1 – 11 must be done before any of the site exports are done.
- All sites must have the same revision software and CX firmware. NO EXCEPTIONS!
- Make sure that all the Alarm Enrollments and Event Notifications have unique names between all sites as these will wind up together in a single database.
- Make sure that all the Graphics in the Root directory have unique names between all sites.
- Make sure each Schedules in the Root directory has a unique name across all sites.
- Make sure each Custom ListViews in the Root directory has a unique name across all sites.
- Make sure each Groups in the Root directory has a unique name across all sites.
- Make sure each Reports in the Root directory has a unique name across all sites.
- Once steps 1-5 are completed, export each class in the root individually.
- Import files from step 6 into the new site
- The Local Site name on all the sites that will be combined must be named LocalSite.
- All workstations must have unique names and ACC IDs between the sites.
- All CX, ACX and BCX controllers must have unique names and ACC IDs between the sites.
Note: The safest way to do steps 9 & 10 is to create a new controller in offline mode with the changed ID, then drag and drop copy from the original controller to the new controller.
Panels, reports, and programs then must be edited to bind to the new controller.
Another way to merge the panel, reports, and programs that are in the root is to copy all the panels, programs, and reports to their corresponding controller then export the controller. Doing this will keep all the bindings linked. Then once the controller is imported into the merged database they can be copied back up to the root.
- All Commports on all controllers and workstations must be named Comm1, Comm2, etc…
- Each site must have the default “ACC” user and password.
- All graphic files (.pin) under the New Graphic Files folder must have unique names between the sites.
Merging the databases
- Install a standard multi-user Continuum system being sure to size the database big enough to accept all the other databases combined into one database.
- After a clean installation is done, shut down the new workstation and the SQL server.
- Copy the empty database files to an area where they won’t get corrupted.
- Do a complete site export from each of the sites that will be combined.
- Back up all the Graphic files (.Pin) files from the site so that they can be transferred to the new server.
- Copy all the backed up Graphic files (.Pin) from each site onto a New Graphics Files folder in the location of choice. Note these files can reside on the SQL server or elsewhere on a mapped drive.
- Import each of the site text exports from the old systems into the new system.
- After each import check to make sure that each import went cleanly.
- Check all the Graphics, Programs, Alarm Enrollments, and Event Notifications to make sure that all the links were made during the import process.