Post reply

Identity Values were Reseeded - causing PK constraint error

  • August 22, 2006 at 7:07 am

    #170082

    In one of our databases - tables with Identity column as a primary keys were somehow reseeded.  So, we were getting Primary Key constraint errors.  I ran checkident on the tables and reseeded them.  How did this happen?  What could cause this?

  • August 23, 2006 at 9:02 am

    #656387

    Only way I know of is if someone actively reseeds it (like you did to correct it)...

  • August 23, 2006 at 9:15 am

    #656392

    Think I found the issue.  This occured in our test database server.  It seems that one of our developers was messing around with Replication and tried to replicate a dbase from our development to test and didn't change the dbase name and replicated to the existing dbase.  Well, that dbase isnt' meant for transactions.  So, when we were testing our application - we were getting PK constraint errors because we were inserting records from the replicated dbase.

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply