Johnson Controls P2000 - Chapter 3: Merging Data between Sites; Merging Data between Sites

24-10515-21 Rev. – 3-1
Chapter
3
This document contains confidential and proprietary information of Johnson Controls, Inc.
© 2010 Johnson Controls, Inc.
MERGING DATA BETWEEN SITES
To establish the subscription of a P2000 regional server to a P2000 central server, the data
currently stored within the P2000 databases needs to be backed up and incorporated into the
P2000 central server.
This is mandatory, as all data in the regional server will be deleted and partially re-initialized
with the current contents of the P2000 central server database.
MS SQL Server’s Database replication requires this action to ensure that the database tables
and contents of the P2000 central server and the P2000 regional server are synchronized.
NOTE
It is strongly recommended that all P2000 servers in the P2000 Enterprise
Configuration system use the same version of the Microsoft SQL Server.
This chapter outlines a procedure to move the most important configuration information
from the P2000 regional server into the database of the P2000 central server.
The data recorded in tables associated with the following publications will not be
maintained:
 FDA
 BadgeImages FDA
 Xaction
 Audit
 Alarms
It is therefore mandatory that you make a database backup of the P2000 regional server
before the subscription is established. Using P2000 utilities, restore this backup as
PegasysBackup database on the regional and the central servers. Once restored on the
regional server, you can run standard P2000 reports against this database.
MERGING DATA BETWEEN SITES
This section outlines the steps required to merge the data between the P2000 regional server
and the P2000 central server: