7

I am designing table in SQL Server 2008 R2 SP2 Express database. I created table with nvarchar column for data and tinyint column for auto-incrementing identity assuming there will be no more than few rows (that's why I choose 0-255 tinyint). When I add more than 255 rows, this error keeps occurring permanently even after I delete all rows in that table and try to add one new row. I am doing this using SQL Server Management Studio Express.

  1. How to force database engine to check what indexes are free?
  2. Will this happen too if I change tinyint to int and reach limit of int number?
Improve this question
1
  • 1
    That is the error that happens when the range of the IDENTITY column is used up - regardless of what datatype that column has. However: with INT, you get at least 2 billion possible values - which should last a bit longer than the 255 you have used up by now.... Commented Nov 20, 2014 at 13:37

2 Answers 2

Reset to default
11

Once you add 255 rows, then want to delete all rows from table, But the counter of increment column is already set to 255, even after delete all rows.

To solve this, you need to reset counter of increment column after deleting all rows. Please use below query when deleting all rows, so that counter will reset to reset to 0. After execute this query, you can add rows in table with increment column values as 1 or what you set at table design time.

DELETE FROM [TestTable]

DBCC CHECKIDENT ('[TestTable]', RESEED, 0)
GO

You can also use truncate table command, if you want to delete all rows from table. Truncate Command also reset increment column to initial value.

Truncate Table [TestTable]
Improve this answer
Sign up to request clarification or add additional context in comments.

Comments

4

... even after I delete all rows in that table

The point of an identity is that it will increment the last assigned value irrespective of deletes, so as soon as you exceed the capacity of the identity type, that error is permanent.

Will this happen too if I change tinyint to int and reach limit of int number?

Yes, it will happen for any type that can overflow.

How to force database engine to check what indexes are free?

This would kind of defeat the purpose of an identity as you would be reusing previous values.

Improve this answer

Comments

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.