Data mapping describes how to map elements between two distinct data models, usually distinguished as the source and the target. To support SQL access to cloud data stores, the DataDirect Cloud connectivity service maps tables, columns, rows, relationships between tables, and stored procedures. In a DataDirect Cloud map, the source data model can be from a relational or a non-relational data store, and the target type is a relational model.
For some data stores, the DataDirect Cloud connectivity service creates a map when it connects for the first time and subsequently uses it for queries and updates. The map options, which are located on either the General tab or the Mapping tab for the Data Source, define the way the map to the data store is created. Map options provide the ability to force creation of a new map and to create named maps. For some data stores, map options also define whether or not to include extra columns such as audit and system columns, and how to process custom prefixes and suffixes. Once a map is created, the options used in creating that map cannot be changed without creating a new map.
The default values for advanced mapping fields are appropriate in many cases for any data store. However, if your organization uses custom objects, wants to access audit columns, or has tables or columns named with reserved words, you might want to change map option settings. Understanding how DataDirect Cloud creates and uses maps will help you choose the appropriate values. Watch a video.
Map options are specific to particular data stores. The following table lists all options that apply to each type of data store.
Note: Map creation is an expensive operation. In most cases, you will only want to re-create a map if you need to change mapping options.
Table 171. Map options for each data store type
Salesforce-based data sources, including FinancialForce, ServiceMax, and Veeva CRM