What is the difference between an orm and ADO.net?

ado.net c# entity-framework linq-to-sql orm

Question

I am reading a book and it says : "if you will create your own data access layer by using ADO.NET for access into you database, you will be minimally affected whether the data schema exists or not. If however you are using an O/RM, your flexibility will be limited by the tool you use". What is the major difference between ADO.NET and any other ORM?

1
11
11/9/2016 11:53:24 AM

Fastest Entity Framework Extensions

Bulk Insert
Bulk Delete
Bulk Update
Bulk Merge

Accepted Answer

ADO.NET provides consistent access to data sources such as SQL Server and XML, and to data sources exposed through OLE DB and ODBC. Data-sharing consumer applications can use ADO.NET to connect to these data sources and retrieve, handle, and update the data that they contain.

ADO.NET separates data access from data manipulation into discrete components that can be used separately or in tandem. ADO.NET includes .NET Framework data providers for connecting to a database, executing commands, and retrieving results. Those results are either processed directly, placed in an ADO.NET DataSet object in order to be exposed to the user in an ad hoc manner, combined with data from multiple sources, or passed between tiers. The DataSet object can also be used independently of a .NET Framework data provider to manage data local to the application or sourced from XML.

ADO.NET is a layer that allows you to connect to DB and modify it using SQL connections, commands, parameters. ADO.NET MSDN

Object-relational mapping (ORM, O/RM, and O/R mapping tool) in computer science is a programming technique for converting data between incompatible type systems in object-oriented programming languages. This creates, in effect, a "virtual object database" that can be used from within the programming language. There are both free and commercial packages available that perform object-relational mapping, although some programmers opt to construct their own ORM tools.

Entity Framework and NHibernate are ORMs. It means that you do not operate by SQL connections, commands, parameters - ORM does it for you and it allows to map your database structure in OOP manner: you can add, read, update, delete records in your DB using objects in C#. You need only map your object to DB correctly. Entity Framework is built on ADO.NET and it uses ADO.NET inside. SQL statements are generated by ORM. ORM

Generally, access to DB without ORM is faster, but you should provide more lines of code. If you want to operate your DB in OOP manner and write more readable code you should choose ORM. It depends on your purposes on what to choose.

There are Micro ORMs (Dapper, BLToolkit) which allows you to write SQL queries and map parameters to object properties. Micro ORMs, in general, have better performance than Full ORMs, but ADO.NET is still faster.

Also, there are some questions and answers on StackOverflow: EF vs ADO.NET

10
9/11/2019 3:28:16 PM

Popular Answer

  • Along the way, I have learned that developers hate working with DataSets and DataReaders
  • .NET platform defines a number of namespaces that allow you to interact with relational database systems. Collectively speaking, these namespaces are known as ADO.NET.
  • ORM stands for Object-Relational Mapper which is to map an object with a relational world. As the name suggests it builds a relation / maps objects (model) to database objects(tables).
  • ADO.NET was the traditional way to connect your application to a database & gave the developer entire control over the database operations whereas ORM is built on top of ADO.NET and uses ADO.NET implicitly.
  • In short using an ORM like NHibernate, Entity Framework makes life simpler where mapping of objects(models) is taken care of internally by the ORM.
  • When you use an ORM not everything is in your hands since all of the queries are generated by the ORM itself. Now we don't know whether those queries are optimized or not.

In scenarios where performance of your application is a primary concern & absolutely critical OR in scenarios where you know that your application will grow huge in mere future then it is advisable to use ADO.NET rather than Entity Framework because it makes your application heavy.

  • The solution to this was Micro ORM's like Dapper, BLToolkit. These provide the esssence of what developers want - an easy way to map Database operations to strongly typed classes.
  • LINQ support in some makes it even better.But the main advantage of some of these Micro-ORMs is its raw speed.

Words of Wisdom:

  1. Dapper just does mapping but you need to code a lot , EF does much more on the top of it and not just mapping. So EF will be slow.
  2. I can also say that pure ADO.NET is faster than Dapper , OLEDB is faster than ADO.NET and ODBC can be faster than OLEDB.
  3. So if I am serious about performance I would probably avoid any ORM.
Tahir77667

Related Questions

ADO.NET + C# + LINQ Join two tables using EF and return everything without having to define all fields explicitly.

Is this what you need?... var result = from itemA in TableA join itemB in TableB on itemA.ID equals itemB.ID select new { itemA, itemB }; ...Alternately, you could declare a result class that helps you build the result object without specifying all the fields:... class ItemAB { public ItemAB(Item...
ado.net c# entity-framework linq
asked by bruno conde

Entity validation best practices in ASP.NET MVC and ADO.NET Entity Framework

i am using ASP.NET MVC & ADO.NET Entity Framework in a project. I want to add validation logic to my entities via partial classes. It works similar like shown in the ...NerdDinner.com ASP.NET MVC Application... which is using LINQ2SQL. The main difference is, that i have to use the"OnPropertyChanging" event instead the "OnValidating" like in LINQ2S...
.net asp.net-mvc entity-framework validation
asked by Alexander

Unable to load the native components of SQL Server Compact corresponding to the ADO.NET provider

In my project, I use SQL CE 3.5 database with entity framework and followed ...this article... but i have this exception :...Unable to load the native components of SQL Server Compact corresponding to the ADO.NET provider of version 8080. Install the correct version of SQL Server Compact. Refer to KB article 974247 for more details....All details...
c# entity-framework sql-server-ce
asked by Tarek Saied

No Entity Framework provider found for the ADO.NET provider with invariant name 'System.Data.SqlClient'

I just got into the same problem and it looks like EntityFramework although installed from NuGet Package Manager was not correctly installed in the project....I managed to fix it by running the following command on ...Package Manager Console...:...PM> Install-Package EntityFramework
entity-framework
asked by douglaslps

No Entity Framework provider found for the ADO.NET provider with invariant name 'Oracle.ManagedDataAccess.Client'

The current version of the ...Oracle Managed ODP... is not compatible with ...EF 6..., learned this the hard way. Use ...EF 5... instead....There is a ticket open at oracle support, I can't find it right now though....EDIT...I got another upvote on this today, so I thought I'd add that the newest version of ...ODP.net... now supports ...EF 6.......
.net asp.net-mvc-4 c# entity-framework oracle
asked by flindeberg

No Entity Framework provider found for the ADO.NET provider with invariant name 'System.Data.SqlClient'.

We are using EntityFramework 6 with Code First. We have a console app that has no reference to EntityFramework but reads the connection string from its App.config. It calls the DatabaseInitializationUtilities assembly passing the connection string as a parameter. ...DatabaseInitializationUtilities has the reference to EF6 (EntityFramework and Ent...
.net asp.net c# entity-framework-6 sql-server
asked by Dewey

Delete row ASP.NET MVC ADO.NET entity Model

You want to also remove the ms_person and ms_user?...Do this....db.ms_student.Remove(ms_student); if (ms_student.ms_person != null) { db.ms_person.Remove(ms_student.ms_person); if (ms_student.ms_person.ms_user != null) { db.ms_user.Remove(ms_student.ms_person.ms_user); } } db.SaveChanges();
ado.net asp.net asp.net-mvc c# entity-framework
asked by Yuliam Chandra

ADO.NET provider with invariant name 'System.Data.SqlClient;' cannot be found (Entity Framework MVC)

You have this:...<add name="ReadContext" connectionString="Server=Sql2014intsnace;Database=database;User Id=secret; Password=secret;" providerName="System.Data.SqlClient;" /> <-- semi-colon ...It should be this:...<add name="ReadContext" connectionString="Server=Sql2014intsnace;Database=database;User Id=secret; Password=secret;" ...
.net asp.net asp.net-mvc entity-framework entity-framework-6
asked by Tieson T.

When comparing Entity Framework to ADO.NET, why is dapper ORM so fast?

Please mention the reason of Fast execution of dapper ORM by comparing Entity Framework and ADO.NET. I got the reference for comparison from the link ...dapper vs entity framework
ado.net compare dapper entity-framework-6 performance
asked by Muruga

What exactly is the difference between ORM and micro ORM?

Please mention the difference between (big) ORM and micro ORM. What are the advantages of micro ORM over big ORM. For eg. the difference between entity framework ORM and dapper micro ORM.
dapper difference entity-framework-6 micro-orm orm
asked by Muruga

Fastest Entity Framework Extensions

Bulk Insert
Bulk Delete
Bulk Update
Bulk Merge
View more on Stack Overflow

Prime Library

Performance

Expression Evaluator

More Projects...

Related

Licensed under: CC-BY-SA with attribution
Not affiliated with Stack Overflow
Licensed under: CC-BY-SA with attribution
Not affiliated with Stack Overflow