Replication Server and BCP

[Mike Marcal]

I would appreciate any help/comments on the following problem involving replicating databases:

I have a primary database P, and n replicates: R1, R2, ..., Rn. The replicates are maintained by Replication Server.

Every day I get a file F which I want to bcp into P, and have these updates propagated to all the replicates. The number of rows affected by F is large, say, around 5000.
In the "old" days, I would "fast" bcp F into the database, by turning off logging. With Replication Server, I now need to bcp with logging if I want the Log Transfer Manager to detect the updates and propagate them to the replicates. However, the usual disadvantages associated with this "slow" bcp apply: e.g. P might run out of log space unexpectedly, the updates to P (and consequently, to the replicates as well) will be very slow.

I am aware of Bulk Subscription Materialization, but this seems to apply only for an "initial" load into P: you 'define subscription' at each replicate; 'activate subscription with suspension' at each replicate; bcp F into F, R1, R2, ..., Rn; 'validate subscription' at each replicate. There doesn't seem to be a way to 'suspend subscription' (without dropping the subscripton altogether) at each replicate to perform subsequent bcp's.

Thanks all in advance.

---
Michael A. Marcal (marc...@gs.com)
Goldman, Sachs & Co.
85 Broad St.
New York, NY 10004
(212) 902-8496