Summary Data Access from A to Z
Emitting live from a big ass room filled with data access geeks while doing a factory restore without Lenovo's crapware. Approximately two hours away from a cold beer and typical US food.
DataSet
- Queryable, remotable, in-memory relation collection
DBMS-Specific ADO.net data provider
- Direct access to native storage syntax, types
EntityClient
- Canonical Ad Hoc queries with Flexible Mapping
Linq to Sql
- Strongly typed Microsoft SQL Server schema
- LinqDatasouce for use in ASP.NET
Object Services
- Strongly typed entity model with flexible mapping
- Ling to Entities strongly typed queries
- EntitySql complex queries, ad hoc queries, provider specific features
Entity DataSource
- Simple asp.net integration
ASP.NET Data Services
- Standard, robust, rest based service
- Easy to use highly extensible
- .NET client for simple programming
*V2 of the Entity Framework will be released in the next cycle of Visual Studio.NET.
10 years ago we said stored procedures where the way to go because:
- Performance because dynamic sql was slow, that's not the case anymore.
- Security. Stored procedures and table valued functions are still the way to go.
- Level of indirection. Which is now offered through the EDM models.
- Control the queries the user was able to send to the database.
The world has changed.
Stuff that came up during the questions:
- When we talked about more flexible features in LINQ to SQL (flexible mapping and more providers). Microsoft want to have a clear story. LINQ to SQL will be likely continue to focus on offering a typed view on a store. The Entity Framework will continue to focus on a flexible mapping solution while staying provider independent.
- POCO is a major target for the next version of the EF.
- The team is working with the Visual Studio.NET for databases team to understand the lifecycle of the database and the model over the database and the answer for source control over the metadata.
- Use no-tracking option for read-only entities.