Do the merge for records that are fine between the two servers. If there is an issue on the merge, save the record to an error table. Then, process the merge table. You'll probably have to create a new id for that record then merge it in.




>Just one time. I can't use either because the customer ID in A has to be preserved.
>>This is usually handled in one of two ways..
>>
>>1) a column for the original server, then the id becomes id + server
>>
>>2) use a guid instead of an int for the id
>>
>>Is this a one time merge or will you need to do this regularly?
>>
>>
>>>Hello all.
>>>I have two customer tables in different servers (A and B). They contain many common custumers, but the Id's are different, so my client provided me with a table with the id equivalence of the common customers (ie, customer 5 in table A is customer 3 in table B and so on). If the customer in B has no equivalent in A then the equivalent ID is blank.
>>>My client wants to generate a single customers table with the same customer id in both databases. It seems easy but there are problems:
>>>What happens if customer 3 in A is customer 5 in B and customer 7 in A is customer 3 in B? If I change the Ids that equivalence never happens.
>>>
>>>So here I am asking for ideas.
>>>Regards