Primary Key Problem in identity increment

Question

5.00/5 (1 vote)

See more:

SQL-Server-2005

, +

Hi
i created a table ID int is a primary key for that table i put

Identity Specification :yes
IsIdentity :yes
Identity Increment :1
Identity Seed :1

my problem is

when i inserting records its working fine

but when i deleting records the identity is not decrimented

for example i have 15 records i deleted the 15 th record and inserted the new record but now it takes 16 as new record insted of 15.

The Above experiment is done on Gridview control in asp.net website i did this from Grideview Enable Deleting Property
how to solve this

Posted 8-Jun-11 20:53pm

krishna_goluguri

Updated 8-Jun-11 21:57pm

CPallini

v2

Add a Solution

3 solutions

Solution 1

This is the point of Incriment there is no way to decriment unless you enter the ID manualy and not by autonumber.

You get the MAX ID and add 1 and insert it to the new record.

Posted 8-Jun-11 20:58pm

JustWorking

Comments

JustWorking 9-Jun-11 3:00am

PS: If you find my answer helpfull Accept Solution and vote 5 :)

Solution 2

Hi,
The identity is never decremented on delete. It either increments or decrements. You can simulate the behavior of decrement on delete (by resetting the seed), but its strongly discouraged.
Regards

Posted 8-Jun-11 20:58pm

Ciumac Sergiu

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

OriginalGriff · Accepted Answer · 2011-06-08T21:00:00

No, it won't be. The reason is simple:
What if you have a second table, which contains information related to the first?

For example, if your first table is Customers, and your second is Purchases, then there would be a numeric field in your second table to relate the purchase to a specific customer in the first. If you do not tell SQL about it, it will still work fine, but if SQL re-ordered any identity fields then purchases would not be affected and would reflect on the wrong customer.

No: SQL does not re-order identity fields: in fact, it will not generate the same number twice - that's the whole idea. If you really must work with ordered numbers, then do not use an identity field, but work from the ordinal position of each record for a given sort order.