|
|
Posted by teddysnips on 08/17/07 10:30
On Aug 17, 11:16 am, Erland Sommarskog <esq...@sommarskog.se> wrote:
> (teddysn...@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.
I take your point. However, all transactions on this system are user-
initiated, especially the generation of this particular type of
record. Further, there is currently only one user of the system
(though it is, believe it or not, mission critical, and this is a
major aerospace company!) and he would not hit the "Add New Record"
button 3,000 times. If it failed the first time, he'd call me!
Just to keep this up-do-date, I have heard from the sysadmin that
there are other databases (which my company does not support) on the
same database server where the data has been quadruplicated!
Will the weirdness never end?
Thanks
Edward
Navigation:
[Reply to this message]
|