Input 

Document

• Min: 0

• Max: 1

• Mapper

• Copy

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.

Output

Document

• Min: 0

• Max: 1

• Mapper

• Router

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.

Error

Error handling is a generic way to handle errors without losing data or failing the Snap execution. You can handle the errors that the Snap might encounter when running the pipeline by choosing one of the following options from the When errors occur list under the Views tab:

• Stop Pipeline Execution: Stops the current pipeline execution if the Snap encounters an error.

• Discard Error Data and Continue: Ignores the error, discards that record, and continues with the remaining records.

• Route Error Data to Error View: Routes the error data to an error view without stopping the Snap execution.

Learn more about Error handling in Pipelines.

Specify the name for the Snap. You can modify this to be more specific, especially if you have more than one of the same Snap in your Pipeline.

Default Value: Teradata Execute
Example: Teradata Execute

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: 

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.

For example:

Open

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.

For example:

Open

Default Value: [None]

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

When Auto is selected, the Snap tries to determine the query type automatically.
If the execution result of the query is not as expected, you can change the query type to Read or Write.

Default Value: Auto
Example: Read

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: Not selected 

Specify the maximum number of retry attempts the Snap must make in case of network failure. 

When you set the Number of retries to more than 0, the Snap generates duplicate records when the connection is not established. To prevent duplicate records, we recommend that you follow one of the following:

• Set the Number of retries to 0 (default value) to prevent duplicate records from being passed downstream while executing a pipeline.

• Use a Primary key to prevent records from being inserted into the database.

• Use an Upsert instead of an Insert statement.

Default Value: 0

Example: 3

Specify the time interval between two successive retry requests. A retry happens only when the previous attempt resulted in an exception. 

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.

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

Failure: Failed to execute query

error code: 5992

A syntax error was found in the QUERY_BAND.

Verify that the query band is in the format specified in the Query band field above.

For example, if priority=1;workload=high in the Query band, add a semi-colon and update the value to priority=1;workload=high;.