Keeping identical data in int primary key and a varchar() type fields of SQL Express 2005 Server database table.

Question

0.00/5 (No votes)

See more:

SQL-Server-2005

, +

In a database table we have a varchar() type field which has to maintain identical data to int type primary key for a specific purpose. And varchar fields data value to be calculated before saving new records.

We used Select Max(primary key column) to retrieve maximum value of primary field and add 1 to it for this purpose. But on deleting last record, newly added record's varchar() field stores deleted record's value and primary key field value becomes +1 to it.

Posted 27-Apr-11 17:39pm

sk saini

Add a Solution

Comments

walterhevedeich 28-Apr-11 0:12am

And what is the question? :)

sk saini 28-Apr-11 1:33am

inconsistency between both field values to whom we want to keet identical due to deletion of last record.

sk saini 28-Apr-11 1:36am

How to remove inconsistency in values of both fields whose values to be kept identical.

Sandeep Mewara 28-Apr-11 0:42am

Issue?

sk saini 28-Apr-11 1:37am

How to remove inconsistency in values of both fields whose values to be kept identical.

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)

*dan!sh* · Answer 1 · 2011-04-27T18:42:00

It seems you are keeping track of the number of rows that were inserted in the table. It does not matter whether they were deleted later on. I think you should be going for Audit tables. Whenever Insert/Update/Delete happens, a trigger can change this table. Later you can use this for any reporting job that you need. Although as people say that triggers are evil, there are to ways of doing this:

Change the datatype for the varchar column. It should be integer. And make a autoicnrement column. This should serve the purpose. Alhtough you will have to check the effect of row deletion on the incremental value. I believe it should be same as sequence in Oracle so it should change.