On the other hand, it might be useful to spot check what other DBCC commands are (or are not) being run, though. It's meant to show you when the maximum value is greater than the value SQL Server assigned last (and from which it determines what it thinks it's going to assign next, even if in practice this isn't always true). Note, this will show more than just CHECKIDENT events, but you can filter that further. After running the DBCC command your next inserted row into your table will be inserted with an identity column value 1 higher than the new seed value specified in the DBCC command.
Lets create a simple example to demonstrate it. DBCC CHECKIDENT ('youtable', RESEED,But in SQL Server 2012, you can feel the difference in result set when it is RESEED or NORESEED. CREATE TABLE tblreseed (sno INT IDENTITY,col1 CHAR (1)) GO INSERT INTO tblreseed SELECT A UNION SELECT B.
The below query create a test table with dummy values. This is done with DBCC CHECKIDENT command. Not sure what you mean by "recovered" - current column value tells you the maximum value in the table. If you execute DBCC CHECKIDENT command in earlier version, you get the same result set, whether it is RESEED or NORESEED. The blog title DBCC Reseed table identity value refers to resetting the current seed value of an identity column.