"Maer" <maer@auditleverage.com> wrote in message
news:uABofjI0HHA.5380@TK2MSFTNGP04.phx.gbl...
> Hi - When synchronizing, the following conflict occurred:
>
> INSERT statement conflicted with COLUMN FOREIGN KEY constraint
> 'FK_ContraintName'. The conflict occurred in database 'DatabaseName',
> table 'TableName', column 'PrimaryKeyCol'.
>
> The row was inserted at the publisher but since it could not insert the
> row at the subscriber, the row was added to the conflict table.
>
> Here is the problem: when I go to the subscriber and look at the parent
> table, the parent row exists. I was actually able to manually insert a row
> using the same PrimaryKeyCol value and there was no conflict. So it looks
> like this is happening only when synchronizing.
>
> Is there something that I am overlooking that could be causing this?
>
> Thank you,
>
> Maer
>
>
>
>

"Hilary Cotter" <hilary.cotter@gmail.com> wrote in message
news:%23yHN3WR0HHA.5764@TK2MSFTNGP03.phx.gbl...
> You need to put a not for replication property on your constraints.
>
> Your problem is that with merge replication rows are sync'd according to
> their article id as opposed to the order they are inserted in, so they
> might be inserted out of order.
>
> --
> 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
> "Maer" <maer@auditleverage.com> wrote in message
> news:uABofjI0HHA.5380@TK2MSFTNGP04.phx.gbl...
>> Hi - When synchronizing, the following conflict occurred:
>>
>> INSERT statement conflicted with COLUMN FOREIGN KEY constraint
>> 'FK_ContraintName'. The conflict occurred in database 'DatabaseName',
>> table 'TableName', column 'PrimaryKeyCol'.
>>
>> The row was inserted at the publisher but since it could not insert
>> the row at the subscriber, the row was added to the conflict table.
>>
>> Here is the problem: when I go to the subscriber and look at the
>> parent table, the parent row exists. I was actually able to manually
>> insert a row using the same PrimaryKeyCol value and there was no
>> conflict. So it looks like this is happening only when synchronizing.
>>
>> Is there something that I am overlooking that could be causing this?
>>
>> Thank you,
>>
>> Maer
>>
>>
>>
>>
>
>