sql server replication: Stopping subscriptions from being marked inactive -- sql server replication

Stopping subscriptions from being marked inactive

Josh V
3/14/2005 3:37:05 PM

sql server replication:

Hi,

I have a transactional publication setup that has no automatic schedule of
it's distribution agent. The agent is started from an application as a
"Publish" feature that is used when the user wants to commit the data to our
production systems.

It seems as though the combination of the infrequent transactions on this
database and infrequent runs of the distribution agent result in the
subscription regularly being marked as inactive and requiring a push of a new
snapshot.

It's not being expired and dropped - just marked as inactive. Are there any
steps I can take to guarantee this won't happen regardless of long it is in
between transactions and agent runs?

Both Publisher/Distributor and Subscriber are SQL Server 2000 SP3a and I
have changed the Subscription Expiration to a higher value than the default.
The marking as inactive seems to be controlled by something else.

Thanks,

Re: Stopping subscriptions from being marked inactive

Hilary Cotter
3/14/2005 8:29:06 PM

I normally query msdistribution_history to get a list of subscribers which
the publisher has not talked to in 24 hours. I then raise an alert which
NetIQ picks up and handles.

[quoted text, click to view]