You can use this Snap to execute a stored procedure in a SQL Server database and writes the values of OUT parameters to the output view.
Starting from SQL Server 2008, the result set from a Transact-SQL statement or stored procedure includes the count of the number of rows affected. This Snap fails to parse this extra information and may display an error (such as Failed to process result set). To fix the issue, add the following line to the stored procedure to turn off the output of the count: SET NOCOUNT ON
Snap Type
SQL Server - Stored Procedure is a Write-type Snap that executes an SQL Server stored procedure.
This Snap allows up to one input view. If an input view is defined, then values from an incoming document can be used as input parameters to the stored procedure.
Output
Document
Min: 2
Max: 2
Mapper Snap
This Snap has exactly two document output views, one regular output view, and one Result Set output view.
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.
Suggestion icon (): Indicates a list that is dynamically populated based on the configuration.
Expression icon (): Indicates whether 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 field set.
Remove icon (): Indicates that you can remove fields from the fieldset.
Field Name
Field Type
Description
Label*
Default Value: SQL Server - Stored Procedure Example: SQL Server - Stored Procedure
String
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.
Schema Name
Default Value: N/A Example: schema_demo
String/Expression
Specify the schema name where the procedure resides. The property is suggestible and will return all schemas of the DB.
The values can be passed using the pipeline parameters but not the upstream parameter.
Stored Procedure Name*
Default Value: N/A Example: addSeventeen
String/Expression
Specify the Stored Procedure to execute. The property is suggestible and will return all procedures of the DB. If a package is defined, then it will only return the procedures of that package. If a schema is defined and no package is defined, then it will return all procedures of that schema.
Parameter Values
Use this fieldset to set Parameter Values to be used in the stored procedure. The parameter values will be bound to input columns in the order they appear in the list.
Parameter Value
Default Value: N/A Example: Suppose there is a stored procedure named createGreeting. It has three parameters p1,p2, and p3. p1 and p2 are input parameters of type VARCHAR2. Then there have to be two string values provided. The first value goes to p1 and the second to p2.
String/Expression
Specify the input parameter values for the stored procedure. If you define parameter values, you must do so in the same order as they appear in the stored procedure definition.
Quotation marks should not be used when setting input parameters unless they are part of the input value itself, since they are treated as escaped plain characters. For example, if the desired input value is TEST_VALUE1, the input parameter should be set as TEST_VALUE1, if you set it as "TEST_VALUE1", it will be recognized as \"TEST_VALUE1\".
If you do not provide any parameters in the Snap, you can still view the required input parameters in the Target Schema of the upstream Mapper Snap. The parameters are dynamically populated based on the column keys of the stored procedure; you can map the parameters and pass them as an input to the Stored Procedure Snap
Bypassing Parameters
If you wish to bypass any parameter then add a blank row in its place in this section. This is required since the Snap expects the parameters in the order in which they are defined.
For example, if there are three parameters and they are defined as Pipeline parameters _empid, _empname, and _loc and you wish to by pass the parameter _empname, then the Snap should be configured as:
Pass through
Default Value: Deselected
Checkbox
If selected, the input document will be passed through to the output views under the key 'original'. The document will be passed to the Parameter output view, and it will also be passed to the Result Set output view if there is output sent from this view.
This property applies only to the Execute Snaps with SELECT statement or the Select Snaps.
Number of retries
Default Value: 0 Example: 3
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)
Default Value: 1 Example: 10
Integer/Expression
Specify the time interval between two successive retry requests. A retry happens only when the previous attempt resulted in an exception.
Snap execution
Default Value: Execute only Example: Validate & Execute
Dropdown list
Select one of the three modes in which the Snap executes. Available options are:
Validate & Execute: Performs limited execution of the Snap, and generates a data preview during Pipeline validation. Subsequently, performs full execution of the Snap (unlimited records) during Pipeline runtime.
Execute only: Performs full execution of the Snap during Pipeline execution without generating preview data.
Disabled: Disables the Snap and all Snaps that are downstream from it.
The Snap does not support the custom type parameter since SQL Server JDBC driver lacks support for this feature. http://blogs.msdn.com/b/jdbcteam/archive/2012/04/03/how-would-you-use-table-valued-parameters-tvp.aspx
Examples
The following example is an application of the SQL Server Stored Procedure Snap for the example found at http://database.ittoolbox.com/groups/technical-functional/sql-server-l/example-of-code-that-overloads-a-sql-server-stored-procedure-5406272
Create a table called dbo.EMP by executing the following code:
CREATE TABLE [dbo].[EMP]( [EMPNO] [int] NOT NULL, [ENAME] [varchar](10) COLLATE SQL_Latin1_General_CP1_CI_AS NULL, [DEPTNO] [int] NOT NULL, CONSTRAINT [EMP_EMPNO_PK] PRIMARY KEY CLUSTERED ( [EMPNO] ASC )WITH (IGNORE_DUP_KEY = OFF) ON [PRIMARY] ) ON [PRIMARY]
Insert several rows:
INSERT INTO [dbo].[EMP] VALUES (1111,’EDWARDS’,10);
INSERT INTO [dbo].[EMP] VALUES (2222,’ALLEN’,10);
INSERT INTO [dbo].[EMP] VALUES (3333,’WATTS’,20);
INSERT INTO [dbo].[EMP] VALUES (4444,’KIRAN’,20);
INSERT INTO [dbo].[EMP] VALUES (5555,’CASTER’,20);
INSERT INTO [dbo].[EMP] VALUES (6666,’VIJI’,30);
INSERT INTO [dbo].[EMP] VALUES (7777,’DATTA’,30);
Create a store procedure "EMP_PROC" with three input parameters:
CREATE proc [dbo].[EMP_PROC] @empno int=null, @ename varchar(10)=null, @deptno int=null AS IF EXISTS(SELECT 1 from [EMP] where EMPNO = @empno) BEGIN UPDATE [EMP] SET [EMPNO] = COALESCE(@empno,EMPNO), [ENAME] = COALESCE(@ename,ENAME), [DEPTNO] = COALESCE(@deptno,DEPTNO) WHERE EMPNO = @empno END
Build and execute the pipeline:
The input data to the SQL Server - Stored Procedure Snap is:
Only two input parameter values are provided while there are three input parameters in the procedure. This is possible because the procedure is written to support the overload feature. Executing the above pipeline will result in the update of ENAME value in the first row from "EDWARD" to "Ted".
Downloads
Important steps to successfully reuse Pipelines
Download and import the pipeline into the SnapLogic application.
Configure Snap accounts as applicable.
Provide pipeline parameters as applicable.
File
Modified
No files shared here yet.
Snap Pack History
Click here to expand...
Release
Snap Pack Version
Date
Type
Updates
August 2024
main27765
Stable
Updated and certified against the current Snaplogic Platform release.
May 2024
437patches27732
Latest
Fixed an issue with the SQL Server - Select Snap configured with an Ultra task to handle temporary database unavailability. The Snap now validates the database connection to ensure that it is reestablished after temporary database outages.
May 2024
437patches27328
Latest
Fixed an issue with the SQL Server Insert Snap that caused an error when inserting the infinity value into a decimal-type column.
May 2024
437patches27091
Latest
Fixed a case-sensitivity issue with the SQL Server—Bulk Load Snap that caused a NullPointerException when retrieving the PATH environment variable in a Windows environment. This change is applicable only to Windows, as environment variables are case-sensitive in Linux.
May 2024
main26341
Stable
Updated the Delete Condition (Truncates a Table if empty) field in the SQL Server - DeleteSnap to Delete condition (deletes all records from a table if left blank) to indicate that all entries will be deleted from the table when this field is blank, but no truncate operation is performed.
February 2024
436patches26177
Latest
Fixed an issue with the SQL Server Snap Pack that displayed an error when numeric values with scale 0 were inserted into the database with DECIMAL or NUMERIC type columns, instead of inserting the value with decimal digits truncated.
Fixed an issue with the SQL Server Snap Pack that displayed an error when fractional numeric values (numbers with a decimal point) were inserted into the database with an INT type column, instead of inserting the value with decimal digits truncated.
February 2024
436patches25757
Latest
Fixed an issue with the SQL Server - Insert Snap that previously displayed an error when attempting to insert a true or false value into a TinyInt datatype. The Snap now correctly inserts 1 or 0 for true or false in the table, respectively.
February 2024
436patches25548
Latest
Added support for XML and spatial types (Geography and Geometry) for SQL Server Snap Pack.
Fixed an issue with the SQL Server - Insert Snap that displayed an error when an empty or blank string was passed as a value to an integer-type column.
Behavior change: As part of the JOOQ upgrade done in main25112, the SQL Server-Insert Snap displayed the following error when an empty string was inserted to an integer-type column: Caused by: java.lang.NumberFormatException: Character n is neither a decimal digit number, decimal point, nor "e" notation exponential mark Now, the Snap inserts a null value in this scenario.
February 2024
main25112
Stable
As of main25112, the SQL Server Snap Pack no longer supports the jDTS driver. If you are using the latest SQL Server driver versions (2014 and higher), we recommend you use the driver that is bundled with the SQL Server Snap Pack. Note that the older SQL Server versions are supported as is.
November 2023
main23721
Stable
Updated and certified against the current SnapLogic Platform release.
August 2023
434patches22758
Latest
Fixed an issue with the SQL Server Stored Procedure and Table List Snaps that caused no retries to be executed even if you select the number of retries in the UI when a custom JDBC driver was used.
August 2023
434patches22579
Latest
Improved the SQL Server Bulk Load Snap to reduce the chance of causing a deadlock error.
August 2023
main22460
Stable
The SQL Server - Execute Snap now includes a new Query type field. When Auto is selected, the Snap tries to determine the query type automatically.
The SQL Server Snap Pack is upgraded to the latest version of the Microsoft JDBC Driver 12.2.0.jre11 for SQL Server:
Pipelines using the default JAR in the SQL server accounts might fail after the driver upgrade because the latest driver is backward-incompatible. To prevent your accounts from failing, reconfigure the URL properties field in account settings as follows:
trustServerCertificate = true
Pipelines NOT using the default driver (bundled with the SQL Server Snap Pack) will not fail. Note: This update will be a part of the stable distribution with the GA release on August 9, 2023. Learn more about the SQL Server driver upgrade: FAQ for Upgrading to SQL Server JDBC Driver 12.2.0
Fixed an issue with the SQL Server Insert Snap that was causing performance degradation between GA release 4.32 and 4.33 if the network connection between the Groundplex and the database server was slow.
May 2023
433patches21386
-
The SQL Server Snap Pack is upgraded to the latest version of the Microsoft JDBC Driver 12.2.0.jre11 for SQL Server:
Pipelines using the default JAR in the SQL server accounts might fail after the driver upgrade because the latest driver is backward-incompatible. To prevent your accounts from failing, reconfigure the URL properties field in account settings as follows:
trustServerCertificate = true
Pipelines NOT using the default driver (bundled with the SQL Server Snap Pack) will not fail.
The Microsoft JDBC Driver 12.2.0.jre11 for SQL Server included in the SQL Server Snap Pack is currently NOT available with the latest distribution. However, you can still consume this patch through 433patches21386. This update is scheduled to be included in the upcoming distribution release on July 12, 2023, and will be a part of the stable distribution with the GA release on August 9, 2023.
May 2023
433patches21119
Latest
Updated the Bulk Load Snap to preserve empty strings as empty strings and null as nulls.
May 2023
main21015
Stable
Upgraded with the latest SnapLogic Platform release.
February 2023
main19844
Stable
Upgraded with the latest SnapLogic Platform release.
November 2022
431patches19263
Latest
The SQL Server Insert Snap no longer no longer includes the Preserve case-sensitivity checkboxbecause the database is case-insensitive. The database stores the data regardless of whether the columns in the target table and the input data are in mixed, lower, or upper case.
November 2022
431patches19268
Latest
The SQL Server-Insert Snap now displays the error, Number overflow: <number> (instead of Batch operation failed) when inserting a number into tinyinit column.
November 2022
431patches19234
Latest
A memory leak in the SQL Server Stored Procedure Snap is fixed. The Snap now clears the closed connections from memory and retains the open connections.
November 2022
431patches19000
Stable/Latest
The SQL Server accounts failed with a certificate error on Windows Snaplexes when using the default SQL driver with the 4.31 main18944 build. This patch addresses the certificate error issue.
November 2022
main18944
Stable
The MySQL Insert Snap now creates the target table only from the table metadata of the second input view when the following conditions are met:
The Create table if not present checkbox is selected.
The target table does not exist.
The table metadata is provided in the second input view.
August 2022
430patches17064
Latest
The SQL Server - Select Snap now has the Convert rowversion datatype to integer checkbox to support the ROWVERSION data type. Select this checkbox to display the ROWVERSION data type as integers in the output.
4.30 Patch
430patches17368
Latest
The SQL Server Execute Snap containing an explicit SQL transaction now works as expected when using a default JDBC driver.
August 2022
main17386
Stable
Upgraded with the latest SnapLogic Platform release.
4.29 Patch
429patches16235
Latest
Fixed an issue with SQL Server Execute Snap where the Snap did not display a valid error message when the delete condition is invalid.
4.29
main15993
Stable
Enhanced the SQL Server - Bulk Load Snap with the Batch Size field to process records in a batch.
4.28 Patch
428patches14649
Latest
Enhanced the SQL Server - Select and SQL Server - Lookup Snaps with Option for Unique Identifier Column that allows you to convert the case to lower or upper while displaying the Unique Identifier output (display) value.
4.28
main14627
Stable
Updated the label for Delete Condition to Delete Condition (Truncates Table if empty) in the SQL Server Delete Snap.
Fixed an issue in the SQL Server Bulk Load snap where boolean data type failed to load into BIT field.
4.26
main11181
Stable
Upgraded with the latest SnapLogic Platform release.
4.25 Patch
425patches10797
Latest
Fixed an issue with the SQL Server - Bulk Load Snap where the Snap fails when the login password contains a colon or a less than (<) symbol.
4.25
main9554
Stable
Upgraded with the latest SnapLogic Platform release.
4.24 Patch
424patches8657
Latest
Enhances the SQL Server - Select Snap by introducing a new field, Query Hints, which helps to customize and optimize the database engine to process query statements.
4.24
main8556
Stable
Enhances the SQL Server - Select Snap to return only the selected output fields or columns in the output schema (second output view) using the Fetch Output Fields In Schema check box. If the Output Fields field is empty all the columns are visible.
Enhances the SQL Server - Stored Procedure to accept parameters from input documents by column keys. If the values are empty, the parameters are populated based on the column keys for easier mapping in the upstream Mapper Snap.
4.23 Patch
423patches8190
Latest
Fixes an issue with SQL Server - Execute to handle SQL statements that begin with special characters.
4.23
main7430
Stable
Enhances the accounts in this Snap Pack to allow Windows-based (Active Directory) authentication and user impersonation for SQL Server user accounts.
4.22 Patch
422patches6728
Latest
Enhances the SQL Server Snap pack to allow Windows (Active Directory) based authentication and user impersonation for SQL Server user accounts.
4.22
main6403
Stable
Upgraded with the latest SnapLogic Platform release.
4.21 Patch
421patches6272
Latest
Fixes the issue where Snowflake SCD2 Snap generates two output documents despite no changes to Cause-historizationfields with DATE, TIME and TIMESTAMP Snowflake data types, and with Ignore unchanged rows field selected.
4.21 Patch
421patches6144
Latest
Fixes the following issues with DB Snaps:
The connection thread waits indefinitely causing the subsequent connection requests to become unresponsive.
Connection leaks occur during Pipeline execution.
4.21 Patch
MULTIPLE8841
Latest
Fixes the connection issue in Database Snaps by detecting and closing open connections after the Snap execution ends.
4.21 Patch
db/sqlserver8837
Latest
Fixed the SQL Server - Stored Procedure Snap to support the UUID datatype.
4.21
snapsmrc542
Stable
Upgraded with the latest SnapLogic Platform release.
4.20 Patch
db/sqlserver8793
Latest
Fixed an issue in the SQL Server - Insert Snap due to which the Snap failed to load values of data type INT.
4.20 Patch
db/sqlserver8796
Latest
Fixed the SQL Server - Bulk Load Snap to mask the password in the logged exception messages.
4.20
snapsmrc535
Stable
Upgraded with the latest SnapLogic Platform release.
4.19 Patch
db/sqlserver8413
Latest
Fixed an issue with the SQL Server - Update Snap wherein the Snap is unable to perform operations when:
An expression is used in the Update condition property.
Input data contain the character '?'.
4.19
snaprsmrc528
Stable
Upgraded with the latest SnapLogic Platform release.
4.18 Patch
db/sqlserver7989
Latest
Fixed an issue in the SQL Server - Merge Snap wherein identity columns are not handled correctly. Also, added a field, Enable Identity Insert, that enables you to insert values into an identity column.
4.18
snapsmrc523
Stable
Added support for SQL Server account Active Directory authentication for SQL server for driver JAR version mssql-jdbc-6.2.2-jre8.jar.
Reverts a 4.17-patch (db/sqlserver7394) update regarding how BIT and BOOLEAN column data type values are displayed. They now display as true or false (4.17 GA behavior in snapsmrc515) rather than converting to 0 or 1 values (4.17-patch behavior).
4.17 Patch
MULTIPLE7479
Latest
Fixed an issue with the SQL Server - Lookup Snap wherein it fails a UUID search.
4.17
ALL7402
Latest
Pushed automatic rebuild of the latest version of each Snap Pack to SnapLogic UAT and Elastic servers.
4.17
snapsmrc515
Latest
Fixed an issue with the SQL Server Execute Snap wherein the Snap would send the input document to the output view even if the Pass through field is not selected in the Snap configuration. With this fix, the Snap sends the input document to the output view, under the key original, only if you select the Pass through field.
Added the Snap Execution field to all Standard-mode Snaps. In some Snaps, this field replaces the existing Execute during preview check box.
4.16 Patch
db/sqlserver6981
Latest
Fixed an issue of slow performance in SQL Server Snaps while using SQL Server Dynamic account type.
4.16 Patch
db/sqlserver6818
Latest
Fixed an issue with the Lookup Snap passing data simultaneously to output and error views when some values contained spaces at the end.
4.16
snapsmrc508
Stable
Upgraded with the latest SnapLogic Platform release.
4.15 Patch
db/sqlserver6337
Latest
Replaced Max idle time and Idle connection testperiod properties with Max life time and Idle Timeout properties respectively, in the Account configuration. The new properties fix the connection release issues that were occurring due to default/restricted DB Account settings.
4.15
snapsmrc500
Stable
Upgraded with the latest SnapLogic Platform release.
4.14 Patch
db/sqlserver5912
Latest
Fixed an issue to parse the right data type and display it in the input schema for SQL Server Snap..
4.14 Patch
db/sqlserver5665
Latest
Implemented a connection retry logic in the SQL Server account to resolve the connection loss issue in a customer's org.
4.14
snapsmrc490
Stable
Upgraded with the latest SnapLogic Platform release.
4.13
snapsmrc486
Stable
Upgraded with the latest SnapLogic Platform release.
4.12
snapsmrc480
Stable
Upgraded with the latest SnapLogic Platform release.
4.11 Patch
db/sqlserver4388
Latest
Fixed an issue with the Stored Procedure Snap that does not maintain the columns' order on the output as per table's definition.
4.11 Patch
db/sqlserver4288
Latest
SQL Server Snap Pack - Fixed an issue when inserting a valid NaN value into a column.
4.11
snapsmrc465
Stable
Upgraded with the latest SnapLogic Platform release.
4.10 Patch
sqlserver3953
Latest
Fixed an issue where the SQL Server Stored Procedure gets hanged when more than one Snap existed in the pipeline each processing greater than 1K documents.
4.10
snapsmrc414
Stable
Added Auto commit property to the Select and Execute Snaps at the Snap level to support overriding of the Auto commit property at the Account level.
4.9.0 Patch
sqlserver3224
Latest
Addressed an issue with SQL Server - Bulk Load execution even with 0 input documents
4.9.0 Patch
sqlserver3076
Latest
Fixed an issue regarding connection not closed after login failure; Expose autocommit for "Select into" statement in PostgreSQL Execute Snap and Redshift Execute Snap
4.9
snapsmrc405
Stable
Upgraded with the latest SnapLogic Platform release.
4.8.0 Patch
sqlserver2803
Latest
Addressed an issue with slow performance with Bulk Load BCP.
4.8.0 Patch
sqlserver2761
Latest
Potential fix for JDBC deadlock issue.
4.8.0 Patch
sqlserver2706
Latest
Fixed SQL Server Snap Pack rendering dates that are one hour off from the date returned by database query for non-UTC Snaplexes.
4.8
snapsmrc398
Stable
Upgraded with the latest SnapLogic Platform release.
4.7
snapsmrc382
Stable
Extended support for SQL Server Dynamic accounts.
Updated the SQL Server Stored Procedure Snap with the Pass through field.
4.6
snapsmrc362
Stable
Resolved an issue in SQL Server Bulk Load Snap that caused BCP program related failures.
Enhanced to fully support SQL statements with/without expressions & SQL bind variables.
Resolved an issue that caused failures when executing merge statements.
4.5.1
snapsmrc344
Latest
Upgraded with the latest SnapLogic Platform release.
4.5
snapsmrc344
Stable
Resolved an issue in SQL Server Execute Snap that erroneously reported a database/schema mismatch during Snap/pipeline execution.
Resolved an issue in SQL Server Lookup Snap that occurred when handling case-insensitive field values.