Database Properties - 6.3

Talend Data Mapper User Guide

Talend Big Data Platform
Talend Data Fabric
Talend Data Management Platform
Talend Data Services Platform
Talend MDM Platform
Talend Real-Time Big Data Platform
Design and Development
Talend Studio

This property sheet describes the database connection information and allows you to test the connection to the database. This is used both when you are importing the database and when you show the properties of the database in the Repository navigator.

Basic Properties

Database information basic properties:

  • Database Name - The name of the database as you wish to refer to it. This will be the name of the object that is visible in the Repository navigator.

  • Database Type - Specify the type of database using the list.

  • Database Name or Instance Id - Specify the name of the database or the instance Id of the server. The label on this will change depending on the type of database selected.

  • Schema/User Name - For Oracle this is the Schema name, for all other databases this will appear as the user name.

  • Password - The password of the above user.

  • Host - The host name to connect to. Leave blank for the current host.

  • Port - The port number to connect to. Leave as zero for the default port number for the database.

  • Schema - Some databases (SQL Server and Sybase) have the notion of a schema within the database. You can specify a schema value here (like dbo) which will be used to filter the tables extracted from the database.

  • Test Connection - Use this to immediately connect to the database and report any errors.

  • Show More - Press this and you will see the advanced properties (below).

  • Structure Folder (not shown on screenshot) - The folder that contains the structure definitions for the database that were generated on the import. This appears only when viewing the properties of the database object. It does not appear in the import wizard.

Advanced Properties

The advanced properties are normally things you will not need to change; they are automatically set up depending on the choice of database type. However you can change these as required, even to the point of supporting a different database type.

  • URL pattern - A pattern used to construct the connection URL. In most cases you will not need to change this, however you can customize it as required. The ${databaseName} and ${hostPort} place holders will be substituted with actual values at runtime. This is automatically set to work with the default driver class using the driver manager mechanism (see below). If you wish to use a DataSource, set this to be the URL used to lookup the DataSource in JNDI.

  • Default primary key columns - In the (rare) case where there is no primary key specified by the database, you can set the primary key based on the leading columns in the table. For example, if you specify a 1, the primary key will be set to the first column in the table (when not specified otherwise by the database). If you specify -1 (the default), then all of the columns in the table will be considered the primary key.

  • Driver selection - Specify Driver Manager to use a JDBC driver class that is on the classpath or built in. Specify Data Source if you wish to use a JNDI lookup using the specified URL pattern to get the DataSource.

  • Driver class - The class name of the JDBC driver to use. Each database type has a default driver class, and the Jar file that contains the driver is automatically included in the product, both at design and runtime. If you wish to use your own driver, modify the project's classpath (see Edit Classpath) below so that you can test it in the designer. At runtime, make sure the driver class is available on the classpath (the project's classpath is used only at design time).

  • XA DataSource driver class - The class name of the XA data source that is provided when distributed transaction support is required. Like the driver class, this is set by default to a class automatically included.

  • Hibernate dialect class - The class name of the Hibernate dialect class that is used to handle SQL translation for the database.

  • Hibernate metadata dialect class - The class name of the Hibernate metadata dialect class to handle issues when reading database metadata.

  • Edit Classpath - Use this to change the classpath that is associated with the project containing the database. You can also change the project's classpath in the project properties (from the Repository navigator). You would change the classpath if you want to test with a database driver for example that is not built in.