Primary key value problem in SQL managment

Question

0.00/5 (No votes)

See more:

I am inserting some data in send request table of my database. I have used break point and it shows that primary key has value of 1 but when i m checking it in SQL management studio there primary key value is greater than 1000 each time. please help me what is this problem and how to solve it.
I have deleted the all records from that table. there is no data it means when i m inserting the new data it should be on id 1 but its on id 1003 or 1004 .

What I have tried:

I have searched on the internet and i have used ressed table identity but its not working in asp .net mvc.

Posted 2-Oct-16 8:43am

Member 12771245

Updated 2-Oct-16 9:02am

v2

Add a Solution

Comments

[no name] 2-Oct-16 14:53pm

Probably because you have that column set to be auto increment.

1 solution

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)

Wendelius · Answer 1 · 2016-10-02T09:02:00

As pointed out by NotPolitcallyCorrect[^] you probably use an automatically incrementing identity.

First of all since this kind of key definition serves only as a unique identifier for a single row, it should not matter what the value is. 1000 is just as fine as 1, since it just identifies a row.

You will probably always have gaps in the numbering. For example if
- you add three rows in the table: 1, 2, and 3
- you delete row 2
- you now have rows 1 and 3

If you still want to reset the identity, have a look at reseeding the value with DBCC CHECKIDENT (Transact-SQL)[^]