SpiraTeam and KronoDesk have IDs that occasionally jump by 1,000

Why Does this Happen?

SQL Server 2012 now uses a cache size of 1,000 when allocating IDENTITY values and restarting the service "loses" unused values.

If this is for some reason a real issue for you see the workarounds on the linked Microsoft Connect Item thread.

You can use a sequence with a lower cache size for example or trace flag 272 makes the IDENTITY allocation logged as in previous versions.

You should be aware neither of these assure no gaps. IDENTITY has never guaranteed this as it would only be possible by serializing inserts to the table.

References

• http://stackoverflow.com/questions/14146148/identity-increment-is-jumping-in-sql-server-database
• https://connect.microsoft.com/SQLServer/feedback/details/739013/failover-or-restart-results-in-reseed-of-identity