ADO.NET Entity Framework - Programming Against a Model, Not Against the Database
Developers spend too much time writing view, stored procedures and setting relationships and worrying about their backend
The Entity Framework is designed to enable developers to create data access applications by programming against a conceptual application model instead of programming directly against a relational storage schema.
We can focus on the task of writing our applications, rather than accessing the data.
Applications can work in terms of a more application-centric conceptual model, including types with inheritance, complex members, and relationships.
- Applications are freed from hard-coded dependencies on a particular data engine or storage schema.
- Mappings between the conceptual model and the storage-specific schema can change without changing the application code.
- Developers can work with a consistent application object model that can be mapped to various storage schemas, possibly implemented in different database management systems.
- Multiple conceptual models can be mapped to a single storage schema.
- Language-integrated query support provides compile-time syntax validation for queries against a conceptual model.
- Adding functionality to a pre-built is relatively seamless.
Speaker focus
Ashwani Roy is SQL Server MVP and Senior Consultant with Information Management Group (IMGROUP), winners of the Microsoft Global Business Intelligence Partner of the Year award for the past four years. Ashwani has worked with SQL Server BI stack since 2003 and is Microsoft Certified IT Professional. His main field of expertise are SQL Server Analysis Services, MDX, SQL Server Database Engine, T-SQL, and SSIS and C #.
Other sessions from this conference