Answers for "Why does the identity value start with 2 in 2008 R2 and with 1 in 2012?"
https://ask.sqlservercentral.com/questions/114860/why-does-the-identity-value-start-with-2-in-2008-r.html
The latest answers for the question "Why does the identity value start with 2 in 2008 R2 and with 1 in 2012?"Answer by David Wimbush
https://ask.sqlservercentral.com/answers/114879/view.html
Is this table recreated each time or do you just truncate/delete the contents? If it's recreated I would start with just some SQL testing to make sure the SQL engine works the way you would expect:
create table test (ID int identity(1,1) not null);
insert test default values;
select * from test;
drop table test;
I just tried this on SQL 2008 R2, 2012 and 2014. In all cases I got the value 1 in the identity column. I can't think why it wouldn't work the same for a new table in any version of SQL Server.
If you truncate the table the identity should be re-seeded to 1 (ie. 1 will be the next value output). If you delete the rows, the identity value is not reset and the next insert will get the next value in the sequence.
Another possibility is perhaps the job inserts row 1 and then rolls back later. The identity value is not reset if a transaction fails or is rolled back.Wed, 17 Sep 2014 12:39:02 GMTDavid WimbushAnswer by west007
https://ask.sqlservercentral.com/answers/114864/view.html
Maybe there was allready one row in the table of 2012?
Make a Test: reseed to 0 and try againTue, 16 Sep 2014 10:40:00 GMTwest007