# tCreateTable Standard properties

These properties are used to configure tCreateTable running in the Standard Job framework.

The Standard tCreateTable component belongs to the Databases family.

The component in this framework is available in all Talend products.

## Basic settings

| Database Type | Select the type of the database. The connection properties may differ slightly<br>according to the database type selected. |
| --- | --- |
| Property Type | Select the way the connection details<br>will be set.<br><br><ul> <li> <p> <span>Built-In</span>: The connection details will be set                                locally for this component. You need to specify the values for all                                related connection properties manually.</p> </li> <li> <p> <span>Repository</span>: The connection details stored                                centrally in <span><span>Repository</span> &gt; <span>Metadata</span></span> will be reused by this component. You need to click                                the <span>[...]</span> button next to it and in the pop-up                                    <span>Repository Content</span> dialog box, select the                                connection details to be reused, and all related connection                                properties will be automatically filled in.</p> </li> </ul> |
| Use an existing connection | Select this check box and in the Component List click the relevant connection component to<br>reuse the connection details you already defined.<br><br>When a Job contains the parent Job and the child Job, if you need to<br>share an existing connection between the two levels, for example, to share the<br>connection created by the parent Job with the child Job, you have to:<br><br><ol> <li> <p>In the parent level, register the database connection to be shared                in the <span>Basic settings</span> view of the connection                component which creates that very database connection.</p> </li> <li> <p>In the child level, use a dedicated connection component to read                that registered database connection.</p> </li> </ol><br><br>For an example about how to share a database connection across Job<br>levels, see *Talend Studio<br>User Guide*. |
| JDBC Provider | Select the provider of the JDBC driver to be used, either Microsoft (the default, recommended) or Open<br>source JTDS.<br><br>When Microsoft is selected, you need to download the<br>Microsoft JDBC Driver for SQL Server on [Microsoft Download<br>Center](https://www.microsoft.com/en-us/download/details.aspx?id=11774), unpack the downloaded zip file, choose a jar in the<br>unzipped folder based on your JRE version, rename the jar to *mssql-jdbc.jar* and install it manually. For more<br>information about choosing the jar, see the System Requirements<br>information on [Microsoft Download<br>Center](https://www.microsoft.com/en-us/download/details.aspx?id=11774).<br><br>When using this component with Datasource in Talend Runtime, you need<br>to use the Open source JTDS driver.<br><br>This option is available when MSSQLServer is selected from the Database Type drop-down list. |
| DB Version | Select the version of the database. |
| Host | The IP address or hostname of the database. |
| Port | The listening port number of the database. |
| Database name | The name of the database. |
| Schema | The name of the database schema.<br><br>This property is available for DB2, Exasol, Greenplum, Informix, MS SQL Server, Oracle, PostgresPlus, 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.<br><br>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.<br><br>This property is available only for the HSQLDb database type. |
| DB Alias | The name of the database.<br><br>This property is available only for the HSQLDb database type. |
| Framework Type | Select the framework type for your database.<br><br>This property is available only for the JavaDb database type. |
| DB Root Path | Browse to your database root.<br><br>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.<br><br><ul> <li> <p> <span>Oracle SID</span>: select this connection type to uniquely                  identify a particular database on a system.</p> </li> <li> <p> <span>Oracle Service</span>: select this connection type to use the TNS                  alias that you give when you connect to the remote database.</p> </li> <li> <p> <span>Oracle OCI</span>: 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.</p> </li> <li> <p> <span>Oracle Custom</span>: select this connection type to access a                  clustered database.</p> </li> <li> <p> <span>WALLET</span>: select this connection type to store credentials                  in an Oracle wallet.</p> </li> </ul> |
| Account | In the Account field, enter, in double quotation marks, the account name<br>that has been assigned to you by Snowflake.<br><br>This property is available only for the Snowflake database type. |
| Username and Password | The database user authentication data.<br><br>To enter the password, click the [...] button next to the<br>password field, and then in the pop-up dialog box enter the password between double quotes<br>and click OK to save the settings. |
| Role | Enter, in double quotation marks, the default access<br>control role to use to initiate the Snowflake session.<br><br>This role must already exist and has been granted to the<br>user ID you are using to connect to Snowflake. If this field is left empty, the<br>PUBLIC role is automatically granted. For information about Snowflake access control<br>model, see [Understanding the Access Control<br>Model](https://docs.snowflake.net/manuals/user-guide/security-access-control.html).<br><br>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.<br><br><ul> <li> <p> <span>Create table</span>: the specified table doesn't exist and gets created.</p> </li> <li> <p> <span>Create table if not exists</span>: the specified table is created if it does not exist.</p> </li> <li> <p> <span>Drop table if exits and create</span>: the table is removed if it already exists and gets created again.</p> </li> </ul> |
| Temporary Table | Select this check box to create a temporary table during an operation, which is automatically dropped at the end of the operation. Since temporary tables exist in a special schema, you cannot specify a schema name when creating a temporary table, and the name of the temporary table must be distinct from the name of any other table, sequence, index, and view in the same schema.<br><br>Note that once you select to create a temporary table, you should empty the values when you edit schema.<br><br>This field is available only when Postgresql is selected from the Database Type drop-down list. |
| Unlogged Table | Select this check box to create an unlogged table during an operation. This way, data is loaded considerably faster than an ordinary table where the data is logged and then written. However, the data in an unlogged table is not crash-safe.<br><br>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.<br><br>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.<br><br>This property is available only for the MySQL database type. |
| Create | Select the type of the table to be created.<br><br><ul> <li> <p> <span>SET TABLE</span>: the table that does not allow duplicate rows.</p> </li> <li> <p> <span>MULTISET TABLE</span>: the table that allows duplicate rows.</p> </li> </ul><br><br>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<br>(columns) to be processed and passed on to the next component. When you create a Spark<br>Job, avoid the reserved word line when naming the<br>fields.<br><br><ul> <li> <p> <span>Built-In</span>: You create and store the schema locally for this component                only.</p> </li> <li> <p> <span>Repository</span>: You have already created the schema and stored it in the                Repository. You can reuse it in various projects and Job designs.</p> </li> </ul><br><br>When the schema to be reused has default values that are<br>integers or functions, ensure that these default values are not enclosed within<br>quotation marks. If they are, you must remove the quotation marks manually.<br><br><br>For more information, see the related<br>description of retrieving table schemas in Talend Studio User Guide.<br><br>Click Edit<br>schema to make changes to the schema. If the current schema is of the Repository type, three options are available:<br><br><ul> <li> <p> <span>View schema</span>: choose this                option to view the schema only.</p> </li> <li> <p> <span>Change to built-in property</span>:                choose this option to change the schema to <span>Built-in</span> for local changes.</p> </li> <li> <p> <span>Update repository connection</span>:                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 <span>No</span> upon completion and choose this schema metadata                again in the <span>Repository Content</span>                window.</p> </li> </ul> |

## Advanced settings

| 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.<br><br>This property is available for the AS/400 and MSSQL Server database types. |
| --- | --- |
| Create projection | Select this check box to create a projection.<br><br>This property is available only for the Vertica database type. |
| Enforce database delimited identifiers | Select this check box to enable delimited identifiers.<br><br>This property is available only for the Snowflake database type.<br><br>For<br>more information on delimited identifiers, see https://docs.intersystems.com/latest/csp/docbook/DocBook.UI.Page.cls?KEY=GSQL\_identifiers.<br><br>Information noteNote: If you use special characters in your column names,<br>select this checkbox to avoid possible errors or Job execution<br>failure. |
| tStatCatcher Statistics | Select this check box to gather the Job processing metadata at the Job level<br>as well as at each component level. |

## Global Variables

| QUERY | The query statement being processed. This is a Flow variable and it returns a<br>string. |
| --- | --- |
| ERROR\_MESSAGE | The error message generated by the component when an error occurs. This is an After<br>variable and it returns a string. |

## Usage

| Usage rule | This component can be used as a standalone component of a Job or<br>subJob. |
| --- | --- |