# General

![Table Output step](/files/XmoqFVPXPNDVpkQ1jX9h)

The table below describes the general options for the Table Output step:

| Option                      | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
| --------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Step name**               | Specifies the unique name of the Table Output step on the canvas. You can customize the name or leave it as the default.                                                                                                                                                                                                                                                                                                                                                        |
| **Connection**              | <p>Use the list to select the name of an existing database connection where you want your data to be written. Select the connection according to the relational database type you are modifying.</p><p>If you do not have an existing connection, click <strong>New</strong> or <strong>Wizard</strong>. If you need to modify an existing connection, click <strong>Edit</strong>.</p>                                                                                         |
| **Target Schema**           | Specify the name of your database schema.                                                                                                                                                                                                                                                                                                                                                                                                                                       |
| **Target table**            | Specify the name of the table where you want to write your data.                                                                                                                                                                                                                                                                                                                                                                                                                |
| **Commit size**             | Specify the size of the commit batch. The size is the number of `INSERT` statements to be performed before sending a `COMMIT` command to the database. Specifying a commit size may change the performance.Transactions are not supported on all database platforms.                                                                                                                                                                                                            |
| **Truncate table**          | Select to truncate the table before the first row is inserted into the table. If you will run the transformation on clusters or with multiple copies of this step, you must truncate the table before you start the transformation.                                                                                                                                                                                                                                             |
| **Ignore insert errors**    | Select to ignore all insert errors such as violated primary keys. A maximum of 20 warnings will be logged. This option is not available for batch inserts.                                                                                                                                                                                                                                                                                                                      |
| **Specify database fields** | Select to specify the fields in the **Database fields** tab. Otherwise all fields are inserted by default. This option must be selected to use the **Get fields** and the **Enter field mapping** tools in the **Database fields** tab.                                                                                                                                                                                                                                         |
| **SQL** (button)            | Click to open the [Simple SQL Editor](/pdia-data-integration/10.2-data-integration/data-integration-perspective-in-the-pdi-client/advanced-topics-pdi-perspective/use-the-sql-editor.md). The editor automatically generates the SQL needed to create the output table. You can modify the SQL statements if necessary, or click **Execute** to run the SQL and generate the table. The SQL Editor creates a target table with the name specified in the**Target table** field. |

!\[SQL editor]\(PDI\_TableOutput\_SQLEditor.png)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.pentaho.com/pdia-data-integration/10.2-data-integration/pdi-transformation-steps-reference-overview/table-output/general-table-output-step.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.