Skip to main content

Entity Framework Versus LINQ To SQL (comparison summary)

LINQ to SQL and ADO.NET Entity Framework are extensions of ADO.NET and are introduced to avoid difficulties involved in writing programs using object oriented programming languages to access data residing in RDBMS.

Entity Framework
LINQ To SQL is easier to use.
Entity Framework is more complex compared to LINQ To SQL.
DB Server Support
LINQ To SQL supports only Microsoft SQL Server.
Entity Framework is built on top of ADO.NET data provider model and thus supports all existing ADO.NET data providers  i.e. IBM DB2, Sybase, Oracle, SQL Azure etc.
File Type
It uses Database Markup Language (DBML) file that contains XML mappings of entities to tables.
Entity Framework uses four files EDMX, CSDL, SSDL and MSL. The later three are generated at runtime.
Used for rapid application development.
EF is used for enterprise n-tier application.
LINQ To SQL is tightly coupled - object property to specific field of database or more correctly object mapping to a specific database schema
EF is loosely coupled.
LINQ To SQL provides one-to-one mapping of tables to classes.
Entity Framework enable decoupling DB Server (Database Schema) and Entity Representation in terms of Model (Conceptual Schema). You can map one table to multiple entities or multiple tables to one entity.
Mapping Type
In LINQ To SQL each table is mapped to single class. Join table must be represented as a class. Also, complex types cannot be easily represented without creating separate table.
In Entity Framework a class can map to multiple tables.
In LINQ To SQL inheritance is difficult to apply. It supports Table Per Class Hierarchy (TPH).
In Entity Framework inheritance is simple to apply. It supports Table Per Class Hierarchy (TPH) and Table Per Type (TPT). It also provides limited support of Table Per Concrete Class (TPC).
Complex Type
LINQ To SQL does not support the creation of complex types.
Entity Framework supports the creation of complex types.
LINQ To SQL is simple to learn and implement for Rapid Application Development, but it will not work in complex applications.
Entity Framework has more features which will take time to learn and implement, but it will work in complex applications.
Query Capability
LINQ To SQL has DataContext object through which we can query the database.
With the Entity Framework, we can query database using LINQ To Entities through the ObjectContext object and ESQL (provides SQL like query language). In addition, Entity Framework has ObjectQuery class (used with Object Services for dynamically constructing queries at runtime) and EntityClient provider (runs query against conceptual model).
LINQ To SQL is slow for the first time run. After first run provides acceptable performance.
Entity Framework is also slow for the first run, but after first run provides slightly better performance compared to LINQ To SQL.
Generate Database from Model
It has no capability to generate database from Model.
Entity Framework supports generation of database from Model.
Future Enhancement
Microsoft intended to obsolete LINQ To SQL after the Entity Framework releases. So it will not receive any future enhancements.
Entity Framework has future enhancements.

So while there is a lot of overlap, LINQ to SQL is targeted more toward rapidly developing applications against your existing Microsoft SQL Server schema, while the Entity Framework provides object- and storage-layer access to Microsoft SQL Server and 3rd party databases through a loosely coupled, flexible mapping to existing relational schema.
For detailed description about EF with sample please check here

Popular posts from this blog

C#: Merging Excel cells with NPOI HSSFWorkbook

In this post we’ll see how to merge the two or more cell with each other while creating the excel sheet using NPOI.
Mentioned below is code to merge multiple cells, in this example we are merging first cell to fifth cell of first row (you can adjust row or cell range by passing particular parameters in CellRangeAddress).
//Created new Workbook var hwb = new NPOI.HSSF.UserModel.HSSFWorkbook(); //Create worksheet with name. var sheet = hwb.CreateSheet("new sheet"); //Create row and cell. var row = sheet.CreateRow(0); var cell = row.CreateCell(0); ; //Set text inside cell cell.SetCellValue("This is Merged cell"); cell.CellStyle.WrapText = true; //define cell range address // parameters: -> first row to last and first cell to last cell var cra = new NPOI.SS.Util.CellRangeAddress(0, 0, 0, 4); //Add merged region to sheet. sheet.AddMergedRegion(cra);
Hope this solution helps you J

Calculate Sum and average of two or more Textbox values using JQuery

We can calculate sum and average of values entered in textboxes with the help of small piece of jQuery code.
First of all let’s create a HTML form where we’ll ask user to enter marks in each subject, under body section add following HTML:
<tableclass="demo-table"> <trclass="label"> <tdcolspan="2">Please enter marks(0-99):</td> </tr> <tr> <td>English</td> <td> <inputtype="text"class="txtMarks"name="txtMarks"

Difference between Web API, WCF and Web Service

So now we have got the basic idea about Web API, now let’s do some comparison of Web API with WCF and web services.
Web Service WCF Web API Web services created as file with .asmx extension. WCF create with .svc extension Web API are simple class file with .cs(for C#) extension. Web API is inherited from “ApiController” and class name must end with “Controller”. It is SOAP based service and return data in XML form. It is also based on SOAP and return data in XML form. Web API is HTTP based service and by default it return data in JSON or XML form. It supports only HTTP protocol. It supports various protocols like TCP, HTTP, HTTPS, Named Pipes, and MSMQ. It supports HTTP protocol. It can be hosted only on IIS. It can be hosted with in the application or on IIS or using window service. It can be hosted with in the application or on IIS. It is not open source but can be consumed by any client that understands xml. It is not open source but can be consumed by any client t…