Data Source Properties

To view or edit a data source's properties, double-click its Browser or list entry. The property sheet tabs and fields listed here are those available by default, before any customization of the interface by you or an administrator.

The General tab contains the following properties:

Property

Description

Name/Code/Comment

Identify the object. The name should clearly convey the object's purpose to non-technical users, while the code, which is used for generating code or scripts, may be abbreviated, and should not normally include spaces. You can optionally add a comment to provide more detailed information about the object. By default the code is generated from the name by applying the naming conventions specified in the model options. To decouple name-code synchronization, click to release the = button to the right of the Code field.

Model Type

Type of model(s) being used as data source. See Object Mappings

Access type

Controls which types of queries (for PDM data sources) are available in the Mappings property sheet or in the Mappings pane of the Mapping Editor, and also controls the existence of forward and reverse mappings. For more information about forward and reverse mappings, see Creating a data source.

Keywords

Provide a way of loosely grouping objects through tagging. To enter multiple keywords, separate them with commas.

The following tabs are also available:
  • Models - Lists the models associated with the data source. Use the Add Models tool to add models open in the current workspace.
  • Database Connection - [for data sources created in a PDM] Contains the parameters needed to connect to the database associated with the data source. Click the Select a Data Source tool to specify an ODBC data source or connection profile (see Connecting to a Data Source).
  • Cost - [for data sources created in a PDM that supports lifecycle modeling] Lets you specify the cost per GB of storage for the data source along with the compression rate, which is used to estimate the relative size of the data once it has been loaded to the data warehouse (where 100% indicates no compression).
  • Data Movement (Lifecycle) - [for data sources created in a PDM that supports lifecycle modeling] Lets you define parameters to connect to a remote database, whose data will be loaded into the warehouse.