Microsoft Data Access Technology
Microsoft Data Access Technology
The
choice of an appropriate data access technology will depend on the type of data
you are dealing with, and how you want to manipulate the data within the
application. Certain technologies are better suited for specific scenarios. Use
the following common scenarios and solutions to map your application scenarios
to common data access technology solutions:
ADO.NET Core
Consider
using ADO.NET Core if you:
- Need to
use low level API for full control over data access your application.
- Want to
leverage the existing investment made into ADO.NET providers.
- Are
using traditional data access logic against the database.
- Do not
need the additional functionality offered by the other data access
technologies.
- Are
building an application that needs to support disconnected data access
experience.
ADO.NET Data Services Framework
Consider
using ADO.NET Data Services Framework if you:
- Are
developing a Silverlight application and want to access data through a
data centric service interface.
- Are
developing a rich client application and want to access data through a
data centric service interface.
- Are
developing N-tier application and want to access data through data centric
service interface.
ADO.NET Entity Framework
Consider
using ADO.NET Entity Framework (EF) if you:
- Need to
share a conceptual model across applications and services.
- Need to
map a single class to multiple tables via Inheritance.
- Need to
query relational stores other than the Microsoft SQL Server family of
products.
- Have an
object model that you must map to a relational model using a flexible
schema.
- Need
the flexibility of separating the mapping schema from the object model.
ADO.NET Sync Services
Consider
using ADO.NET Sync Services if you:
- Need to
build an application that supports occasionally connected scenarios.
- Need
collaboration between databases.
LINQ to Data Services
Consider
using LINQ to Data Services if you:
- Are
using data returned from ADO.NET Data Services in a client.
- Want to
execute queries against client-side data using LINQ syntax.
- Want to
execute queries against REST data using LINQ syntax.
LINQ to DataSets
Consider
using LINQ to DataSets if you:
- Want to
execute queries against a Dataset, including queries that join tables.
- Want to
use a common query language instead of writing iterative code.
LINQ to Entities
Consider
using LINQ to Entities if you:
- Are
using the ADO.NET Entity Framework
- Need to
execute queries over strongly-typed entities.
- Want to
execute queries against relational data using LINQ syntax.
LINQ to Objects
Consider
using LINQ to Objects if you:
- Need to
execute queries against a collection.
- Want to
execute queries against file directories.
- Want to
execute queries against in-memory objects using LINQ syntax.
LINQ to XML
Consider
using LINQ to XML if you:
- Are
using XML data in your application.
- Want to
execute queries against XML data using LINQ syntax.
0 comments:
Post a Comment