the dbcc checkident will only be able to set the new seed value (1000), but not the increment (10).
you need the alter table statement:
ALTER TABLE table_name ALTER column_name IDENTITY ( 1000 , 10)
Main Topics
Browse All TopicsHow to change the increment value of an identity column. Current values for seed and increment is 1,1. Need to change this value to 1000,10.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
The forced accepted solution is not a solution for this question. We cannot change the increment value once it has been set. This can be done only either by dropping and recreating the columns or creating a temporary table, inserting data into it, dropping existing table and then renaming temp table to the original table.
I'm having a huge issue with Identity.
When a table is born, the Identity increment is 1, seed 1, and the identity increments. Looking at the table a year later you still see 1, 1.
Now. Take a table where we force set the seed to say 1000, for any number of reasons; it gets set.
You now have a HUGE risk. Any time you alter the table schema, and the table is dropped - added, say a column change, addition, deletion. The Identity is rolled BACK to 1000.
This is not a problem when the table always keeps these rows, you will get a dup throwback.
However if this is a 'temporary' table, but the identity is critical, there is no duplicate.
Any suggestions on how to set the identity to a newer number, but not setting that 'Designer, view. How does SQL know the Ident_Current for aged tables?
Business Accounts
Answer for Membership
by: aneeshattingalPosted on 2007-01-09 at 09:48:50ID: 18277296
DBCC CHECKIDENT ( 'table_name', RESEED, new_reseed_value )
Current identity value is set to the new_reseed_value. If no rows have been inserted to the table since it was created, the first row inserted after you run DBCC CHECKIDENT uses new_reseed_value as the identity. Otherwise, the next row inserted uses new_reseed_value + the current increment value.
If the table is not empty, setting the identity value to a number less than the maximum value in the identity column can result in one of the following conditions:
If a PRIMARY KEY or UNIQUE constraint exists on the identity column, error message 2627 will be generated on later insert operations into the table because the generated identity value will conflict with existing values.
If a PRIMARY KEY or UNIQUE constraint does not exist, later insert operations will result in duplicate identity values.