Very Computer

We have a site that was running for a number of weeks quite happily, and
then we upgraded the software and re-generated the publications and
subscriptions which worked correctly.

The snapshot rebuilt itself at midnight and then today we find that the
subscribing sites databases have no data in them anymore, but there are no
deletes in the merge agent log!

Some questions

1. Should we be scheduling the snapshot to regenerate each night?
2. Where's the data for the snapshot held - there aren't any bcp files in
the snapshot directory.
3. Each article is marked with a pre-action of 'drop table', since the
schema changes at the publisher need to be pushed down to the
subscriber, is this likely to be causing the 'disappearing data' problem?

Regards

Paul Hatcher, MCSD
Principal Consultant
Graduate Associates Ltd

BCP files are only used by the merge replication's snapshot if dynamic
filtering is not used.  Otherwise, if you elected to use 'sync' mode rather
than 'nosync', the initial "snapshot" is performed by inserting records
one-by-one through the merge agent.  If you are using dynamic filtering, you
only need to re-create your snapshot when your schema changes.  As to why
you have no data at your remote sites, if you are using dynamic filtering,
check to make sure that the filter criteria is met.

Regards,

--
Nathan Allan

Quote:> My understanding of the snapshot in merge replication is to provide a set
> of schema and data so that the subscriber has a base point to start with.

> We have a site that was running for a number of weeks quite happily, and
> then we upgraded the software and re-generated the publications and
> subscriptions which worked correctly.

> The snapshot rebuilt itself at midnight and then today we find that the
> subscribing sites databases have no data in them anymore, but there are no
> deletes in the merge agent log!

> Some questions

> 1. Should we be scheduling the snapshot to regenerate each night?
> 2. Where's the data for the snapshot held - there aren't any bcp files in
> the snapshot directory.
> 3. Each article is marked with a pre-action of 'drop table', since the
> schema changes at the publisher need to be pushed down to the
> subscriber, is this likely to be causing the 'disappearing data' problem?

> Regards

> Paul Hatcher, MCSD
> Principal Consultant
> Graduate Associates Ltd

Thanks, the problem was that one day we had data, the next day after the
snapshot agent had run again, the data had disappeared from the site!

Regards

Paul Hatcher, MCSD
Principal Consultant
Graduate Associates Ltd

Quote:>BCP files are only used by the merge replication's snapshot if dynamic

If using static filtering, does this mean that the snapshot files are needed
for subsequent replication sessions?

Greg

--
Mike
RapidSQL 5.2 review is up: http://www.mssqlserver.com/products
SQL Server resources: http://www.mssqlserver.com
Jokes, general products, and consulting: http://www.mhotek.com
Certification resources: http://www.certfaq.com
SYSOP PASS Discussion Forums: http://www.sqlpass.org

"Aim high. You can never achieve more than you aspire to." - Al Reis
Please direct all replies to the newsgroup unless specifically stated
otherwise.