Posted by teddysnips on 08/17/07 09:18

And here's another thing that's gives me pause for thought (for other
information see the thread entitled "ODBC Timeout problems but very
hard to pin down")

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?

Thanks

Edward

• Next in forum: Re: Unaccountable jump in Identity column value
• Prev in forum: Re: Restore database with no log
• Thread view: Unaccountable jump in Identity column value

[Reply to this message]