Retrieve, create, update or delete entities through a simple Domain Model-based API. Benefit from a LINQ implementation that works equally well generating SQL queries for MS SQL Server, Oracle, MySQL or any other supported backend.
Telerik Data Access supports adding types or fields to your mapping, even during runtime. Add new classes and start using them right away. Add new properties to the existing classes, map them to database columns and implement your application extensibility without any persistence headaches.
With few lines of code you can create a new database or compare existing one with your data model, then push required database schema changes to your server.
Use the Artificial Types API to define new classes, and then update your schema based on the changes.
Data Access supports both optimistic and pessimistic concurrency control. Both approaches can be mixed during runtime. It is possible to automatically obtain a pessimistic lock upon the first modifying access in an otherwise optimistic transaction. When using optimistic concurrency control (the default), conflicts can be detected by designated version fields, the old content of the modified fields or all fields. You can also turn conflict detection off.
Modifications to values of persistent fields are automatically tracked. You don't need to notify the Data Access runtime system that an instance is to be written. When modifications are detected, only the necessary columns are included in the resulting SQL statements. All referenced persistent objects will be handled as well, and only complete object graphs are stored –no instance is left behind.
Telerik Data Access uses lazy loading on the client upon access, where your application objects are filled with the data. Not all fields are filled immediately, so a collection or picture fields can be deferred in their population. This has the advantage of saving memory and network bandwidth while preserving easy access. When the field's content is needed, the data is fetched transparently from the database server. You decide which fields are to be fetched and when. Data Access provides sensible defaults.
The Data Access Profiler makes it simple to visualize and summarize the application's data operations in real time. It analyzes and detects programming and coding mistakes, performance drawbacks, and inefficient use of the database. It is also a data tuning advisor, which will show alerts when certain thresholds are reached, and will help you fine-tune the SQL and data performance of your Data Access-generated persistence layer.
You can extend the structure of a persistent class by adding new persistent fields during runtime by using Artificial Fields. These new fields can be described by using the Fluent API. They are accessible via the Generic Metadata Access which is based on the System.ComponentModel API, but adds Data Access specific functionality.
Get your fully functional free copy of Data Access.
Read comprehensive technical documentation complete with code snippets
Explore Knowledge Base
Explore tutorials and working examples on how to achieve common scenarios
Copyright © 2002-2016 Telerik. All rights reserved.
Powered by Telerik