A subscription has expired and has been dropped

I have two SQL 2000 Servers with Merge Replication. I had a problem on my
link for a month and the "Expired subscription clean up" job dropped the
subscription ! and now I don't know how to replicate the generated data at
the subscriptor.
I appreciate any help.
You will need to re-apply a snapshot to the subscriber...
"gus barraza" wrote:

> I have two SQL 2000 Servers with Merge Replication. I had a problem on my
> link for a month and the "Expired subscription clean up" job dropped the
> subscription ! and now I don't know how to replicate the generated data at
> the subscriptor.
> I appreciate any help.
>
|||Jim the subscription type is PUSH
re-apply a snapshot means that i should PUSH a new subscription again ?
Will I lost the data generated at the subscriber ?
"Jim Breffni" wrote:
[vbcol=seagreen]
> You will need to re-apply a snapshot to the subscriber...
>
> "gus barraza" wrote:
|||Interesting problem.
I don't know of any method of automatically re-syncing after the
subscription has been dropped other than to apply a new snapshot.
Once the subscription has been dropped SQL has no way of keeping track of
changes that need to be applied to the subscriber.
Sounds like you will need a manual process to bring the publisher up to date
with subscriber changes before creating a new snapshot. Not a pleasent
thought...
Redgate do a sql DATA compare tool that will generate sql scripts for you
that will update your tables.
Jim.
"gusbarraza" wrote:
[vbcol=seagreen]
> Jim the subscription type is PUSH
> re-apply a snapshot means that i should PUSH a new subscription again ?
> Will I lost the data generated at the subscriber ?
> "Jim Breffni" wrote:
|||Thank you Jim,
I have my own application to this cases, but I had been confirm my suspects,
that the only way to recover data on the subscriber is through this slow
process.
I should start to make this process...
"Jim Breffni" wrote:
[vbcol=seagreen]
> Interesting problem.
> I don't know of any method of automatically re-syncing after the
> subscription has been dropped other than to apply a new snapshot.
> Once the subscription has been dropped SQL has no way of keeping track of
> changes that need to be applied to the subscriber.
> Sounds like you will need a manual process to bring the publisher up to date
> with subscriber changes before creating a new snapshot. Not a pleasent
> thought...
> Redgate do a sql DATA compare tool that will generate sql scripts for you
> that will update your tables.
>
> Jim.
>
> "gusbarraza" wrote: