FME can read and write attribute data held in Teradata database tables. FME provides read and write access via Teradata’s JDBC driver, which must be installed separately.
Teradata Non-Spatial Product and System Requirements
|
Format |
FME Platform |
Operating System |
||||
|---|---|---|---|---|---|---|
|
Reader/Writer |
FME Form |
FME Flow |
FME Flow Hosted |
Windows 64-bit |
Linux |
Mac |
|
Reader |
Yes |
Yes |
No |
Yes |
Yes |
Yes |
|
Writer |
Yes |
Yes |
No |
Yes |
Yes |
Yes |
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 the Teradata Downloads page. Teradata's download typically contains the following files:
- terajdbc4.jar
- tdgssconfig.jar (only for versions prior to Teradata 16)
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. If unset, the default value is 1024K.
This variable must be set in multiples of 1024 and greater than 1 MB. To indicate kilobytes, megabytes, or gigabytes, append k or K, m or M, or g or G, respectively. For example, any of these values is acceptable:
6291456
6144k
6m
FME_JVM_MAX_HEAP_SIZE
Maximum heap size for initializing the JVM. If unset, the default value is 16384K.
This variable must be set in multiples of 1024 and greater than 2 MB. To indicate kilobytes, megabytes, or gigabytes, append k or K, m or M, or g or G, respectively. For example, any of these values is acceptable:
83886080
81920k
80m