| Database Connections |
|---|
|
Connections store authentication information. For general information about sharing database connections, please see Using Database Connections. Note that different subsets of Database Connection parameters are made available in different contexts.  Connection
Select an existing connection, or Add Database Connection to define a new connection. The new connection can be made visible only to the current user, or can be shared among multiple users. |
Database Connection
Database Path
Select the location of the database.
Password
This parameter is only required for Access databases with password protection.
Constraints
Table List
After you have specified the database connection, click the Browse button to select tables for import. A connection window appears while the system compiles a table from the database.
Once the table list appears, you can select one or more tables, and then click OK to dismiss the window. The table name(s) will appear in the Table List field in the parameter box.
WHERE Clause
An SQL WHERE clause can be applied to the selected tables, to constrain the the row selection in tables chosen in the table list (for example, NUMLANES=2).
Schema Attributes
Additional Attributes to Expose
Use this parameter to expose Format Attributes in Workbench when you create a workspace:
- In a dynamic scenario, it means these attributes can be passed to the output dataset at runtime.
- In a non-dynamic scenario, you can use this parameter to expose additional attributes on multiple feature types.
Advanced
Number of Records to Fetch At A Time
The number of rows that are retrieved at one time into local memory from the data source. For example, if set to 10, the reader reads 10 rows into local memory. As features are processed, the reader returns the data from the local memory buffer. When the reader passes the last row available in local memory, it retrieves the next 10 rows from the data source.
This parameter may cause significantly degraded reader performance if incorrectly set. The optimum value depends primarily on the characteristics of individual records and the transport between the database and the client machine. It is less affected by the quantity of rows to retrieve.
The default setting of 10 has been determined to be the optimal value for average datasets.