I have Transactional Replication set up between two SQLServers (sp3), Build: Microsoft SQL Server 2000 - 8.00.818 (Intel X86) May 31 2003 16:08:15 Copyright (c) 1988-2003 Microsoft Corporation Enterprise Edition on Windows NT 5.0 (Build 2195: Service Pack 4).
I am getting the error:
Cannot insert duplicate key row in object 'table_name' with unique index 'PK_table_name'.
(Source: Server1(Data source); Error number: 2601)
LastCommand:
{CALL sp_MSins_table_name('kt102', 38277, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, 0, 6.000000000000000e+000, NULL, NULL, 0, 0, 2005-11-14 17:21:00, NULL, NULL, NULL, 0, 0, 0, 0, NULL, NULL, NULL, NULL, NULL, 0, NULL, NULL, NULL, 0, 0, NULL)}
Transaction sequence number and command ID of last execution batch are 0x0003605800008F5A000100000000 and 6.
I've found the row in the destination table and deleted it and started synchronizing it then skips that row and finds another that exists. I delete that one start synchronizing again and it finds another row that already exists. When I go to look for the rows I deleted after synchronizing those rows do not exist.
No one should be writing to this database as its our failover (doesn't mean someone isn't I just don't know at this point in time). Barring someone else writing to this database is there any other reason this could be happening and what can I do to fix it.
Thanks in advance,
Mike
I am getting the error:
Cannot insert duplicate key row in object 'table_name' with unique index 'PK_table_name'.
(Source: Server1(Data source); Error number: 2601)
LastCommand:
{CALL sp_MSins_table_name('kt102', 38277, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, 0, 6.000000000000000e+000, NULL, NULL, 0, 0, 2005-11-14 17:21:00, NULL, NULL, NULL, 0, 0, 0, 0, NULL, NULL, NULL, NULL, NULL, 0, NULL, NULL, NULL, 0, 0, NULL)}
Transaction sequence number and command ID of last execution batch are 0x0003605800008F5A000100000000 and 6.
I've found the row in the destination table and deleted it and started synchronizing it then skips that row and finds another that exists. I delete that one start synchronizing again and it finds another row that already exists. When I go to look for the rows I deleted after synchronizing those rows do not exist.
No one should be writing to this database as its our failover (doesn't mean someone isn't I just don't know at this point in time). Barring someone else writing to this database is there any other reason this could be happening and what can I do to fix it.
Thanks in advance,
Mike