High CPU usage if History Log Limit Exceeds Number of Subscriptions (180393)
The information in this article applies to:
- Microsoft Host Data Replicator 1.0
This article was previously published under Q180393
BUG #: WINDOWS NT :174 (1.0)
SYMPTOMS
If the Replication History Log Limit Field is set to a number less than the
number of subscriptions, but greater than zero, CPU usage will increase to
100 percent. This high CPU usage will continue until the Replication
History Log Limit Field is set to a number greater then the number of
subscriptions or to zero.
WORKAROUND
To work around this problem, use a Replication History Log Limit that is
greater then the number of subscriptions. Alternatively, zero can be used
to disable the History Log.
STATUS
Microsoft has confirmed this to be a problem in the Host Data
Replicator version 1.0.
NOTE: Effective immediately, Microsoft has granted exclusive marketing and
distribution rights to StarQuest Software for Host Data Replicator 1.1, a
software utility for replicating among heterogeneous databases. Microsoft
will not be offering this product or any future versions to its customers.
StarQuest has renamed the product, StarQuest Data Replicator. Please refer
to the following link for more information:
| Modification Type: | Major | Last Reviewed: | 4/2/2000 |
|---|
| Keywords: | kbbug KB180393 |
|---|
|