Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I’m using Microsoft SQL Server for my database.
There is an ID column in my table. In my usage, rows are deleted and re-created many times. So, if I use Identity Increment and Identity Seed of SQL Server, ID numbers will be very big after some time…
It is not important that every new row have an ID that is bigger than other rows. Just it must be unique.
How to do that in SQL Server? Should I disable Automatic Increment and set ID manually? how?
I’m using C# and SQL Server Express.
I’m not sure why you care if the numbers are big or small (hopefully users don’t have sentimental value or place any kind of meaning on identity values), but one way to avoid exhaustion problems is to use a BIGINT. I forget the exact numbers but if you generate something like 1000 IDs a second it would take 80 years or so to hit the limit – and you can double this if you start at the negative boundary. Yes BIGINT is 8 bytes instead of 4 but this is still much smaller and more usable than a GUID. And if you combine this with data compression, you won’t require any more storage than an INT until well after you’ve used 2 billion numbers.
Don’t over-engineer this, and don’t make the mistake that an identity value’s size or value should mean something. This is a surrogate value generated for internal identification and efficiency only. If you’re telling users about this value, there’s something not right.