Stored Procedure to add two column in a table

Question

0.00/5 (No votes)

See more:

i have table in the Sql-server 2005, i want to perform math operation on two column(ex addition,multiplication) and save the result in the 3 rd column.
is it possible to do with stored procedure.

Posted 4-Mar-12 23:48pm

shrikant.kudlur

Add a Solution

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)

OriginalGriff · Accepted Answer · 2012-03-04T23:58:00

Solution 2

Yes:

SQL

USE [Testing]
GO
SET ANSI_NULLS ON
GO
SET QUOTED_IDENTIFIER ON
GO
CREATE procedure [proc_AddEmUp] 
AS
UPDATE myTable SET sumColumn=firstColumn+SecondColumn

Posted 4-Mar-12 23:58pm

OriginalGriff

Comments

shrikant.kudlur 6-Mar-12 23:48pm

Thanks for the answer
i have one more question
i am executing two update statement, i don't want to execute second update statement if the first update statement fails.

and i m very new to stored procedure can any one suggest me good book or web site.

thanks in advance..

OriginalGriff 7-Mar-12 4:18am

You could check the @@ERROR code, and only do the second UPDATE if it is zero.
Or, you could use a TRANSACTION and ROLLBACK if either errors - which would be preferable as it leaves your database in a better, more "known" state.