This Snap has at most one document input view.

If the input view is defined, then the where clause can substitute incoming values for a given expression.

• Mapper
• Copy

This Snap has at most one document output view.

If an output view is available and an update/insert/merge/delete statement was executed, then the original document that was used to create the statement will be output with the status of the statement executed.

Valid JSON paths that are defined in the where clause for queries/statements will be substituted with values from an incoming document.

• Mapper
• Router

Required. Specify a unique name for the Snap. Modify this to be more appropriate, especially if more than one of the same Snaps is in the pipeline.

Default value: Teradata Execute

Required. Specify the SQL statement to execute on the server.

There are two possible scenarios that you encounter when working with SQL statements in SnapLogic. You must understand the following scenarios to successfully execute your SQL statements:

Scenario 1: Executing SQL statements without expressions

If the expression toggle of the SQL statement field is disabled:

• The SQL statement must not be within quotes.
• The $<variable_name> parts of the SQL statement are expressions. In the below example, $id and $book.

Additionally, the JSON path is allowed only in the WHERE clause. If the SQL statement starts with SELECT (case-insensitive), the Snap regards it as a select-type query and executes once per input document. If not, it regards it as write-type query and executes in batch mode.

Scenario 2: Executing SQL queries with expressions

If the expression toggle of the SQL statement field is selected:

• The SQL statement must be within quotes.
• The + $<variable_name> + parts of the SQL statement are expressions, and must not be within quotes. In the below example, $tablename.
• The $<variable_name> parts of the SQL statement are bind parameter, and must be within quotes. In the below example, $id and $book.

• We recommend that you add a single query in the SQL Statement field.
• When the SQL statement property is an expression, the Pipeline parameters are shown in the suggest, but not the input schema.

Single quote escaping examples:

• String has no single quotes: To pass Schaum Series, use 'Schaum Series'
• String contains single quotes: To pass O'Reilly's Publication, use 'O''Reilly''s Publication'

Default value: N/A

Select the type of query for your SQL statement (Read or Write).

The default option, Auto, attempts to infer the type based on your SQL statement. Read is used with SELECT statements, Write is used with INSERT, UPDATE, or DELETE.

Default value: Auto

Specify the name-value pairs to use in the session's generated query band statement. The query band is passed to the Teradata database as a list of name-value pairs separated by semi-colons.

Default value: N/A

Example: ProjectName=dstage1;user=test;

Select this checkbox to pass the input document to the output view under the key 'original'. This property applies only to the Execute Snaps with SELECT statement.

Default value: Selected

Select this checkbox to ignore empty result; no document will be written to the output view when a SELECT operation does not produce any result. If you deselect this checkbox and select the Pass through checkbox, the input document will be passed to the output view.

Default value: Deselected

The number of retry attempts the Snap makes in case of a connection failure.

Default value: 3

The interval in seconds between retry attempts.

Default value: 1

Select one of the options for this property to override the state of the Auto commit property on the account. The Auto commit at the Snap-level has three values: True, False, and Use account setting. The expected functionality for these modes are:

• True - The Snap will execute with auto-commit enabled regardless of the value set for Auto commit in the Account used by the Snap.
• False - The Snap will execute with auto-commit disabled regardless of the value set for Auto commit in the Account used by the Snap.
• Use account setting - The Snap will execute with Auto commit property value inherited by the Account used by the Snap.

Behavior of DML Queries in Database Execute Snap when auto-commit is false

DDL queries used in the Database Execute Snap will be committed by the Database itself, regardless of the Auto-commit setting. When Auto commit is set to false for the DML queries, the commit is called at the end of the Snap's execution. The Auto commit needs to be true in a scenario where the downstream Snap does depend on the data processed on an Upstream Database Execute Snap containing a DML query. When the Auto commit is set to the Use account setting on the Snap, the account level commit needs to be enabled.

Default value: Use account setting

Example: False

Select the option 'Timestamp with microsecond precision' to support the microsecond precision for TIMESTAMP data type. The SELECT query for TIMESTAMP columns produces string values with microsecond precision in the output documents.

Default value: None