Teradata
Teradata is a relational database management system.
watsonx.data on IBM Software Hub
watsonx.data Developer edition
Teradata
Configure the following details for Teradata:
| Field | Description |
|---|---|
| Display name | Enter the database name to be displayed on the screen. |
| Database name | Enter the name of your database. |
| Hostname | Enter the Hostname. |
| Port | Enter the Port number. |
| Authentication type | Choose and enter the Authentication type details:
|
| Port is SSL enabled | Use the toggle switch to enable or disable SSL connection. If enabled, i. The Upload SSL certificate (.pem, .crt, .cert or .cer) link is enabled. ii. Click the Upload SSL certificate (.pem, .crt, .cert or .cer) link. iii. Browse the SSL certificate and upload. |
| Connection status | Click the Test connection link to test the database connection. If the database connection is successful, a success message appears. |
Console UI Associate catalog |
Console UI Select the checkbox to associate a catalog to the data source. This catalog is automatically associated with your data source and serves as your query interface with the data stored within. |
| Catalog name / Name |
|
| Create | Click Create to create the database. |
Limitations for SQL statements
ALTER TABLEdoes not drop the first column forDROP COLUMNstatement.DROP TABLEstatement is supported only when enabled in the catalog.- For the database-based catalogs,
CREATE SCHEMA,CREATE TABLE,DROP SCHEMA,DROP TABLE,DELETE,DROP VIEW,ALTER TABLE, andALTER SCHEMAstatements are not available in the Data manager UI.
Limitations for data types
BLOBandCLOBdata types support onlyCREATEandSELECTstatements.- The data that is shown for the
BLOBdata type from the UI is in Base64 format, while the result from presto-cli is in hexadecimal format. BINARYdata type supports onlySELECTstatement.VARBYTEis theBINARYalternative data type.- When the fields of data type
REALhave 6 digits or more in the decimal part with the digits being predominately zero, the values when queried are rounded off. It is observed that the rounding off occurs differently based on the precision of the values. For example, a decimal number 1.654 when rounded to 3-digits after the decimal point are the same. Another example is 10.890009 and 10.89000. It is noticed that 10.89000 is rounded to 10.89, whereas 10.89009 is not rounded off. This is an inherent issue because of the representational limitations of binary floating point formats. This might have a significant impact when querying involves sorting.