That's by design in SQL Server. This could happen when SQL Server restarts. Google for it and you'll see any others experiencing the same thing.
If you don't assume that identities are sequential then you're good to go with this. If you need sequential numbers, look into SQL Server sequences.
Cheers,
Imar
|