This document provides an overview of the evolution of data access application programming interfaces (APIs) used in Microsoft technologies, including ADO.NET 1.0, LINQ, and the ADO.NET Entity Framework. It discusses the goals and features of each API, how they address challenges in working with data, and how they improved developer productivity. It also describes the architecture and components of the Entity Framework, how it maps object and relational models, and techniques for customizing data mappings.

1.  Jose A. Blakeley
Partner Architect
Microsoft Corporation
 Michael Pizzo
Principal Architect
Microsoft Corporation

2. 




3. 








 ADO.NET 1.0
 Building a Data Platform
 The ADO.NET Entity Framework

4. 









5. 











6. 













7. 














8. 











9.  Evolution of Data Access APIs


 Getting Data from a SQL Database
 Working with Data
 ADO.NET and XML
 Building a Data Platform
 The ADO.NET Entity Framework

10. Managed Provider
DataReader
Command
Connection
Controls,
Designers,
Code-gen, etc
DataSet
DataAdapter
XmlReader
XmlWriter
OLTP operations,
Programmatic Processing,
Frameworks

11. ADO.NET Data Provider













Data
store
Data
Provider
Connection
CreateCommand()
ExecuteReader()
DataReader
Command ParametersParametersParameters

12. 









DataSet DataSet
Tables
Table
Columns
Column
Constraints
Constraint
Rows
Row
Relations
Relation

13. 











14. 








Data
store
DataAdapter
MappingsMappingsMappings
InsertCommand
UpdateCommand
DeleteCommand
SelectCommand
Fill() Update()
DataSet

15. 










16.  Evolution of Data Access APIs
 ADO.NET 1.0
 Building a Data Platform
 Why a Conceptual Model?
 The Microsoft Entity Data Model
 Entity SQL
 The ADO.NET Entity Framework

17. 







Programming Data is Hard

18. 








Increase Developer Productivity

19. 





20. 




 The Need…
 Applications work with a well
Defined Model
 Storage Schema Abstraction
 Declarative mapping between
application and storage models
 No brittle, hard-coded mapping

21. 

















SalesPerson
EmployeeID = 729742
LoginID = pete
Title = "Developer"
VacationHours = 0
…
ExpenseAccount = …
CarLicenseNum = …
…
SalesPerson
EmployeeID = 729742
LoginID = pete
Title = "Developer"
VacationHours = 0
…
ExpenseAccount = …
CarLicenseNum = …
…
SalesPerson
EmployeeID = 729742
LoginID = pete
Title = "Developer"
VacationHours = 0
…
ExpenseAccount = true
…
SalesPerson
EmployeeID = 294272
LoginID = adam
Title = "Dev Lead"
VacationHours = 0
…
Reports
Manager
11
N

22. 














23.  Data Access in the 80s
 ADO.NET 1.0
 Building a Data Platform


 Entity Designer
 EntityClient
 Object Services

25.  Data Access in the 80s
 ADO.NET 1.0
 Building a Data Platform
 The ADO.NET Entity Framework
 Overview

 EntityClient
 Object Services

26. 









27. 











28.  Data Access in the 80s
 ADO.NET 1.0
 Building a Data Platform
 The ADO.NET Entity Framework
 Overview
 Entity Designer

 Object Services

29. 















30.  Data Access in the 80s
 ADO.NET 1.0
 Building a Data Platform
 The ADO.NET Entity Framework
 Overview
 Entity Designer
 EntityClient


31. 











32. 




33. 









34. // Lambda Expressions
string[] names = { "Luis", "Mary", "Mike", "Jose" };
Display( names, s => s.Length > 3);
// Anonymous Types and object initialization
var emp = new { Name = "Mary", Company = "Microsoft",
Age = 30 };
// Extension Methods
public static class ExtensionMethods {
public static void Display<T>(this T[] names,
Func<T, bool> filter) {
foreach (T s in names) {
if (filter(s)) Console.WriteLine(s);
}
}
}
// Query Expressions
var query = from c in Customers
where c.Discount >= 3.0 && c.Discount < 4.0
select new { c.Name, Perc = c.Discount / 100.0 };

35.  Introduction to LINQ




 LINQ to Entities
 LINQ to DataSet

36. 








DirectMapping

37. StronglytypedSQLDatabase













38. 















Features

39.  Introduction to LINQ
 LINQ to SQL




 LINQ to DataSet

40. FlexibleMappingtoRelationalData
•
•
•
•
•
•
•
•
•


41. Features















42.  Introduction to LINQ
 LINQ to SQL
 LINQ to Entities


43. LINQoverDisconnectedCachewithChangeTracking











44. TypedandUnTyped

 AsEnumerable()

 Field<T>(columnName)

var query = from row in myDataSet.Tables["Customers"].AsEnumerable()
where row .Field<string>("City") == "London"
select new { row.Field <string> ("CustomerID"),
row.Field <string> ("ContactName") } ;
var query = from customer in northwind.Customers
where customer.City == "London"
select customer;
 Typed DataSet
 Use strongly typed accessors

45. 











46. 




47. 










Customizing Data Classes

48.  Customizing Data Classes
 Entity Framework Mapping Scenarios
 Core Mapping Scenarios
 Function Mapping
 Mapping Limitations
 Database Design Considerations
 Advanced Mapping Techniques

49. 











50. 





51. 








52. 








53.  Customizing Data Classes
 Entity Framework Mapping Scenarios
 Database Design Considerations





54. 










55. <Schema Namespace="AdventureWorksModel" Alias="Self"
xmlns="http://schemas.microsoft.com/ado/2006/04/edm">
<EntityContainer Name="AdventureWorksEntities">
<EntitySet Name="Contacts"
EntityType="AdventureWorksModel.Contact" />
<AssociationSet Name="ManagerEmployees"
Association="AdventureWorksModel.ManagerEmployee">
<End Role="Employees" EntitySet="Contacts" />
<End Role="Manager" EntitySet="Contacts" />
</AssociationSet>
</EntityContainer>
<EntityType Name="Contact">
<Key>
<PropertyRef Name="ContactID" />
</Key>
<Property Name="ContactID" Type="Int32" Nullable="false" />
<Property Name="Title" Type="String" />
<Property Name="FirstName" Type="String" Nullable="false" />
<Property Name="LastName" Type="String" Nullable="false" />
</EntityType>
<Association Name="ManagerEmployee">
<End Role="Employees"
Type="AdventureWorksModel.Employee" Multiplicity="*" />
<End Role="Manager"
Type="AdventureWorksModel.Employee" Multiplicity="0..1" />
</Association>
</Schema>

56. <Schema Namespace="AdventureWorksModel.Store" Alias="Self"
Provider="System.Data.SqlClient" ProviderManifestToken="2008"
xmlns:store="http://schemas.microsoft.com/ado/2007/12/edm/EntityStoreSchemaGenerator"
xmlns="http://schemas.microsoft.com/ado/2006/04/edm/ssdl">
<EntityContainer Name="HumanResources">
<EntitySet Name="Contact"
EntityType="AdventureWorksModel.Store.Contact" Schema="Person" />
<AssociationSet Name="FK_Employee_Employee_ContactID"
Association= "AdventureWorksModel.Store.FK_Employee_Employee_ContactID">
<End Role="Employees" EntitySet="Employee" />
<End Role="Manager" EntitySet="Employee" />
</AssociationSet>
</EntityContainer>
<EntityType Name="Contact">
<Key>
<PropertyRef Name="ContactID" />
</Key>
<Property Name="ContactID" Type="int" Nullable="false" StoreGeneratedPattern="Identity" />
<Property Name="Title" Type="nvarchar" />
<Property Name="FirstName" Type="nvarchar" Nullable="false" />
<Property Name="LastName" Type="nvarchar" Nullable="false" />
</EntityType>
<Association Name="FK_Employee_Employee_ContactID">
<End Role="Employees" Type="AdventureWorksModel.Store.Employee" Multiplicity="*" />
<End Role="Manager" Type="AdventureWorksModel.Store.Employee" Multiplicity="0..1" />
</Association>
</Schema>

57. <Mapping Space="C-S" xmlns="urn:schemas-microsoft-com:windows:storage:mapping:CS">
<EntityContainerMapping StorageEntityContainer="HumanResources"
CdmEntityContainer="AdventureWorksEntities">
<EntitySetMapping Name="Contacts"
TypeName="AdventureWorksModel.Contact" StoreEntitySet="Contact">
<ScalarProperty Name="ContactID" ColumnName="ContactID" />
<ScalarProperty Name="Title" ColumnName="Title" />
<ScalarProperty Name="FirstName" ColumnName="FirstName" />
<ScalarProperty Name="MiddleName" ColumnName="MiddleName" />
<ScalarProperty Name="LastName" ColumnName="LastName" />
</EntitySetMapping>
<AssociationSetMapping Name="ManagerEmployees"
TypeName="AdventureWorksModel.ManagerEmployee" StoreEntitySet="Employee">
<EndProperty Name="Employees">
<ScalarProperty Name="ContactID" ColumnName="ContactID" />
</EndProperty>
<EndProperty Name="Manager">
<ScalarProperty Name="ContactID" ColumnName="ManagerID" />
</EndProperty>
<Condition ColumnName="ManagerID" IsNull="false" />
</AssociationSetMapping>
</EntityContainerMapping>
</Mapping>

58.  Customizing Data Classes
 Entity Framework Mapping Scenarios
 Database Design Considerations
 Advanced Mapping Techniques
 Anatomy of an .edmx file

 Custom Mapping

59. 
<ComplexType Name ="FullName">
<Property Name="Title" Type="String" />
<Property Name="FirstName" Type="String" Nullable="false" />
<Property Name="MiddleName" Type="String" />
<Property Name="LastName" Type="String" Nullable="false" />
</ComplexType>
<EntityType Name="Contact">
<Key>
<PropertyRef Name="ContactID" />
</Key>
<Property Name="ContactID" Type="Int32" Nullable="false" />
<Property Name="Name" Type="Self.FullName" Nullable="false"/>
<!-- … -->
</EntityType>
 Use your ComplexType in your Entities
 Map the Complex Type in your MSL
<EntitySetMapping Name="Contacts" TypeName="AdventureWorksModel.Contact"
StoreEntitySet="Contact">
<ScalarProperty Name="ContactID" ColumnName="ContactID" />
<ComplexProperty Name="Name">
<ScalarProperty Name="Title" ColumnName="Title" />
<ScalarProperty Name="FirstName" ColumnName="FirstName" />
<ScalarProperty Name="LastName" ColumnName="LastName" />
</ComplexProperty>
</EntitySetMapping>

60.  Entity Framework Mapping Scenarios
 Database Design Considerations
 Customizing Data Classes
 Advanced Mapping Techniques
 Anatomy of an .edmx file
 Complex Types


61. 






Customize Conceptual Definition

62. 






Customize Mapping Definition

63. 








64. 








65. 



 ADO.NET and SQL Server
 Futures
 Summary:ADO.NETAto Z

66. 
















67. 











68. 














69. 











70.  DataAccessAcross Tiers











 Futures

71. 







72. 


 Simple programming model
 Strongly typed
 Reduce client/server round trips
 Do not cause a statement to recompile
CREATE TYPE myTableType AS TABLE
(id INT, name NVARCHAR(100),qty
INT);
CREATE PROCEDURE myProc (@tvp
myTableType READONLY) AS
UPDATE Inventory SET
qty += s.qty
FROM Inventory AS i INNER JOIN
@tvp AS tvp
ON i.id = tvp.id
GO

73. TVP Client Stack Support

 SqlDbType.Structured





74. ADO.NET Example using DataTable
Using (MyConnection){
//Create a data table
DataTable dt = new DataTable(“TVPOrdersDataTable”);
dt.Columns.Add(“ProductType”, typeof(string));
dt.Columns.Add(“Quantity”, typeof(int));
// Add rows
dt.Rows.Add(“Canon Digital Camera”, 20);
dt.Rows.Add(“June”, 10);
dt.Rows.Add(“Xbox-360”, 8);
// Create a command and bind parameter
SqlCommand tvp_cmd = new
SqlCommand(“sp_UpdataInventory”,
MyConnection);
SqlParameter tvpParam =
tvp_cmd.Parameters.AddWithValue(
@OrdersTvp, dt);
//Execute command
tvp_cmd.ExecuteNonQuery();

76. SqlCommand command =
new SqlCommand(string.Empty, sqlConnection);
command.CommandText = "insert into MoviesRented
values(@customerId, @MovieID, @RentalDate,
@DueDate)";
….
// create a parameter for RentalDate
SqlParameter rentDateParam = new SqlParameter("RentDate",
System.Data.SqlDbType.DateTimeOffset);
rentDateParam.Value = DateTimeOffset.Now;
command.Parameters.Add(rentDateParam);
// create a parameter for DueDate
SqlParameter dueDateParam = new SqlParameter("DueDate",
System.Data.SqlDbType.DateTimeOffset);
dueDateParam.Value = DateTimeOffset.Now.AddDays(7);
command.Parameters.Add(dueDateParam);
….

77. // create a command to get the DueDate
SqlCommand command =
new SqlCommand(String.Empty, sqlConnection);
command.CommandText =
"select DueDate from MoviesRented where MovieId = @MovieId";
…
// Execute the DataReader
//
using (SqlDataReader dataReader = command.ExecuteReader())
{
if (dataReader.Read() == false)
{
Console.WriteLine("Movie has not been rented");
}
DateTimeOffset dueDate =
dataReader.GetDateTimeOffset (0);
Console.WriteLine("Movie due back on : {0}", dueDate);
}

78. 










79. // Poll for completion
IAsyncResult result = cmd.BeginExecuteReader();
while(!result.IsCompleted) {
// do some work
}
SqlDataReader reader = cmd.EndExecuteReader(result);
// Use a Callback
IAsyncResult result = cmd.ExecuteReader(
new AsyncCallback( myDataCallback ));
// do other work…
// optionally wait using sync object
result.WaitHandle.WaitOne();
public void myDataCallback( IAsyncResult result ) {
SqlDataReader reader = cmd.EndExecuteReader(result);
}

80. 









81. 









82. public SqlDataReader GetProducts(int Category) {
SqlCommand cmd = new SqlCommand(
"Select ProductName, UnitPrice from Products " +
"where CategoryID = @CatID", cnn);
cmd.Parameters.Add("@CatID",Category);
cmd.Notification = new SqlNotificationRequest(
Category.ToString(), // message
"myQueue", // message body
3000); // timeout
return cmd.Execute();
}
public void WaitForChanges() {
SqlCommand cmd = new SqlCommand(
"Receive message_body from myQueue " +
"WITH wait_for_results", cnn);
cmd.CommandTimeout = 0;
int category = (int)cmd.ExecuteScalar();
Console.WriteLine("Category {0} changed.",category);
}

83. 



public void LoadFromDataReader(IDataReader reader)
{
// Copy the Data to SqlServer
SqlBulkCopy bcp =
new SqlBulkCopy( connectString );
bcp.DestinationTableName = "Customers";
bcp.WriteToServer( reader );
}

84. 














85. SqlConnection cnn = new SqlConnection(connectString);
cnn.Open();
SqlCommand cmd =
new SqlCommand("SELECT p FROM PointTable", cnn );
SqlDataReader reader = cmd.ExecuteReader();
while( reader.Read() )
{
Point point=(Point)reader[0];
Console.WriteLine(
"x:{0}, y:{1}", point.x, point.y );
}
cnn.Close();

86. Aggregates
AVG
CHECKSUM_AGG
COUNT
COUNT_BIG
MAX
MIN
STDEV
STDEVP
VAR
VARP
String Functions
ASCII
CHAR
CHARINDEX
DIFFERENCE
LEFT
LEN
LOWER
LTRIM
nchar
PATINDEX
QUOTENAME
REPLACE
REPLICATE
REVERSE
RIGHT
RTRIM
SOUNDEX
SPACE
STR
STUFF
SUBSTRING
UNICODE
UPPER
Math Functions
ABS
ACOS
ASIN
ATAN
ATN2
CEILING
COS
COT
DEGREES
EXP
FLOOR
LOG
LOG10
PI
POWER
RADIANS
RAND
ROUND
SIGN
SIN
SQRT
SQUARE
TAN
Date Functions
DATEADD
DATEDIFF
DATENAME
DATEPART
DAY
GETDATE
SYSDATETIME
SYSUTCDATETIME
SYSDATETIMEOFFSET
GETUTCDATE
MONTH
YEAR
System Functions
DATALENGTH
CHECKSUM
NEWID
CURRENT_TIMESTAMP
CURRENT_USER
HOST_NAME
USER_NAME
ISNUMERIC
ISDATE

87.  DataAccessAcross Tiers
 ADO.NET and SQL Server


88. 













89. 









90. 












91. 














92. © 2008 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market
conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation.
MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.