...
| title | Table Of Contents |
|---|
...
| Table of Contents | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
Overview
Though the ACM user guide only gives recommendation for minimum This guide provides recommendations for SQL Merge Replication that will to keep your ACM working in case of a failover you may do a more through fail-over. However, more can be done using replication. Below is an outline of our 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 around. These tables data are either changing. Table data is used only for calculation and/or movement that can be regenerated on the flywhich 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 failover 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 your the publisher position of your publisher pointers, so that you do not accidental republish pointers to prevent accidental republishing of your data on failoverfail-over.
- tblArchiveRecords
- tblCommStats
- tblLiquidRecords
- tblMeterRecords
- tblMeterRecordsHistory
- tblPublishedRecord
- tblPublishPosition
History Tables
The below These history tables contain none 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 the records and know what version store the database you are atversion information. They do not change between builds, so replication is optional.
- tblDbVersion
- tblGcWriteResultLookup
- tblLookupCommType
- tblLookupPeriod
- tblLookupPollFailCode
- tblLookupPollStatus
- tblLookupRefProp
- tblLookUpTypeID