AlloyDB Insert
In this article
Overview
You can use this Snap to execute a SQL INSERT statement using the document's keys as the columns to insert to and the document's values as the values to insert into the columns.
Snap Type
The AlloyDB Insert Snap is a Write-type Snap.
Prerequisites
A valid account with the required permissions.
Support for Ultra Pipelines Â
Works in Ultra Pipelines if batching is disabled.
Limitations and Known Issues
None.
Behavior Change
Â
Snap Views
Type | Format | Number of Views | Examples of Upstream and Downstream Snaps | Description |
---|---|---|---|---|
Input | Document Binary  |
|
| A table name and record details. By default the input view accepts the rows to insert into the table. A second input view can be added that accepts the table metadata document from a database Select Snap.  The table metadata is used to create the target table in the database. |
Output | Document Binary |
|
| Inserts a record. |
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 while running the Pipeline by choosing one of the following options from the When errors occur list under the Views tab:
Learn more about Error handling in Pipelines. |
Snap Settings
Asterisk ( * ): Indicates a mandatory field.
Suggestion icon (): Indicates a list that is dynamically populated based on the configuration.
Expression icon ( ): Indicates the value is an expression (if enabled) or a static value (if disabled). Learn more about Using Expressions in SnapLogic.
Add icon ( ): Indicates that you can add fields in the fieldset.
Remove icon ( ): Indicates that you can remove fields from the fieldset.
Upload icon ( ): Indicates that you can upload files.
Field Name | Field Type | Description |
---|---|---|
Label* Â Default Value: AlloyDB Insert | String | Specify a unique name for the Snap. Â |
Schema  Default Value: N/A | String/Expression | Specify the database schema name. Selecting a schema filters the Table name list to show only those tables within the selected schema. You can pass values using the Pipeline parameters but not through the upstream Snap. |
Table name*
| String/Expression | Specify the table that the rows will be inserted into. You must check the data type of each column in the table into which you want to insert the input data, and structure your data accordingly; else the endpoint generates an error. For example, if the column |
Create table if not present
| Checkbox | Select this checkbox to automatically create the target table if it does not exist.
|
Preserve case sensitivity
| Checkbox | Select this checkbox to preserve the case sensitivity of the column names while performing the insert operation. If you do not select this option, then Snap converts the column names in the input document to match the column names in the target database table before inserting the values. The Snap checks for the following three conditions:
On the contrary, if you select this checkbox, the Snap does not convert the case of the column names and inserts the names as-is in the target database. Therefore, ensure that the column labels in the input document match the column labels in the target database table. Else, the Snap does not insert the values and displays an error. For example, if the column names (ID, Name) in the input document do not match the column names (Id, name) in the database, then the Snap does not insert the values and displays an error. |
Number of retries
| Integer/Expression | Specify the maximum number of attempts to be made to receive a response. The request is terminated if the attempts do not result in a response. Â |
Retry interval (seconds)
| Integer/Expression | Specify the time interval between two successive retry requests. A retry happens only when the previous attempt results in an exception.  |
Snap Execution Default Value:Â Execute only | Dropdown list | Select one of the following three modes in which the Snap executes:
|
Â
Â
Snap Pack History
Related Links
Have feedback? Email documentation@snaplogic.com | Ask a question in the SnapLogic Community
© 2017-2024 SnapLogic, Inc.