We're suffering from SQL replication issues - every now and again, the replication dies, citing "General Network Error" as the cause. The first
step to sorting this is finding out when it happens, but as we only notice
it when the app that uses the database dies, this is a little problematic.
We have a network monitoring system that knows about WMI, but I have no
idea which performace counters to watch - there doesn't seem to be a handy
"number of replication erors" counter or anything of the kind. Can someone
enlighten me as to which counters we could use?
Monitoring Replication ... We're suffering from SQL replication issues - every now and again, ...replication dies, citing "General Network Error" as the cause. ... idea which performance counters to watch - there doesn't seem to be a handy ... (microsoft.public.sqlserver.replication)
General network error. Check your network documentation ... I've a merge replication over a ISDN router between two ... SQL Server 2000 databases....General network error.... (Source: MAILVXE (Data source); Error number: 11) ... (microsoft.public.sqlserver.replication)
Re: Replication - GUID:s.... ... it is not necessary to use GUID instead of ...Autonumbers as the primary key, then they will be converted to ... "random" autonumbers after applying replication....>counters - long integer. ... (microsoft.public.access.replication)
Re: ABNORMAL Transactional Replication behaviour ... Run this in the distribution database to ... If they aren't run sp_repltrans in your publication database.... Looking for a SQL Server replication book?... > assign a range to this counters and the replication blocks itself before ... (microsoft.public.sqlserver.replication)
