Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

titleTable Of Contents

...

Table of Contents
maxLevel3
minLevel3
typeflat
printablefalse
separatorpipe

Overview

This guide provides recommendations for SQL Merge Replication to keep ACM working in case of a fail-over; however. However,  more can be done using replication. Below is an outline of the 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 aroundchanging. Table data is either used only for calculation and/or movement that can be regenerated which is re-generated on demand. These tables should NOT be replicated.

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

Required Data Tables

The next This set of tables are the tables that contain the data that is necessary for starting ACMACM configuration, history collection sequence positions and item persistence. If you want a fail-over ACM system 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 Tables

Historical EFM data is stored in multiple tables. If you replicate your EFM data, you should also want to replicate the publisher position of publisher pointers to prevent accidental republishing of your data on fail-over.

  • tblArchiveRecords
  • tblCommStats
  • tblLiquidRecords
  • tblMeterRecords
  • tblMeterRecordsHistory
  • tblPublishedRecord
  • tblPublishPosition

History Tables

The below These history tables contain no 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 This set of tables contain information to help decode records and store the database version information. They do not change between builds, so replication is optional.

  • tblDbVersion
  • tblGcWriteResultLookup
  • tblLookupCommType
  • tblLookupPeriod
  • tblLookupPollFailCode
  • tblLookupPollStatus
  • tblLookupRefProp
  • tblLookUpTypeID