Thank you for your interest in Telerik Data Access.
Indeed, Telerik Data Access offers design-time tools
that support the Model - First scenario
, where you can create and edit tables, modify their members, and setup relationships between the tables. The so defined conceptual model is stored in a special XML file - the .rlinq file
, and through a part of our API
this model can be integrated in your own custom tool that will deploy the database. To get a little bit of hands on experience with the product, you can take a look at the Getting Started section
in our documentation.
Regarding the management of indexes, views and stored procedures, our tools have a few limitations there:
- The customization of indexes
in available only for the code-only mapping approach
(the model is defined through code, without visual tools);
- In both the model-first
and the round-trip
scenarios our tools do not create views. However, if the database already has views, you can create mapping for them
in the model through the tools.
- The same as the latter applies for stored procedures - if they exist in the database you can consume them through the model, but you cannot create your own stored procedures and migrate them to the database. The exception here is when you map the CUD operations for a given entity to stored procedures
When it comes to the support, Telerik Data Access is and will continue to be both a free tool and a part of the DevCraft packages
with releases three times a year, which includes new features and bug fixes.
As for the special tool dedicated to the deployment of databases, currently Telerik does not offer a One-To-One analogue of StrataFrame.
If you find this feasible, do let us know if you need further information or assistance during the process.
OpenAccess ORM is now Telerik Data Access
. For more information on the new names, please, check out the Telerik Product Map