ORM vs Direct SQL - which approach would be best one in performance

Question

0.00/5 (No votes)

See more:

, +

We have a web application based on domain object model where the database tables will be mapped to domain objects.
Multiple tables may get mapped to single domain object. I would like to know which solution for domain entity to DB mapping suits us with respect to performance and maintainability

Would like to know which approach we need to implement. Either to go for ORM or Direct SQL

1. Linq to SQL
2. Entity Frame Work
3. nHibernate
4. Stored Procedures

We are currently using VS 2008 , Sql Server 2008 .
We have around 100 tables,60 to 70 Objects and 50 UI Forms.

Our application scope is more on CRU operations (Create, Read and Update) and less Delete Operations.

Like to know your valuable suggestion on which approach would be best one in performance.

Posted 17-Oct-11 5:29am

Liju Sankar

Add a Solution

3 solutions

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)

Not Active · Answer 1 · 2011-10-17T05:40:00

'Like to know your valuable suggestion on which approach would be best one in performance."
There is no "best" solution. Every project is different and it depends on usage, future extensibility, integration, etc, etc.

There are other articles similar to this one. Research and make the decision based on your needs.
Entity Framework Performance[^]

Liju Sankar · Answer 2 · 2011-10-17T21:05:00

Entity Framework is the MS suggested way to move ahead with new applications and where I see most of the support coming from the VS and third party tooling/controls . The new 5.0 version of it is the one which finally came up with the most basic set of enterprise wide usable functionalities (multiple resultsets, table params, enums, multiple shared view of modal, multi generation of Sps etc..., ).

FastEvo8 · Answer 3 · 2011-10-18T10:15:00

IMHO scalability is very important, in other words how many users will use the app at the same time.
I did not see yet an app that is using the first 3 choices that can outperform a data layer using Stored Procedures.
LINQ, Entity and nHibernate do not render efficient SQL and my team spend quite some time in rewriting and optimizing auto generated code.

ORM vs Direct SQL - which approach would be best one in performance

3 solutions

Solution 1

Solution 2

Solution 3

Add your solution here

Preview 0