Welcome to Scribd. Sign in or start your free trial to enjoy unlimited e-books, audiobooks & documents.Find out more
Standard view
Full view
of .
Look up keyword
Like this
0 of .
Results for:
No results containing your search query
P. 1
LINQ Difference FAQS Compiled-1

LINQ Difference FAQS Compiled-1

|Views: 30|Likes:
Published by Umar Ali
This is compiled version(part-1) of LINQ Difference FAQS
This is compiled version(part-1) of LINQ Difference FAQS

More info:

Published by: Umar Ali on Sep 25, 2012
Copyright:Attribution Non-commercial


Read on Scribd mobile: iPhone, iPad and Android.
download as PDF, TXT or read online from Scribd
See more
See less





LINQ Difference FAQs-1
1.Difference between LINQ and SQLS.NoLINQSQL
1LINQ Stands for languageintegrated query.SQL stands for StructuredQuery Language.2LINQ Statements are verifiedduring compile time.SQL statements can be used in aapplication gets verified for their syntaxes only in the run time.3To use LINQ we can dependupon our .Net Languagesyntaxes and also we canconsume base class libraryfunctionalities.To use SQL we need to be familiar with SQL syntaxes and also thepre-defined functions of SQL likeMAX,MIN,LEN and SUBSTRINGetc...4LINQ Statements can bedebugged as they executeunder framework environment.SQL . As SQL statements execute onDatabase server debugging of thecode is not possible.
2.Difference between LINQ to SQL and Entity FrameworkS.NoLINQ to SQLEntity Framework
1It only works with Sql server. It works with variety of db products.2Used for rapid applicationdevelopment.Cannot used for rapid applicationdevelopment.3It does not support for complextype.It provides support for complextype.4It cannot generate db frommodel.It can generate db from model.5Mapping type ( class to singletable)Mapping type ( class to multipletables)6We can query data usingDataContext.We can query data usingesql,object services,entity clientand linq to entities.
Another Good Reference:
S.NoLINQStored Procedures
1As LINQ is part of .NET, wecan use visual studio’sdebugger to debug the queriesIt is really very hard to debug theStored Procedure2With LINQ everything getscomplied into single DLL hencedeployment becomes easy.With Stored Procedures, we needto provide an additional script for deployment3LINQ is type safe, so querieserrors are type checked atcompile time.It is really good toencounter an error whencompiling rather than runtimeexception!Stored Procedures are not typesafe i.e., error can be caught onlyduring runtime.4LINQ supports multipledatabasesWith Stored Procedures whichneed to be re-written for differentdatabases.5LINQ supports abstractionwhich allows framework to addadditional improvements likemulti threading. It is muchsimpler and easier to add thissupport through LINQ thanStored Procedures. As Stored Procedures does notsupport abstaction , so it is difficultto add additional impovements likemulti threading6LINQ queries need to compilebefore execution.Therefore,LINQ is slower than StoredProcedures.Stored Procedures are ster thnLINQ because they areprecompiled i.e., StoredProcedures have a predictableexecution plan.Therefore, if astored procedure is being executedfor the second time, the databasegets the cached execution plan toexecute the stored procedure.
4.Difference between LINQ to SQL and LINQ to ObjectsS.NoLINQ to SQLLINQ to Objects
1LINQ to SQL needs a DataContext object. The DataContext object is the bridgeLINQ to Objects does not need anyintermediate LINQ provider or API.
between LINQ and thedatabase.2LINQ to SQL returns data otype IQueryableLINQ to Objects returns data of type IEnumerable.3LINQ to SQL is translated toSQL by way of ExpressionTrees, which allow them to beevaluated as a single unit andtranslated to the appropriateand optimal SQL statements.LINQ to Objects does not need tobe translated.4LINQ to SQL is translated toSQL calls and executed on thespecified databaseLINQ to Objects is executed in thelocal machine memory.
5.Difference between LINQ to SQL and LINQ to EntitiesS.NoLINQ to SQLLINQ to Entities
1Does not support ConceptualData ModelSupports Conceptual Data Model2Does not support StorageSchemaSupports Storage Schema3Does not support MappingSchemaSupports Mapping Schema4Does not support New Data Access Provider Supports New Data AccessProvider 5Does not support Non-SQLServer Database SupportSupports Non-SQL Server Database Support6Supports Direct DatabaseConnectionDoes not support Direct DatabaseConnection7Does not support Multiple-tableInheritanceSupports Multiple-table Inheritance8Does not support Single Entityfrom Multiple TablesSupports Single Entity fromMultiple Tables

You're Reading a Free Preview

/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->