tCreateTable Standard properties

Database Type

Select the type of the database. The connection properties may differ slightly according to the database type selected.

Property Type

Select the way the connection details will be set.

• Built-In: The connection details will be set locally for this component. You need to specify the values for all related connection properties manually.

• Repository: The connection details stored centrally in Repository > Metadata will be reused by this component.

  You need to click the [...] button next to it and in the pop-up Repository Content dialog box, select the connection details to be reused, and all related connection properties will be automatically filled in.

Use an existing connection

Select this check box and in the Component List drop-down list, select the desired connection component to reuse the connection details you already defined.

When a Job contains the parent Job and the child Job, if you need to share an existing connection between the two levels, for example, to share the connection created by the parent Job with the child Job, you have to:

1. In the parent level, register the database connection to be shared in the Basic settings view of the connection component which creates that very database connection.

2. In the child level, use a dedicated connection component to read that registered database connection.

For an example about how to share a database connection across Job levels, see Sharing a database connection.

JDBC Provider

Select the provider of the JDBC driver to be used, either Microsoft (the default, recommended) or Open source JTDS.

When Microsoft is selected, you need to download the Microsoft JDBC Driver for SQL Server on Microsoft Download Center, unpack the downloaded zip file, choose a jar in the unzipped folder based on your JRE version, rename the jar to mssql-jdbc.jar and install it manually. For more information about choosing the jar, see the System Requirements information on Microsoft Download Center.

When using this component with Datasource in Talend Runtime, you need to use the Open source JTDS driver.

This option is available when MSSQLServer is selected from the Database Type drop-down list.

DB Version

Select the version of the database.

Host

Enter the IP address or the hostname of the database.

If you select MSSQLServer from the Database Type drop-down list, enter the IP address or the hostname of the database server or the Azure Synapse Analytics to be used in this field. If the SQL Server Browser service is running on the machine where the MSSQL server resides, you can connect to a named instance through a TCP dynamic port by providing the host name and the instance name in this field in the format of {host_name}\{instance_name}. In this case, you can leave the Port field empty. See SQL Server Browser service for related information.

Port

Enter the listening port number of the database.

If you select MSSQLServer from the Database Type drop-down list, enter the listening port number of the database server or the Azure Synapse Analytics to be used in this field. If the SQL Server Browser service is running on the machine where the server resides, you can connect to a named instance through a TCP dynamic port by providing the host name and the instance name in the Host field and leave this field empty. See SQL Server Browser service for related information.

Database name

The name of the database.

Schema

The name of the database schema.

This property is available for DB2, Exasol, Greenplum, Informix, MS SQL Server, Oracle, PostgreSQL, Redshift, Sybase, and Vertica database types.

Access File

The path to the Access database file.

Firebird File

The path to the Firebird database file.

Interbase File

The path to the Interbase database file.

SQLite File

The path to the SQLite database file.

Running Mode

Select the Server Mode that corresponds to your database setup.

This property is available only for the HSQLDb database type.

Use TLS/SSL Sockets

Select this check box to enable the security mode if required.

This property is available only for the HSQLDb database type.

DB Alias

The name of the database.

This property is available only for the HSQLDb database type.

Framework Type

Select the framework type for your database.

This property is available only for the JavaDb database type.

DB Root Path

Browse to your database root.

This property is available only for the JavaDb database type.

ODBC Name

The name of the ODBC database.

Connection Type

Select the Oracle database connection type.

• Oracle SID: select this connection type to uniquely identify a particular database on a system.

• Oracle Service: select this connection type to use the TNS alias that you give when you connect to the remote database.

• Oracle OCI: select this connection type to use Oracle Call Interface with a set of C-language software APIs that provide an interface to the Oracle database.

• Oracle Custom: select this connection type to access a clustered database.

• WALLET: select this connection type to store credentials in an Oracle wallet.

Account

In the Account field, enter, in double quotation marks, the account name that has been assigned to you by Snowflake.

This property is available only for the Snowflake database type.

UserName and Password

Enter the database user authentication data.

To enter the password, click the [...] button next to the Password field, enter the password in double quotes in the pop-up dialog box, and then click OK.

If you select MSSQLServer from the Database Type drop-down list, you can use Type 2 integrated authentication on Windows by adding integratedSecurity=true in the Additional JDBC Parameters field and leave these two fields empty. See section Connecting with integrated authentication On Windows at Building the connection URL for related information.

Role

Enter, in double quotation marks, the default access control role to use to initiate the Snowflake session.

This role must already exist and has been granted to the user ID you are using to connect to Snowflake. If this field is left empty, the PUBLIC role is automatically granted. For information about Snowflake access control model, see Understanding the Access Control Model.

This property is available only for the Snowflake database type.

Table name

The name of the table to be created.

Table Action

Select the action to be carried out on the table.

• Create table: the specified table doesn't exist and gets created.

• Create table if not exists: the specified table is created if it does not exist.

• Drop table if exits and create: the table is removed if it already exists and gets created again.

Note that once you select to create a temporary table, you should empty the values when you edit schema.

This field is available only when Postgresql is selected from the Database Type drop-down list.

This field is available only when Postgresql is selected from the Database Type drop-down list and Temporary Table is not selected.

Case Sensitive

Select this check box to make the table/column name case sensitive.

This property is available only for the HSQLDb database type.

Temporary Table

Select this check box if you want to save the created table temporarily.

This property is available only for the MySQL database type.

Create

Select the type of the table to be created.

• SET TABLE: the table that does not allow duplicate rows.

• MULTISET TABLE: the table that allows duplicate rows.

This property is available only for the Teradata database type.

Schema and Edit Schema

A schema is a row description. It defines the number of fields (columns) to be processed and passed on to the next component. When you create a Spark Job, avoid the reserved word line when naming the fields.

• Built-In: You create and store the schema locally for this component only.

• Repository: You have already created the schema and stored it in the Repository. You can reuse it in various projects and Job designs.

When the schema to be reused has default values that are integers or functions, ensure that these default values are not enclosed within quotation marks. If they are, you must remove the quotation marks manually.

For more information, see Retrieving table schemas.

Click Edit schema to make changes to the schema. If the current schema is of the Repository type, three options are available:

• View schema: choose this option to view the schema only.

• Change to built-in property: choose this option to change the schema to Built-in for local changes.

• Update repository connection: choose this option to change the schema stored in the repository and decide whether to propagate the changes to all the Jobs upon completion.

  If you just want to propagate the changes to the current Job, you can select No upon completion and choose this schema metadata again in the Repository Content window.

Additional JDBC Parameters

Specify additional connection properties for the DB connection you are creating. This option is not available if you have selected the Use an existing connection check box in the Basic settings.

This property is available for the AS/400 and MSSQL Server database types.

Select this option to use Azure Active Directory authentication when establishing the connection. See Azure AD Authentication for related information.

This option is available when MSSQLServer is selected from the Database Type drop-down list and Microsoft is selected from the JDBC Provider drop-down list in the Basic settings view.

Create projection

Select this check box to create a projection.

This property is available only for the Vertica database type.

Enforce database delimited identifiers

This property is available only for the Snowflake database type.

For more information on delimited identifiers, see https://docs.intersystems.com/latest/csp/docbook/DocBook.UI.Page.cls?KEY=GSQL_identifiers.

tStatCatcher Statistics

Select this check box to gather the Job processing metadata at the Job level as well as at each component level.

QUERY

The query statement being processed. This is a Flow variable and it returns a string.

ERROR_MESSAGE

The error message generated by the component when an error occurs. This is an After variable and it returns a string.

Usage rule

This component can be used as a standalone component of a Job or subJob.