The Logging tab of the Service Properties dialog allows you to control the logging of replication history records and of Windows events.
The Data Replicator Control database contains statistics for all the replication events that are handled by the Replicator Service. For best performance, keep as few records in the database as meets your requirements.
The Limit Replication History Logging option determines whether replication history records are deleted when a certain number of records is reached. If you enable the Limit Replication History Logging option, set the Maximum Total Number of History Records to the maximum number of history records you want to store in the Control database. The default value for this setting is 1000 records. To keep the replication history records indefinitely, disable (uncheck) the Limit Replication History Logging option.
When the number of rows in the Control database reaches the Maximum Total Number of History Records value, the Replicator Service deletes as many records in the history table as needed to allow new replication entries to be inserted. Which records are deleted depends on which subscriptions the new log entries are for, and how many log entries for those subscriptions already exist in the Control database. If adding the new subscription log entries would exceed the value set for Maximum Records Per Subscription, the oldest records for those subscriptions are deleted. If adding the new subscription log entries does not exceed the limit for the subscriptions, the oldest records in the history table are deleted to make room for the new records.
A change to the log size setting generally takes effect as soon as you click OK. However, if you decrease the value of the setting, excess table rows will not be deleted until the next time replication event information is inserted into the Control database. The topic Viewing Statistics describes how to view the replication history for a subscription, and Deleting Statistics describes how to clear the history records for a particular subscription or group.
The default option for logging Windows events is to record the Normal Operational Level of Detail, such as when the service is started and stopped. If you experience a problem with data replications you can enable the Expanded or Maximum levels of logging to capture the following types of ODBC messages in addition to the operational details.
Expanded Warning Logging |
Logs ODBC error messages as WARNING events. ODBC errors messages can help troubleshoot insert failures, connect failures, or problems dropping or creating indexes. |
Maximum Level of Warning |
Logs ODBC information or warning status messages as INFORMATION events. ODBC information and warning messages reflect events such as database context changes, setting the default language, committing transactions, and binding packages when connections are established. |
The topic Viewing Windows Events describes how to view the Windows events that are logged. Remember to change the Data Replicator service logging level back to Normal Operational Level of Detail when you are finished troubleshooting a problem.
These options can be used to configure detailed customization of which classes of events will result in an Event Log message and/or email notification.
The available options are:
Error (Errors only)
Warn (Errors & Warnings)
Info (All)
None
EVENT CLASS |
Default Value |
Service Control |
Error |
Service Configuration |
Error |
Apply Manager |
Error |
Replicator Manager |
Error |
Schedule Manager |
Info |
Pool Manager |
Info |
License Manager |
Warn |
Network |
Info |
Diagnostic |
None |