"Hilary Cotter" <hilary.cotter@gmail.com> wrote in message
news:OeDgQdSzHHA.484@TK2MSFTNGP06.phx.gbl...
> Set up your DRI on the publisher and subscriber with the not for
> replication clause.
>
> Then set compensate for errors to be false.
>
> --
> 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 > "Leila" <Leilas@hotpop.com> wrote in message
> news:uYPSj44yHHA.4820@TK2MSFTNGP04.phx.gbl...
>> Hi,
>> I have replication between two instances of SQL2K. I have created the
>> subscription with choosing option of "do not initialize schema and
>> data...".
>> Imagine I have Customers and Orders table in publisher and subscriber
>> that CustomerID from orders references CustomerID in customers. Both
>> publisher and subscriber have their own data, therefore some customers
>> exist in publisher that subscriber doesn't have them and vice versa. When
>> subscriber inserts an order for a customer which exists only in
>> subscriber, this new order will be replicated to publisher as well but
>> whereas its customer is not there, the insert encounters the violation of
>> FK constraint. Everything is ok so far. The bad thing is that this new
>> order will be deleted from the subscriber although its customer is
>> available there. How can I prevent this final delete?
>> Any help would be greatly appreciated?
>> Leila
>>
>>
>>
>
>