Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

 Table Of Contents

Overview

Though the ACM user guide only gives recommendation for minimum SQL Merge Replication that will keep your ACM working in case of a failover you may do a more through replication. Below is an outline of our core tables to help guide you in setting up your system.

Temporary/Data Tables

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

JobSchedules
ScheduledJobs
ScheduledJobSteps
tblArchiveStaging
tblCommStatsStaging
tblDailyRecs
tblDailySummary
tblHourlyRecs
tblHourlySummary
tblGcWritePending
tblItemStaging
tblObjectId
tblPubStaging

Required Data Tables

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

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

Historical EFM Data Tables

Historical EFM data is stored in multiple tables. If you replicate your EFM data, you also want to replicate your position of your publisher pointers, so that you do not accidental republish your data on failover.

tblArchiveRecords
tblCommStats
tblLiquidRecords
tblMeterRecords
tblMeterRecordsHistory
tblPublishedRecord
tblPublishPosition

History Tables

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

ErrorLog
ScheduledJobsHistory
tblArchiveExec
tblCommandLog
*tblChanges : note this table is auto-populate on a trigger from tblObjects and tblProperties
tblGcWritePendingAudit
SchedulingErrors

Lookup Tables

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

tblDbVersion
tblGcWriteResultLookup
tblLookupCommType
tblLookupPeriod
tblLookupPollFailCode
tblLookupPollStatus
tblLookupRefProp
tblLookUpTypeID

  • No labels