Click here to Skip to main content
15,798,825 members
Please Sign up or sign in to vote.
1.00/5 (2 votes)
See more: , +
why we are using Entity Framework even though native SQL Sever is more faster than ORM why we are using this?

What I have tried:

SQL Storied procedures or compiled queries are more faster the our server side queries (ORM) but why we are using ORM like entity frame work with out moving to
Updated 23-Feb-20 16:57pm

Not everyone is using ORMs...
There are a few reasons why many people are using them:

Rapid Development- Using an ORM can create your classes from your tables or vice versa, with little to no thought needed from the developer.

Cheaper Development- a NET developer is not paid as much as someone who also has DBA experience.

Portability- Even though different database types have differing syntax, the EF methods will remain the same.
Share this answer
An ORM and a database engine are two distinct tools which fulfill distinct requirements.
Your question is a bit like asking 'Why should I use a screwdriver when I have a chainsaw?'
Share this answer
On building any any solutions, not everyone have same priority as their product to run faster, some might want to finish the product faster so if they want to do it in faster way by spending less time and resources ORM provides the automated tools and methods which will help to finish the product faster hence, if you want the system to run faster,they use native SQL Sever and do add required things manually, if they want to finish work faster they use entity framework. Framework makes coding easier, runs slower.
Share this answer

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900