Single stored procedure with if else or separate for optimal performace

Question

0.00/5 (No votes)

See more:

SQL-Server-2008R2

I am using asp.net,c# and sql 2008 R2 in my project.

I came across a situation where I need to optimize my front end and back end .
I have a grid view with save and delete options.

Case :1 :-I can use either a single stored procedure with a parameter say @action ='Add' for save and @Action='Delete' for delete case .In the stored procedure I can handle these cases inside

if( @action=='Add')
...
else
.....

Case :2 :- i can use one stored procedure for save and another for delete.

Please advise which is the best method.

Thanks in advance.

Posted 22-Apr-15 21:32pm

Member 10112611

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)

Sascha Lefèvre · Accepted Answer · 2015-04-22T21:49:00

Solution 1

Use separate stored procedures. Just like in C# or any other programming language a method should have a single responsibility, your stored procedures should. For adding, you would usually have to supply multiple column values; for deleting usually only one. So if you used one stored procedure for both adding and deleting, you would have to supply but then ignore multiple values when deleting. That wouldn't be good practice. And having separate stored procedures for adding and deleting won't impact your performance at all.

Posted 22-Apr-15 21:49pm

Sascha Lefèvre

Updated 22-Apr-15 21:51pm

v2

Comments

Member 10112611 23-Apr-15 3:52am

Thanks you very much

Sascha Lefèvre 23-Apr-15 3:54am

You're welcome.

Member 10112611 23-Apr-15 3:59am

One more doubt..If I create 2 stored procedures memory consumption of the DB will be increased compared to the other option of using single ,right?. But on the execution side, instead of if... else... (which increases the execution time , i am not sure about this)it is better to use single one..Is it like that?

Sascha Lefèvre 23-Apr-15 4:08am

You absolutely don't have to bother about memory consumption or performance. There won't be a difference significant enough to speak of. But separate stored procedures will be cleaner coding.

Member 10112611 23-Apr-15 4:08am

Ok. Thanks..

Sascha Lefèvre 23-Apr-15 4:10am

You're welcome. Please be so kind and mark my answer as accepted :)