Basic Settings for a Relational Data Source

Select BASIC or Kerberos authentication method, where offered.

See the TDV Administration Guide for more information about Kerberos authentication.

The domain where TDV is installed.

The authetication type used for connecting to the data source.

(BASIC, KERBEROS, NTLM, or NEGOTIATE)

See Supported Character Encoding Types, page 185.

ASCII or EBCDIC.

The number of partitions you want used when tables are created.

This number affects whether and how table partitioning is done when TDV creates new tables in SAP HANA, for example as cache targets.

Ultimately, the number of partitions affects performance when querying the resulting table, so you should optimize it for your SAP HANA instance and usage.

A URL to connect to the physical data source. TDV does not validate modifications. The data source adapter might not validate changes.

jdbc:drill:drillbit=<hostIP>;schema=<scemaname>

jdbc:snappydata://<hostIP>

For DB2 DBMS types, name of the underlying data source. For other DBMS types, enter NONE.

Name or alias of the underlying data source. TDV Server uses this name to find and connect to the data source.

The name of the published TDV database.

The name of the Netezza catalog. The Netezza catalog is equivalent to a database name and allows view of the databases in the catalog.

The Lead node port used for submitting ComputeDB jobs. The default port is 8090.

Name or alias of the underlying data source.

DataDirect SQL access keyword that specifies the means by which the adapter accesses the data. Most of the storage schemes listed below do not allow or are not optimized for SQL push. To use more than one DBMS type, create more data source connections in Studio.

Supported DBMS type values are:

The Data Source Name. You might need to create a new User or System DSN using the ODBC Data Source Administrator utility (available with Windows Administrative Tools).

Name or IP address of the machine hosting the data source.

Oracle data sources: you cannot enter an Oracle database link name in this field.

Instance number of the SAP HANA system.

User name and password required to access the data source. When the data source is used as a target for cache tables or data ship, the user must also have permission to create tables, execute DDL, and perform other required tasks. Refer to the individual data source descriptions for details.

The TNS name that is set up through Oracle Net Configuration Assistant.

Disabled (default)—This allows automated provisioning of a connection pool. Open connection threads can be used by authorized users after the validation query verifies connection status. If pass-through login is disabled, the Save Password check box is not available.

Enabled—A new connection to the data source uses the credentials supplied by the client when data is requested from that data source for the first time. Subsequent requests by the same user reuse the existing connection. When another user attempts to connect to a data source, a new connection is created.

See “Managing Security for TDV Resources” in the TDV Administration Guide for details.

To use Kerberos tokens, Oracle data sources must enable pass-through login. In addition, an enabled Kerberos security module must be running on TDV so that Kerberos-authenticated users with session tokens can use it when submitting queries.

If you choose Kerberos authentication for Sybase, do not enable pass-through login.

Data isolation plan. The default value, SDBC1010, specifies cursor stability. Other values specify repeatable reads, read stability, or uncommitted reads. See the Shadow RTE Client/adapters Installation and Administration Guide for more information.

Port number for the data source to connect with the host. The default port number can depend on data source type. For example:

Composite—9401 DataDirect Mainframe—1200
DB2—no default DB2 z/OS—446
Greenplum—5432 HBase—2181
Hive—10000 Informix—1526
Microsoft SQL Server—1433 MySQL—3306*
NeoView—18650 Netezza—5480
Oracle—1521 PostgreSQL—5432
SAP HANA —30015 Sybase—4100**
Sybase ASE—5000** Sybase IQ—2638**
Teradata—1025 Vertica—5433

* Default is 3306 or the base port setting plus eight, depending on the MySQL instance.

** The port number used for communicating with TDV is the TCP/IP port set in the <Sybase_name>.cfg configuration file.

By default, the login and password are saved to create a reusable TDV Server system connection pool, usable only by the resource owner, explicitly authorized groups and users, and TDV administrators. They can:

To disable saving of the password, enable Pass-through Login.

Name or IP address of the machine hosting the data source.

Name of the database service.

This field is available only if you choose Kerberos authentication.

This field is available only if you choose Kerberos authentication.

This field is available only if you choose Kerberos authentication.

This field is available only if you choose Kerberos authentication.

Use to enable Kerberos security through keytab files. Type the full path to the keytab file.

Specify when using Kerberos authentication.