Teradata Non-spatial (JDBC) Reader Parameters
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. |
Connection Parameters
This specifies the hostname or IP address of the machine hosting the DBMS.
When connecting remotely, this parameter specifies the Teradata Server port on which to connect to the DBMS service. The default port is 1025.
Specifies the name of the Teradata Database. The database name must exist in the DBMS.
Enter the username and password to access the database, user account, or wherever authentication is required.
This parameter specifies how long a SQL query should be allowed to run before being canceled.
A value of 0 disables the timeout.
Constraints
After you have completely specified the database connection, click the Browse button to select tables to import. A connection window appears while FME reads 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 Reader Parameters box.
This optional specification is used to specify a where clause to use for the query. If this parameter is left blank, all rows in the table will be read and returned as individual features. If a WHERE clause is specified, only those rows that are selected by the clause will be read. (Note that the WHERE clause does not include the word WHERE.)
Example:
The example below selects only the rows for which the name column value is equal to safe:
name=’safe’
Schema Attributes
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 where you have multiple feature types, it is convenient to expose additional attributes using this one parameter. For example, if you have ten feature types and want to expose the same attribute in each one, it is easier to define it once than it is to set each feature type individually in the workspace.