Posted by Erland Sommarskog on 08/17/07 10:16

(teddysnips@hotmail.com) writes:
> In APP 1 (Access front end, SQL Server 2000 backend) there is an
> operation to generate a discrepancy report. These are numbered
> sequentially, and this uses an Identity column with a seed and
> increment of 1. These reports are added approximately once a week.
> This week the value of the Identity column has jumped from 5,399 to
> 8,420. I need hardly add that no-one has added just over 3,000
> reports in the interim.
>
> Can this be related to the bizarre behaviour as reported in the other
> thread?

Maybe. Keep in mind that IDENTITY values are consumed even if an INSERT
fails. Say for instance that the INSERT was part of a user-defined
transaction what then was rolled back because of a timeout, and then was
reattempted and reattempted.


--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx

• Next in forum: Re: ODBC Timeout problems but very hard to pin down
• Prev in forum: Unaccountable jump in Identity column value
• Thread view: Re: Unaccountable jump in Identity column value

[Reply to this message]