Create a Teradata connection
To access your data stored on a Teradata database, you will need to know the server and database name that you want to connect to, and you must have access credentials. Once you have created a connection to a Teradata database, you can select data from the available tables and then load that data into your app or document.
In Qlik Sense, you connect to a Teradata database through the Add data dialog or the Data load editor.
In QlikView you connect to a Teradata database through the Edit Script dialog.
Setting up the database properties
Database property | Description | Required |
---|---|---|
Host name | Host name to identify the location of the Teradata database. | Yes |
Port | Server port for the Teradata database. | Yes |
Database | The name of the Teradata database. | Yes |
Authenticating the driver
Qlik Sense: Teradata authentication properties
Authentication property | Description |
---|---|
Username | User name for the Teradata connection. |
Password | Password for the Teradata connection. |
Name |
Name of the Teradata connection. The default name will be used if you do not enter a name. |
QlikView: Teradata authentication properties
Authentication property | Description |
---|---|
Mechanism | You can authenticate with: LDAP, TD2, or user name and password. |
Username | User name for the Teradata connection. |
Password | Password for the Teradata connection. |
Account properties
Credentials
Credentials are used to prove that a user is allowed to access the data in a connection.
There are two types of credentials that can be used when making a connection in Qlik Sense SaaS. If you leave the User defined credentials check box deselected, then only one set of credentials will be used for the connection. These credentials belong to the connection and will be used by anyone who can access it. For example, if the connection is in a shared space, every user in the space will be able to use these credentials. This one-to-one mapping is the default setting.
If you select User defined credentials, then every user who wants to access this connection will need to input their own credentials before selecting tables or loading data. These credentials belong to a user, not a connection. User defined credentials can be saved and used in multiple connections of the same connector type.
In the Data load editor, you can click the underneath the connection to edit your credentials. In the hub or Data manager, you can edit credentials by right-clicking on the connection and selecting Edit Credentials.
See which authentication type applies on each connector's page.
Account property | Description |
---|---|
User defined credentials | Select this check box if you want users that access this connection to have to input their own credentials. Deselect this check box if credentials can be shared with anyone who has access to this connection. |
New credentials | Drop-down menu item that appears if User defined credentials is selected. |
Existing credentials | Drop-down menu item that appears if User defined credentials is selected. |
User | User name for the connection. |
Password | Password for the connection. |
Credentials name | Name given to a set of user defined credentials. |
Miscellaneous properties
Property | Description |
---|---|
Query timeout | Amount of time before a data load query times out. Can be set from 30 seconds to 65535 seconds. Default is 30 seconds. |
Load optimization settings
Property | Description | Required |
---|---|---|
Max String Length |
Maximum length of string fields. This can be set from 256 to 16384 characters. The default value is 4096. Setting this value close to the maximum length may improve load times, as it limits the need to allocate unnecessary resources. If a string is longer than the set value, it will be truncated, and the exceeding characters will not be loaded. |
No |
Advanced options
Property | Description | Required |
---|---|---|
Name |
Name of the custom property. You can add additional properties by clicking the . |
No |
Value |
Value of the property. |
No |