Why Does My SQL Server 2012 Identity Column Start at 1001 Instead of 1?

Identity Column Values Unexpectedly Starting from 1001

In SQL Server 2012, you may encounter an unexpected phenomenon where identity column values begin from 1001 instead of the expected 1. This deviation is caused by a change in how SQL Server handles identity values in the Denali release.

Reasons for the Jump

The identity value jump can occur due to:

• Automatic server restarts after updates
• Other system events that necessitate a server restart

Solutions

To address this issue, you have two options:

• Use Trace Flag 272: This flag generates a log record for each identity value generated. It may impact identity generation performance.
• Use a Sequence Generator with No Cache Setting:

To enable Trace Flag 272:

1. Open "SQL Server Configuration Manager."
2. Right-click the SQL Server instance name and select "Properties."
3. Click "Startup Parameters" and add "-T272" to the "Startup Parameters" box.
4. Confirm the changes.

The above is the detailed content of Why Does My SQL Server 2012 Identity Column Start at 1001 Instead of 1?. For more information, please follow other related articles on the PHP Chinese website!