Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

All Forums  SQL Server 2000 Forums  SQL Server Development (2000)  help with replication / primary key problem

Author  Topic  pshifrin Starting Member 1 Post Posted - 2002-05-19 : 18:37:58 Hi Everyone, I have 2 instances of SQL Server 7.0 SP4. One is setup as a publisher for replication and the other one is set to manually sync (because the other computer is on a dialup connection and not always connected). Anyway, every table syncs fine HOWEVER, after a sync, either side cannot add ANY new records to ANY table. Every table has a primary key defined but after a sync it seems to "forget" what the next unqiue integer and if you try to insert a new record it tries to put "1" in the primary key field, which of course fails with the "primary key violation message". You can keep clicking ok and it will eventually work. example: it tries to insert 1, you click ok, it fails because ID=1 already exists, then it tries 2 and 3 and so on, until it gets to the next available number. Shouldn't it automatically know what the next avail integer is? thanks