Your SlideShare is downloading. ×
Difference between entity sql and transact sql
Difference between entity sql and transact sql
Upcoming SlideShare
Loading in...5

Thanks for flagging this SlideShare!

Oops! An error has occurred.

Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Difference between entity sql and transact sql


Published on

Difference Between Entity SQL and Transact-SQL

Difference Between Entity SQL and Transact-SQL

Published in: Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

No notes for slide


  1. Articles from Jinal Desai .NETDifference Between Entity SQL and Transact-SQL2013-06-04 17:06:02 Jinal DesaiEntity SQL is a SQL-like language that enables you to query conceptual models inthe Entity Framework. Conceptual models represent data as entities andrelationships, and Entity SQL allows you to query those entities and relationships ina format that is familiar to those who have used SQL. Transact-SQL is extension toSQL created for communicating with SQL Server. All applications that communicatewith an instance of SQL Server do so by sending Transact-SQL statements to theserver, regardless of the user interface of the application.Both sounds similar but there are many differences between these two. Followingtable represents those differences.Entity SQL Transact-SQLIs a language similar to SQL used to workwith an Entity Data Model (EDM).Is an ANSI SQL language used forstored procedures and functions.Is used to work with conceptual entities bysupporting features like inheritance andrelationships.Is used to write stored procedures inrelational databases.Supports collections and considers themas first class entities.Does not support collections but doessupport subqueries and expressions.Interprets all subqueries to be multisetsubqueries, irrespective of the context inwhich they are used.Interprets subqueries as per thecontext in which they are used.Allows expressions defined in a fromclause to reference earlier expressionsdefined to the left in the same clause.Does not allow expressions toreference earlier expressions definedin the same scope, such as in aselect clause.Table columns can only be referenced byqualifying them with a table alias, except infrom clauses where table aliases areoptional.Table columns are referenceddirectly.Uses the “.” notation to navigate throughthe properties of an object.Uses the “.” notation to referencecolumns.Does not support the * construct. Supports the * construct.Supports SQL-style aggregates andcollection-based aggregates.Supports only SQL-basedaggregates.Allows nested ORDER By expressionsanywhere in the queries.Allows ORDER By clauses only in thetop most SELCT, FROM, and
  2. anywhere in the queries.WHERE clauses of the queries.Identifiers are compared according to thecase and accent.Identifiers are compared according tothe current database collation.Supports a subset of Transact-SQL’s builtin functions and operators.Supports additional functionalities thatare not supported in Entity SQLincluding:Analytic FunctionsBuiltin Functions, OperatorsDDLDML -insert, update, delete.