Home/ Questions/Q 6701109
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-26T06:53:40+00:00

As the popularity of ORMs like LINQ to SQL and Entity Framework increases, it

  • 0

As the popularity of ORMs like LINQ to SQL and Entity Framework increases, it makes me question using native queries and stored procedures.

I am naturally geared towards SQL and the direct contact with the RDBMS. I enjoy the pure control over what happens, and I like my traces showing exactly what I’m calling in code (stored procedures, etc.).

But what are the gains of ORMs that I am missing out on? Is it just the rapid development process? The lack of necessity to administer the database and objects included?

What am I missing out on by not using EF and LINQ to SQL?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I think biggest impact here is productivity; it’s real simple to use EF (or any other ORM) to build simple CRUD interfaces. But problems comes when you do not fully understand that’s going on.

    For example, lets suppose a big object, with several sub collections; ORMs have a limit do understand how that data is integrated and must return data denormalized to materialize that object. And that can be a huge impact on data transfer.

    Another thing is about performance. Maybe you get an user interface which should do many calculations, or to update a big object and its dependencies. In this case, I suggest to use native access (stored procedures, etc) to unleash your RDBMS full potential.

    Summary: simple interfaces, ORM; medium to complex interfaces, stored procedures.

    • 0