title: identity specification gap after several operations
body: <p>I'm using <code>identity specification</code> for a table in SQL Server 2012. Let we have two <code>Insert</code> and then two <code>Delete</code> operations. After these operation, the primary key should start from 1, but it will start from 3. I'm worried about this problem <strong>causing no place for inserting new item</strong> after a long time. Does SQL Server 2012 fill these gaps by itself?</p>
  
  <p>If it is possible, please refer me a documentation (for example from microsoft)</p>
  
  <p>Update 1:<br>
  I heard that it can jump randomly. Especially when server is restarted. I insert into table every 500 ms. Let, my primary key jump to 1,000,000,000. Two jump like this is enough for termination of my program.</p>