The best solution is not to use snapshot if at all possible. Can you write
BCP scripts that will reload the tables at the subscriber? Or may be you can
put together a DTS package that will trucate and reload the reporting
tables. If you can do that, you will be able to create a subscription with
no sync option and be up and running in no time

-----Original Message-----
From: Thinus van Rooyen
[mailto:mssqldba-ezmlmshield-x92649666.[Email address protected]
Sent: Tuesday, May 30, 2006 9:21 AM
To: LazyDBA Discussion
Subject: reinitialising subscription

Hi there,

I have 2 branches replicating(transactional) to a main reporting server.

Problem: recently the line between one of the clients and reporting server
went down for a couple of days and the subscription had to be reinitialised.

Q: I need to create a snapshot again to reinitialse the subscription, BUT
what happens to all the replicated transactions allready at the reporting
server? Will they be overwritten, do I have to find a way to delete them
manually by comparing data between reportserver and client and then start
the snapshot?

What is the best way to ensure I dont have duplicate records of the one
branch at the reportserver?

Any comments/suggestions would be sppreciated

Thanks

Thinus


---------------------------------------------------------------------
TO REPLY TO EVERBODY , PLEASE CLICK REPLY-ALL, NOT JUST REPLY
Website : http://www.LazyDBA.com
To unsubscribe: http://www.lazydba.com/unsubscribe.html


MS Sql Server LazyDBA home page