sql-lover (7/19/2013)
Ran DBCC CHECKIDENT and the current column value looks like is higher than the current identity value so it will fail because next one is there.
Suggests that someone, sometime for some reason has reseeded the identity value below what's in the column. Finding out who however may prove difficult, I don't think it's logged anywhere. Maybe the default trace.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability