Will I use stored procedures or direct write code in a mvc web project?Which is better?

Question

0.00/5 (No votes)

See more:

My web project is using telerik dataaccess ORM,when I deal with the data,I can use stored procedures or direct write code.I find it is more efficient to use stored procedures.But some of my workmate say that using stored procedures is difficult to maintain, especially for some of the new recruits.Can anyone tell me when to use stored procedures and when direct write code in ORM better?

Posted 1-Nov-14 21:29pm

PEIYANGXINQU

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)

George Jonsson · Answer 1 · 2014-11-01T21:51:00

Different programmers have different opinions about this topic.

I prefer to use stored procedures for two main reasons:

1. The structure of the database is hidden from the caller.
The caller only knows the format of the procedure.
This means that the database structure can change at any time as long as the SP returns the answer in the same way and doesn't change the input.
The client doesn't need to change at all.
This actually makes database administration easier.

2. It is easier to switch between different databases
Let's say you have two factories with one database each with the same functionality.
The two databases are maintained independently and can even be using different flavors, one use MySQL and one use Oracle.
By using stored procedures the client software can be kept the same and just some configuration is necessary.

The main drawback is that it can be quite a few stored procedures to create and they also need to be properly documented.
And as with interfaces in COM, you should never change the format of the procedure.