Configuring Teradata Database Accounts
- Amritesh Singh
- Aparna Tayi (Unlicensed)
- Kalpana Malladi
In this article
Overview
This account is used by the Snaps in the Teradata Snap Pack. You can create an account from Designer or Manager. In Designer, when working on pipelines, every Snap that needs an account prompts you to create a new account or use an existing account. The accounts can be created in or used from:
- Your private project folder: This folder contains the pipelines that will use the account.
- Your Project Space’s shared folder: This folder is accessible to all the users that belong to the Project Space.
- The global shared folder: This folder is accessible to all the users within an organization in the SnapLogic instance.
Account Types
Teradata Database Account
Label | Required. User provided label for the account instance | |
---|---|---|
Account properties | Required. Enter in the information to create a connection to the database. | |
Hostname | Required. The server's address to connect to. Default value: [None] | |
Port Number | The database server's port to connect to. Port can be specified but it often results in the address being parsed as an IPv6 address. Care should be taken. Default value: [None] | |
Database name | Required. The database name to connect to. Default value: [None] | |
Username | Username that is allowed to connect to the database. Username will be used as the default username when retrieving connections. The username must be valid in order to set up the data source. Default value: [None] | |
Password | Password used to connect to the data source. Password wil be used as the default password when retrieving connections. The password must be valid in order to set up the data source. Default value: [None] | |
JDBC jars | List of JDBC JAR files to be loaded. A different driver binary for a driver must have a different name, the same name can not be reused for a different driver. If this property is left blank, a default JDBC driver will be loaded. Default value: [None] | |
JDBC Driver Class | Required. JBDC driver class name to use. Default value: com.teradata.jdbc.TeraDriver | |
Advanced properties | ||
Auto commit | When selected, each of the batches is committed immediately after it is executed. If the Snap fails, only the batch being executed at that moment is rolled back. When deselected, the Snap execution output is committed only after all the batches are executed. If the Snap fails, the entire transaction is rolled back, unless the Snap finds invalid input data before it sends the insert request to the server, and routes the error documents to the Error view. Default value: Selected | |
Batch size | Required. Number of statements to execute at a time. Using a large batch size could use up the JDBC placeholder limit of 2100. Default value: 50 | |
Fetch size | Required. Number of rows to fetch at a time when executing a query. Large values could cause the server to run out of memory. Default value: 100 | |
Max pool size | Required. Maximum number of connections a pool will maintain at a time. Default value: 50 | |
Max life time | Required. Maximum lifetime of a connection in the pool. Ensure that the value you enter is a few seconds shorter than any database or infrastructure-imposed connection time limit. A value of 0 indicates an infinite lifetime, subject to the Idle Timeout value. An in-use connection is never retired. Connections are removed only after they are closed. Default value: 30 | |
Idle Timeout | Required. The maximum amount of time a connection is allowed to sit idle in the pool. A value of 0 indicates that idle connections are never removed from the pool. Default value: 5 | |
Checkout timeout | Required. Number of milliseconds to wait for a connection to be available when the pool is exhausted. If you provide 0, the Snap waits infinitely until the connection is available. Therefore, we recommend you not to specify 0 for Checkout Timeout. Default value: 10000 | |
URL Properties | ||
URL property name | URL property name Default value: selectMethod | |
URL property value | URL property value Default value: cursor |
Account Encryption
Standard Encryption | If you are using Standard Encryption, the High sensitivity settings under Enhanced Encryption are followed. | |
---|---|---|
Enhanced Encryption | If you have the Enhanced Account Encryption feature, the following describes which fields are encrypted for each sensitivity level selected per each account. Account:
|
Teradata Database Dynamic Account
Selecting the Dynamic Account allows the users to pass the account details dynamically as a pipeline parameter. This would enable the users to use the same Snap within a pipeline to connect to different database instances.
Expression-enabled authentication fields, such as Username, Password, and Client Secret, support Secrets Management, a SnapLogic add-on that allows you to store endpoint credentials in a third-party secrets manager, such as AWS Secrets Manager, Azure Key Vault, or HashiCorp Vault. During validation and execution, pipelines obtain the credentials directly from the secrets manager. Learn more: Configure Accounts to use secrets.
Label | Required. User provided label for the account instance | |
---|---|---|
Account properties | Required. Enter in the information to create a connection to the database. | |
Hostname | Required. The server's address to connect to. Default value: [None] | |
Port Number | The database server's port to connect to. Port can be specified but it often results in the address being parsed as an IPv6 address. Care should be taken. Default value: 1025 | |
Database name | Required. The database name to connect to. Default value: [None] | |
Username | Required. Username that is allowed to connect to the database. Username will be used as the default username when retrieving connections. The username must be valid in order to set up the data source. Default value: [None] | |
Password | Password used to connect to the data source. Password wil be used as the default password when retrieving connections. The password must be valid in order to set up the data source. Default value: [None] | |
JDBC jars | List of JDBC JAR files to be loaded. A different driver binary for a driver must have a different name, the same name can not be reused for a different driver. If this property is left blank, a default JDBC driver will be loaded. Default value: [None] | |
JDBC Driver Class | Required. JBDC driver class name to use. Default value: com.teradata.jdbc.TeraDriver | |
Advanced properties | ||
Auto commit | When selected, each of the batches is committed immediately after it is executed. If the Snap fails, only the batch being executed at that moment is rolled back. When deselected, the Snap execution output is committed only after all the batches are executed. If the Snap fails, the entire transaction is rolled back, unless the Snap finds invalid input data before it sends the insert request to the server, and routes the error documents to the Error view. Default value: Selected | |
Batch size | Required. Number of statements to execute at a time. Using a large batch size could use up the JDBC placeholder limit of 2100. Default value: 50 | |
Fetch size . | Required. Number of rows to fetch at a time when executing a query. Large values could cause the server to run out of memory. Default value: 100 | |
Max pool size | Required. Maximum number of connections a pool will maintain at a time. Default value: 50 | |
Max life time | Required. Maximum lifetime of a connection in the pool. Ensure that the value you enter is a few seconds shorter than any database or infrastructure-imposed connection time limit. A value of 0 indicates an infinite lifetime, subject to the Idle Timeout value. An in-use connection is never retired. Connections are removed only after they are closed. Default value: 30 | |
Idle Timeout | Required. The maximum amount of time a connection is allowed to sit idle in the pool. A value of 0 indicates that idle connections are never removed from the pool. Default value: 5 | |
Checkout timeout | Required. Number of milliseconds to wait for a connection to be available when the pool is exhausted. If you provide 0, the Snap waits infinitely until the connection is available. Therefore, we recommend you not to specify 0 for Checkout Timeout. Default value: 10000 | |
URL Properties | ||
URL property name | URL property name Default value: selectMethod | |
URL property value | URL property value Default value: cursor |
Account Encryption
Standard Encryption | If you are using Standard Encryption, the High sensitivity settings under Enhanced Encryption are followed. | |
---|---|---|
Enhanced Encryption | If you have the Enhanced Account Encryption feature, the following describes which fields are encrypted for each sensitivity level selected per each account. Account:
|
Example
For the pipeline, define the pipeline parameters:
- Host
- Username
- Password
- Database
Use the values to supply values them in the Dynamic Account.
Back in the Teradata Export to HDFS pipeline, create a Teradata Database Dynamic Account
- Set the expression toggle on for the Hostname, Database name, Username and Password
- Supply the pipeline parameter values manually into the toggled properties
- Click Apply and fill the Snap Settings for the desired function.
You cannot Validate an account connection when creating a Teradata Database Dynamic Account because the account properties of a dynamic account are provided dynamically as pipeline parameters.
Snap Pack History
Release | Snap Pack Version | Date | Type | Updates |
---|---|---|---|---|
August 2024 | main27765 | | Stable | Upgraded the |
May 2024 | 437patches26471 | Latest | The jOOQ library for Teradata Snap Pack is upgraded from v3.9.1 to v3.17.3. This upgrade will be part of the GA release on August 14, 2024 (Stable release). Pipelines using the Teradata Snaps are not impacted after the jOOQ upgrade. | |
May 2024 | main26341 | | Stable | Updated and certified against the current SnapLogic Platform release. |
February 2024 | main25112 |
| Stable | Updated and certified against the current SnapLogic Platform release. |
November 2023 | main23721 | Stable | Updated and certified against the current SnapLogic Platform release. | |
August 2023 | main22460 | | Stable | The Teradata Execute Snap now includes a new Query type field. When Auto is selected, the Snap tries to determine the query type automatically. |
May 2023 | main21015 | Stable | Upgraded with the latest SnapLogic Platform release. | |
February 2023 | main19844 | Stable | Upgraded with the latest SnapLogic Platform release. | |
November 2022 | main18944 | Stable | The TPT Insert Snap now creates the target table only from the table metadata of the second input view when the following conditions are met:
| |
August 2022 | main17386 | Stable | Upgraded with the latest SnapLogic Platform release. | |
4.29 Patch | 429patches16235 | Latest | Fixed an issue with Teradata Execute Snap where the Snap did not display valid error message when the delete condition is invalid. | |
4.29 | main15993 | Stable | Enhanced the Teradata FastExport Snap with Character Set dropdown list to support encoding of data when you export data from the Teradata Database. | |
4.28 | main14627 | Stable | Upgraded with the latest SnapLogic Platform release. | |
4.27 | main12833 | Stable | Enhanced the Teradata Execute Snap to invoke stored procedures. | |
4.26 | main11181 | Stable | Upgraded with the latest SnapLogic Platform release. | |
4.25 Patch | 425patches11008 | Latest | Improved the error messages for all the Snaps in the Teradata Snap Pack where the Snaps fail with a null pointer exception error when the account reference provided is invalid. | |
4.25 | main9554 | Stable | Upgraded with the latest SnapLogic Platform release. | |
4.24 Patch | 424patches8799 | Latest |
| |
4.24 | main8556 | Stable | Enhanced the Teradata Select Snap to return only the selected output fields or columns in the output schema (second output view) using the Fetch Output Fields In Schema check box. If the Output Fields field is empty all the columns are visible. | |
4.23 | main7430 | Stable | Fixes the multi-line value issue and issue in the TPT Load Snap where the Snap writes null for both an empty string and null values in the input data. The fix for this issue was to add the following three lines in the script and wrap all the values in double quotes unless they are null while writing the input data into a temp CSV file. This fix may cause existing pipelines to fail if empty string values are expected to be loaded as null. | |
4.22 | main6403 | Stable | Upgraded with the latest SnapLogic Platform release. | |
4.21 Patch | 421patches6272 | Latest | Fixed the issue where Snowflake SCD2 Snap generates two output documents despite no changes to Cause-historization fields with DATE, TIME and TIMESTAMP Snowflake data types, and with Ignore unchanged rows field selected. | |
4.21 Patch | 421patches6144 | Latest | Fixed the following issues with DB Snaps:
| |
4.21 Patch | MULTIPLE8841 | Latest | Fixed the connection issue in Database Snaps by detecting and closing open connections after the Snap execution ends. | |
4.21 | snapsmrc542 |
| Stable | Upgraded with the latest SnapLogic Platform release. |
4.20 | snapsmrc535 | Stable | Upgraded with the latest SnapLogic Platform release. | |
4.19 Patch | db/teradata8414 | Latest | Fixed an issue with the TPT Update Snap wherein the Snap is unable to perform operations when:
| |
4.19 | snaprsmrc528 | Stable | Upgraded with the latest SnapLogic Platform release. | |
4.18 | snapsmrc523 | Stable | Upgraded with the latest SnapLogic Platform release. | |
4.17 | ALL7402 | Latest | Pushed automatic rebuild of the latest version of each Snap Pack to SnapLogic UAT and Elastic servers. | |
4.17 | snapsmrc515 | Latest |
| |
4.16 | snapsmrc508 | Stable | Upgraded with the latest SnapLogic Platform release. | |
4.15 Patch | db/teradata6338 | Latest | Replaced Max idle time and Idle connection test period properties with Max life time and Idle Timeout properties respectively, in the Account configuration. The new properties fix the connection release issues that were occurring due to default/restricted DB Account settings. | |
4.15 | snapsmrc500 | Stable | Upgraded with the latest SnapLogic Platform release. | |
4.14 | snapsmrc490 | Stable | Upgraded with the latest SnapLogic Platform release. | |
4.13 | snapsmrc486 | Stable | Upgraded with the latest SnapLogic Platform release. | |
4.12 | snapsmrc480 | Stable | Upgraded with the latest SnapLogic Platform release. | |
4.11 | snapsmrc465 | Stable | Upgraded with the latest SnapLogic Platform release. | |
4.10 | snapsmrc414 | Stable | Added Auto commit property to the Select and Execute Snaps at the Snap level to support overriding of the Auto commit property at the Account level. | |
4.9.0 Patch | teradata3077 | Latest | Fixed an issue regarding connection not closed after login failure; Expose autocommit for "Select into" statement in PostgreSQL Execute Snap and Redshift Execute Snap | |
4.9 | snapsmrc405 | Stable |
| |
4.8 | snapsmrc398 | Stable |
| |
4.7 | snapsmrc382 | Stable |
| |
4.6 | snapsmrc362 | Stable | Snap Pack introduced in 4.6.0. This includes only Teradata extract functionality to move data out of Teradata database using the FastExport Utility. It does not include Snaps for load, select, insert, delete, execute or others at this time. It also does not utilize the Teradata Parallel Transporter to extract data. |
Have feedback? Email documentation@snaplogic.com | Ask a question in the SnapLogic Community
© 2017-2024 SnapLogic, Inc.