Tools - Overview
Telerik Data Access Model is a model for defining data as sets of objects and relationships to which common language runtime (CLR) persistent types and underlying relational artifacts can be mapped. The model enables developers to program against a conceptual schema instead of directly program against a database schema.
The first component of a Data Access model is the persistent classes. When you define a persistent class, all you have to do is create a POCO class with a number of properties that will correspond to the columns of a database table. Later on, after integrating the model project with the Telerik.DataAccess.Fluent NuGet package, during the compilation process a special tool called Enhancer will take care to introduce in the POCO classes features like persistence capability and lazy loading.
When your model is complete and it has persistent classes, a metadatasource class, and a context class, you can consume it with the Telerik.DataAccess.Core NuGet package and any .NET UI technology. The performance of the resulting application can be monitored and finetuned with the help of Telerik Data Access Profiler and Tuning Advisor.
Both Enhancer and Profiler and Tuning Advisor are the subject of this section.