title: DBCC CHECKIDENT(myTable, RESEED,1) reseeding from 2
body: <p>In SQL Server 2012, the following query is seeding the identity column <code>myTable_id</code> from 2 instead of 1. Why? <code>myTable_id</code> is also PK.</p>
  
  <pre><code>DELETE FROM myTable;
  GO
  SELECT * FROM myTable --0 rows are returned as expected
  GO
  DBCC CHECKIDENT(myTable, RESEED,1)
  GO
  INSERT INTO myTable(col1,col2,col3) SELECT FROM AnotherTable(col1,col2,col3)
  GO
  SELECT * FROM myTable --1005 rows are returned as expected, but identity value starts from 2
  GO
  </code></pre>
  
  <p><strong>Remark</strong>:</p>
  
  <ol>
  <li>The data inserted is right, the only issue is that the newly inserted data starts from 2 instead of 1.</li>
  <li>In the above sql code if I use <code>DBCC CHECKIDENT(myTable, RESEED,0)</code> the identity column correctly starts from 1.</li>
  <li>Following is snapshot in SSMS for the <code>myTable_id</code> column:</li>
  </ol>
  
  <p><a href="https://i.stack.imgur.com/PwU1F.png" rel="noreferrer"><img src="https://i.stack.imgur.com/PwU1F.png" alt="enter image description here"></a></p>