Page Comparison

...

Overview

Though the ACM user guide only gives recommendation This guide provides recommendations for minimum SQL Merge Replication that will to keep your ACM working in case of a failover you may do a more through fail-over.  More can be done using replication. Below is an outline of our the core tables to help guide you in setting up your system.

...

The following tables are treated as temporary tables and the data is constantly being shuffled around. These tables Table data are is either only for calculation and/or movement that can be regenerated on the flydemand. These tables should NOT be replicated.

...

The next set of tables are the tables that contain the data that is necessary for starting ACM. If you want a failover fail-over that starts up with current data and last known item data, then these are REQUIRED.

tblArchivePosition
tblItems
tblObjects
tblProperties
*tblServerDirectory : this is only required if you are using the Server Directory function

...

Historical EFM data is stored in multiple tables. If you replicate your EFM data, you may also want to replicate your the position of your publisher pointers , so that you do not accidental republish to prevent accidental republishing of your data on failoverfail-over.

tblArchiveRecords
tblCommStats
tblLiquidRecords
tblMeterRecords
tblMeterRecordsHistory
tblPublishedRecord
tblPublishPosition

...

The below history tables contain none no EFM records. They log changes, actions, and errors. Replicating them is optional.

...

The below history tables contain information to help decode the records and know what version store the database you are atversion information. They do not change between builds.

...