Overview

This article is relevant to entity models that utilize the deprecated Visual Studio integration of Telerik Data Access. The current documentation of the Data Access framework is available here.

Sometimes, during Model First Scenario, the generated database artifact names are not always what you would expect. For example, you may have a class named "ShipAddress" with a field named "spAdr" and the generated database column will be "sp_adr". Telerik Data Access allows you to specify various naming rules and settings that will be applied on the generated relational items (tables and columns) during Model First Scenario. For example, it is possible to instruct Telerik Data Access to use the property name as it is for the column name. The same is valid for the default table name, i.e. it could be based on the class name. The main benefit is that you have control over the generated column names and you don't have to manually change the column name(s) for each field/property. You will always get similar column names based on what you see in the conceptual (domain) model. At the same time, it is possible to set naming rules for the generated domain model classes and properties in Database First Scenario.

In this section:

• Model Names - shows you how to specify various naming rules and settings that will be applied on the generated relational items (tables and columns) during Model First Scenario.
• Database Names - shows you how to specify various naming rules and settings that will be applied on the generated domain model items (classes, properties and fields) during .Database First Scenario