reinitialized subscription - more info

Running - Win 2K / SQL 2K
I am constantly, once a week or so,getting an error on a
transactional publication that I have...
The subscription(s) have been marked inactive and must be
reinitialized. NoSync subscriptions will need to be
dropped and recreated.
This publication is set up to be continious and is
checked daily to verify it is running. I will come in
one morning and there will be an error. There are 15
remote locations using a transactional/continous
publication to move data to the main office.
How can I prevent this from happening?
What is causing this?
Is there some logging option I can turn on to see more
info about the transactions?
Larry....
By default is a publisher and subscriber have not "talked to" each other for
14 days the subscriber is marked inactive and the subscription may be
dropped. You must reinitialize, regenerate and redistribute the snapshot to
clear this condition.
You can set the interval by right clicking on your publication, selecting
properties and in the subscription expiration section, set a long expiration
value.
I normally run scripts that detect whether the distribution agent has
replicated a transaction to the subscriber in the last 24 hours, and if not,
it raises an alert which causes operations to be paged.
This raises the visibility of these errors.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"larry..." <anonymous@.discussions.microsoft.com> wrote in message
news:9b3601c43446$63f03c20$a401280a@.phx.gbl...
> Running - Win 2K / SQL 2K
> I am constantly, once a week or so,getting an error on a
> transactional publication that I have...
> The subscription(s) have been marked inactive and must be
> reinitialized. NoSync subscriptions will need to be
> dropped and recreated.
> This publication is set up to be continious and is
> checked daily to verify it is running. I will come in
> one morning and there will be an error. There are 15
> remote locations using a transactional/continous
> publication to move data to the main office.
> How can I prevent this from happening?
> What is causing this?
> Is there some logging option I can turn on to see more
> info about the transactions?
> Larry....
>