Bookshelf v10.1.3.2: About the Physical Data Sources Tab

The Physical Data Sources tab provides access to the connection properties for the physical data sources. In this tab, you can view and edit existing physical data source connections and create new ones. Table 31 provides a description of the physical data source properties.

Table 31. Physical Data Sources Top Pane Properties
Property	Description
Name	Logical name for the physical data source.
Type	Physical data source type. Possible values are: Source Warehouse Informatica Repository DAC Repository Other
Connection Type	Type of database connection. Possible values are the following: Oracle (OCI8). Connect to Oracle using the tnsnames entry. Oracle (Thin). Connect to Oracle using thin driver. DB2. DB2 UDB database. DB2-390. DB2 390 database. MSSQL. Microsoft SQL Server. Teradata. Teradata database. Flat File
Connection String	If you are using... Oracle (OCI8), use the tnsnames entry. Oracle (Thin), use instance name. SQL server, use the database name. DB2-UDB/DB2-390, use the connect string as defined in the DB2 configuration. Teradata, use the database name.
Table Owner	Name of table owner.
Max Num Connections	Maximum number of database connections this connection pool can contain. For information about determining how to set this value, see Determining the Number of Transactional and Data Warehouse Database Connections
DBHost	Host machine where the database resides. This field is mandatory if you are using Oracle (Thin), MSSQL, or Teradata, but is not required if you are using Oracle (OCI8), DB2, or DB2-390.
Port	Port where the database receives requests. Required for Oracle (Thin) and MSSQL databases. Not required for Oracle (OCI8), DB2, or DB2-390, or Teradata databases.
Priority	User-defined priority of the data source.
Data Source Number	User-defined number of the data source.
Default Index Space	Applicable to Oracle databases only. The default index space for the physical data source. When indices are dropped and created, they are created in this index space.

Table 32 provides a description of the child tabs in the bottom pane of the Physical Data Sources tab.

Table 32. Physical Data Sources Child Tab

Refresh Dates	During an ETL process, this date is captured for all target tables and source tables of the type primary and auxiliary. The DAC uses this date in the change capture process, during parameter generation, when choosing between full and incremental loads, and when deciding whether to truncate a table. (Does not apply to micro ETL processes.) NOTE: Refresh dates for micro ETL processes are captured in the Refresh Dates child tab of the Execution Plans tab.

Actions Available

The following actions are available in the top pane toolbar and in the right-click menu when the Physical Data Sources tab is active.

Test Connection

This command allows you to test the connection to the database. The DAC client will attempt to delegate the test to the DAC server. If the DAC server is not running, you will be asked whether you want to test the connection on the local client machine. The results of a test on the local client machine may not be true for the DAC server environment.