Licensing options for this format begin with FME Professional Edition.
The Teradata Non-Spatial reader and writer modules provide FME with access to attribute data held in Teradata database tables. FME provides read and write access via Teradata’s JDBC driver, which must be installed separately.
Downloading the JDBC Driver
Note: For best results, use the JDBC driver that matches the version of the software being communicated with.
You can download the driver from: http://downloads.teradata.com/download/connectivity/jdbc-driver. Teradata's download typically contains two files:
- terajdbc4.jar
- tdgssconfig.jar
Installing the JDBC Driver
To view instructions for installing the JDBC driver, please see Getting Started with JDBC.
Usage Notes
The performance of this format is dependent on the amount of memory allocated to the Java Virtual Machine (JVM). The following environment variables allow you to specify memory available to Java Plugins:
- FME_JVM_MIN_HEAP_SIZE: Initial heap size for initializing the JVM.
-
FME32_JVM_MIN_HEAP_SIZE: Same as FME_JVM_MIN_HEAP_SIZE, but applies to 32-bit FME Desktop on Windows, and takes precedence over FME_JVM_MIN_HEAP_SIZE.
- FME_JVM_MAX_HEAP_SIZE: Maximum heap size for initializing the JVM.
-
FME32_JVM_MAX_HEAP_SIZE: Same as FME_JVM_MAX_HEAP_SIZE, but applies to 32-bit FME Desktop on Windows, and takes precedence over FME_JVM_MAX_HEAP_SIZE.
These variables must be set for FME to honor them, and must be multiples of 1024K (for example, 4M and 64M, or 4096K and 32768K).
Note: To pass additional parameters used by FME to the Java Virtual Machine, use the JAVA_TOOL_OPTIONS environment variable.