identity column problem skipped a range of values

Hi,
This is on SQL Server 2000 database. Inserts to a table with an identity
column on it have suddenly jumped in value. It was going along, 301,
302, ... then all of sudden identity column values jumped to 64221,
64222...
The app inserting data is an ASP.net app (1.1x). No changes were made to
the app. Does anyone have an idea what must be causing this. BTW, this
happened with only one person access the database.
jj"jj" <jj@.no_spam.net> wrote in message news:e7ua3f$5t9$1@.lists.fhcrc.org...
> Hi,
> This is on SQL Server 2000 database. Inserts to a table with an identity
> column on it have suddenly jumped in value. It was going along, 301,
> 302, ... then all of sudden identity column values jumped to 64221,
> 64222...
If you said it was skipping from say 302 to 306 or something reasonable, I'd
say there's some sort of rollback on transactions occurring.
(keep in mind that the IDENTITY column gets incremented regardless of the
success of a transaction.)
If it's happening with only one person, I'd set up profiler to see what
they're doing with the connection.
I mean I suppose it's possible they're starting and then rolling back 64000
transactions, but that sounds weird.

> The app inserting data is an ASP.net app (1.1x). No changes were made to
> the app. Does anyone have an idea what must be causing this. BTW, this
> happened with only one person access the database.
> jj|||"jj" <jj@.no_spam.net> wrote in message news:e7ua3f$5t9$1@.lists.fhcrc.org...
> Hi,
> This is on SQL Server 2000 database. Inserts to a table with an identity
> column on it have suddenly jumped in value. It was going along, 301,
> 302, ... then all of sudden identity column values jumped to 64221,
> 64222...
If you said it was skipping from say 302 to 306 or something reasonable, I'd
say there's some sort of rollback on transactions occurring.
(keep in mind that the IDENTITY column gets incremented regardless of the
success of a transaction.)
If it's happening with only one person, I'd set up profiler to see what
they're doing with the connection.
I mean I suppose it's possible they're starting and then rolling back 64000
transactions, but that sounds weird.

> The app inserting data is an ASP.net app (1.1x). No changes were made to
> the app. Does anyone have an idea what must be causing this. BTW, this
> happened with only one person access the database.
> jj