How do I "suspend" merge replication while I extract data from central table?

Is there a standard practice to "hold" Merge replication so that the
data collected at the central server (in a remote sales order
application) can be periodically 'removed' to another part of the
system without clashing with ongoing replication from clients?
I'm experiencing my clients initiating replication, and therefore
inserting more rows, whilst the server SSIS job transfers and deletes
rows collected in the central table to the order processing tables,
thus losing data.
My implementation is SQL 2005 Express clients using Merge Websync to a
SQL 2005 standard central server.
Any advice/recommendations would be appreciated!
the best approach is to drop the subscriptions and publications and make the
changes. You can try to disable the triggers make changes, and then
re-enable them. However the results may be unpredictable.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
<reefbreakbda@.hotmail.com> wrote in message
news:1175416990.053051.174730@.y80g2000hsf.googlegr oups.com...
> Is there a standard practice to "hold" Merge replication so that the
> data collected at the central server (in a remote sales order
> application) can be periodically 'removed' to another part of the
> system without clashing with ongoing replication from clients?
> I'm experiencing my clients initiating replication, and therefore
> inserting more rows, whilst the server SSIS job transfers and deletes
> rows collected in the central table to the order processing tables,
> thus losing data.
> My implementation is SQL 2005 Express clients using Merge Websync to a
> SQL 2005 standard central server.
> Any advice/recommendations would be appreciated!
>