Failover or Restart Results in Reseed of Identity - FIX

07 Jan 2015

Adoption Blockers Data Old Blog Posts SQL Server

This post has been ported from which I then repeated on

There existed an "issue" for us when we moved to SQL 2012 where every time your SQL instance restarted for any reason be it manually or server unexpectedly turned off your identity columns would have jumped numbers on the next record being inserted. It was also raised on the connect site

We found out that this was not actually an issue and was by design for performance to optimize the amount of disk IOs that were required to generate sequence numbers. A post on SQL Server Training describes how to change the cache size

Before seeing that post however I developed another solution that basically reseeded every table on instance startup so the issue didn't exist. To use this solution you can just run the script below on your SQL instance.



Hope this helps someone as I see the connect issue on it is still active.