Business Logic in Stored Procedure Yes / No

Question

0.00/5 (No votes)

See more:

Hi,

There is always a debate over the topic - "Whether to put the business logic in Stored Procedure or Not?". If we decide not to use the ORM Tool and not to put the Business Logic in Stored Procedure then where would we put the Business Logic?

In my previous applications I have always preferred putting all of the Business Logic in Stored Procedures only. Then from .NET code I call these Stored Procedures using Data Access Application Blocks. SQLHelper etc. But this can not be the scenario all the time. So I did some googling but ended up in confusion.......

Any suggestionss...?

Regards,
Pravin

Posted 27-Jul-11 21:25pm

Pravin Patil, Mumbai

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)

walterhevedeich · Accepted Answer · 2011-07-27T21:45:00

Solution 1

IMHO, there's a reason why you have a Data Access Layer, and a Business Logic Layer. If you have a small application that does not have much business logic, then I guess you can at put it on your SP. But when you have a complex app, I suggest you create a BLL for that. Reason for it is maintainability. What if there are pending tasks to make some data related fix/enhancement to them? Chances are, you might end up modifying the business logic part of the SP every time this happens.

Posted 27-Jul-11 21:45pm

walterhevedeich

Comments

Pravin Patil, Mumbai 28-Jul-11 5:17am

So, you mean that we should limit the Stored Procedure to fetching the data only and whatever logic we have to apply that should go in BLL i.e. .NET Code.

walterhevedeich 28-Jul-11 5:34am

Not exactly. What I am trying to point out is that business logic should, as much as possible, be put on the the BLL. The SP would not be limited to fetching data only as you also need to do data validation, and this is different from business rules validation, which is what you will put on the BLL.