Posted by Bill E. on 08/19/07 12:16

I'm aware of this and it certainly is easy to fix, but it doesn't give
me insight into how this could have happened in the first place.

Bill

Gert-Jan Strik wrote:
> Check out "DBCC CHECKIDENT" in BOL.
>
> Gert-Jan
>
>
> "Bill E." wrote:
> >
> > SQL Server 2005
> >
> > We have a table where the current identity value is lower than the
> > maximum value. This is the first time I've seen such a thing. How
> > can this occur? I see postings about this problem but they seem to
> > concern older versions of SQL Server.
> >
> > I did some tests on another table to see if I could reproduce the
> > problem by setting Identity_Insert on and then forcing the identity to
> > a value. I then set Identity_Insert off and added a row normally, but
> > the next identity was always the next largest number, not some number
> > in between.
> >
> > Bill E.
> > Hollywood, FL

• Next in forum: Re: How to check if a Table is <empty> ie doesnt contain any rows
• Prev in forum: Re: How to check if a Table is <empty> ie doesnt contain any rows
• Thread view: Re: Inconsistent identity values

[Reply to this message]