Okay, let us say you have the max seed value of 1000.
1000 12:48
you do an insert. SQL Server 'grabs' the next number - 1001 and holds it ready for the input.
1001 'locked for new data'
But now the insert doesn't happen. It's rolled back, not committed, you cancel it, whatever. SQL Server will not release that number. It's used. Then you redo the insert, SQL Server now grabs the next number - 1002. And you get what appears to be an incorrect/missing value.
1000 12:48
1002 12:49
I think that's what you are seeing happen.
-SQLBill
Posting advice: FAQ481-4875