To retain the identity counter, use DELETE instead.Р В РІР‚СњР вЂ™Р’ВBCC CHECKIDENT ('', RESEED, 0) If no seed was defined, the default value 1 is used. If the table contains an identity column, the counter for that column is reset to the seed value defined for the column. For indexes, the delete operation can leave empty pages behind, although these pages will be deallocated quickly by a background cleanup process. If the delete operation does not use a table lock, the table (heap) will contain many empty pages.

For example, empty pages in a heap cannot be deallocated without at least an exclusive (LCK_M_X) table lock.

Without exception, zero pages are left in the table.Р В РІР‚СњР В РІР‚С›fter a DELETE statement is executed, the table can still contain empty pages. TRUNCATE TABLE always locks the table (including a schema (SCH-M) lock) and page but not each row. When the DELETE statement is executed using a row lock, each row in the table is locked for deletion. TRUNCATE TABLE removes the data by deallocating the data pages used to store the table data and records only the page deallocations in the transaction log. The DELETE statement removes rows one at a time and records an entry in the transaction log for each deleted row. The following details are taken from the MSDN page for TRUNCATE TABLE:Р В РІР‚СњР вЂ™Р’В¬ompared to the DELETE statement, TRUNCATE TABLE has the following advantages: no WHERE clause), then as long as a) permissions allow for it, and b) there are no FKs referencing the table (which appears to be the case here), using TRUNCATE TABLE would be preferred as it does a more efficient DELETE and resets the IDENTITY seed at the same time. It should be noted that IF all of the data is being removed from the table via the DELETE (i.e.

Sql 2012 express dbcc checkident reseed