- Created by Diane Miller, last modified by Amritesh Singh on Jan 13, 2023
You are viewing an old version of this page. View the current version.
Compare with Current View Page History
« Previous Version 41 Next »
In this article
This account is used by the Snaps in the Azure SQL Snap Pack.
You can create an account from Designer or Manager. In Designer, when working on Pipelines, every Snap that needs an account prompts you to create a new account or use an existing account. The accounts can be created in or used from:
- Your private project folder: This folder contains the Pipelines that will use the account.
- Your Project Space’s shared folder: This folder is accessible to all the users that belong to the Project Space.
- The global shared folder: This folder is accessible to all the users within an organization in the SnapLogic instance.
Limitations
Selecting the Disable Connection Pooling checkbox forces the session state to close the existing connection and reopen another connection to the database for each Snap until the Pipeline is executed, which might affect the performance. Therefore, we recommend that you select the Disable Connection Pooling checkbox only when there is clear isolation between Snap executions within a Pipeline.
Account Configuration
In Manager, you can navigate to the required folder and create an account in it (see Accounts). To create an account for binary files:
- Click Create, then select any Azure SQL Account:
- Azure SQL Account
- Azure SQL Dynamic Account
Azure SQL Active Directory Account
Azure SQL Active Directory Dynamic Account
- Supply an account label.
- Supply the account properties for your database.
- (Optional) Supply additional information on this account in the Notes field of the Info tab.
- Click Apply.
Avoid changing account credentials while Pipelines using them are in progress. This may lead to unexpected results, including locking the account.
You can Validate an account connection when creating a Azure SQL/Active Directory Account but not when creating a Azure SQL/Active Directory Dynamic Account because the account properties of a dynamic account are provided dynamically as Pipeline parameters.
The difference between Azure SQL/Active Directory Account and Azure SQL/Active Directory Dynamic Account is that in the latter you can specify the Account properties as expressions referencing Pipeline parameters.
Account Types
Active Directory-based authentication is not supported in the Azure SQL Bulk Extract Snap.
Azure SQL Account
Label | Required. User provided label for the account instance. | |
---|---|---|
Account properties | Required. Enter in the information to create a connection to the database. | |
Hostname | Required. The server's address to connect to. Default value: [None] | |
Port Number | Required. The database server's port to connect to. Default value: 3306 | |
Database name | Required. The database name to connect to. Default value: [None] | |
Username | Username that is allowed to connect to the database. Username will be used as the default username when retrieving connections. The username must be valid in order to set up the data source. Default value: [None] | |
Password | Password used to connect to the data source. Password wil be used as the default password when retrieving connections. The password must be valid in order to set up the data source. Default value: [None] | |
JDBC Jars | List of JDBC Jar files to be loaded. Example: ../shared/sqljdbc4-2.0.jar The Azure SQL Snap Pack uses the 11.2x driver by default. If you specify any specific driver, ensure that you provide a version higher than 9.1 that is compatible with the Microsoft Authentication Library for Java, becuase this Snap Pack uses the MSAL4J; otherwise, you may encounter errors. | |
JDBC Driver Class | Required. JBDC driver class name to use. Default value: com.microsoft.sqlserver.jdbc.SQLServerDriver | |
Trust all certificates | Select if all SSL certificates are to be accepted for connecting to the database Default value: Not selected | |
Azure storage account name | Required. Name with which Azure Storage was created. The Bulk Load Snap automatically appends the '.blob.core.windows.net' domain to the value of this property. | |
Azure storage account key | Required. Key generated by Azure for this account. | |
Azure storage container name | Required. Name of an existing container. | |
Advanced properties | ||
Auto commit | When selected, each of the batches is committed immediately after it is executed. If the Snap fails, only the batch being executed at that moment is rolled back. When deselected, the Snap execution output is committed only after all the batches are executed. If the Snap fails, the entire transaction is rolled back, unless the Snap finds invalid input data before it sends the insert request to the server, and routes the error documents to the Error view. Default value: Selected | |
Disable connection pooling | Select this checkbox to prevent the sharing of session state. Connection pooling keeps the connections active. When the Snap uses a connection and creates a table during execution, the table gets locked and is not released even after the Snap is executed and the connection is returned to the pool. If another Snap or the same Snap uses the same connection from the pool and reads the metadata of the same table, it displays an error that the resource is locked. We recommend you to select this checkbox for Snaps that use session state, for example, creating a temporary table. Default Value: Deselected | |
Batch size | Required. Number of statements to execute at a time. Select queries are not batched. Using a large batch size could use up the JDBC placeholder limit of 2100. Default value: 50 | |
Fetch size | Required. Number of rows to fetch at a time when executing a query. Large values could cause the server to run out of memory. Default value: 100 | |
Max pool size | Required. Maximum number of connections a pool will maintain at a time. Default value: 50 | |
Max life time | Required. Maximum lifetime of a connection in the pool. Ensure that the value you enter is a few seconds shorter than any database or infrastructure-imposed connection time limit. A value of 0 indicates an infinite lifetime, subject to the Idle Timeout value. An in-use connection is never retired. Connections are removed only after they are closed. Default value: 30 | |
Idle Timeout | Required. The maximum amount of time a connection is allowed to sit idle in the pool. A value of 0 indicates that idle connections are never removed from the pool. Default value: 5 | |
Checkout timeout | Required. Number of milliseconds to wait for a connection to be available when the pool is exhausted. If you specify 0, the Snap waits infinitely until the connection is available. Therefore, we recommend you not to specify 0 for Checkout Timeout. Default value: 10000 | |
URL Properties | ||
URL property name | URL property name Default value: [None] | |
URL property value | URL property value Default value: [None] |
Account Encryption
Standard Encryption | If you are using Standard Encryption, the High sensitivity settings under Enhanced Encryption are followed. | |
---|---|---|
Enhanced Encryption | If you have the Enhanced Account Encryption feature, the following describes which fields are encrypted for each sensitivity level selected for this account. Account:
|
Azure SQL Dynamic Account
Expression-enabled authentication fields, such as Username, Password, and Client Secret, support Secrets Management, a SnapLogic add-on that allows you to store endpoint credentials in a third-party secrets manager, such as AWS Secrets Manager, Azure Key Vault, or HashiCorp Vault. During validation and execution, pipelines obtain the credentials directly from the secrets manager. Learn more: Configure Accounts to use secrets.
With the Dynamic Account, you can specify the Account properties as expressions referencing Pipeline parameters.
Account Settings
Label | Required. User provided label for the account instance. | |
---|---|---|
Account properties | Required. Enter in the information to create a connection to the database. | |
Hostname | Required. The server's address to connect to. Default value: [None] | |
Port Number | Required. The database server's port to connect to. Default value: 3306 | |
Database name | Required. The database name to connect to. Default value: [None] | |
Username | Username that is allowed to connect to the database. Username will be used as the default username when retrieving connections. The username must be valid in order to set up the data source. Default value: [None] | |
Password | Password used to connect to the data source. Password wil be used as the default password when retrieving connections. The password must be valid in order to set up the data source. Default value: [None] | |
JDBC Jars | List of JDBC Jar files to be loaded. Example: ../shared/sqljdbc4-2.0.jar | |
JDBC Driver Class | Required. JBDC driver class name to use. Default value: com.microsoft.sqlserver.jdbc.SQLServerDriver | |
Trust all certificates | Select if all SSL certificates are to be accepted for connecting to the database Default value: Not selected | |
Azure storage account name | Required. Name with which Azure Storage was created. The Bulk Load Snap automatically appends the '.blob.core.windows.net' domain to the value of this property. | |
Azure storage account key | Required. Key generated by Azure for this account. | |
Azure storage container name | Required. Name of an existing container. | |
Advanced properties | ||
Auto commit | When selected, each of the batches is committed immediately after it is executed. If the Snap fails, only the batch being executed at that moment is rolled back. When deselected, the Snap execution output is committed only after all the batches are executed. If the Snap fails, the entire transaction is rolled back, unless the Snap finds invalid input data before it sends the insert request to the server, and routes the error documents to the Error view. Default value: Selected | |
Batch size | Required. Number of statements to execute at a time. Select queries are not batched. Using a large batch size could use up the JDBC placeholder limit of 2100. Default value: 50 | |
Fetch size | Required. Number of rows to fetch at a time when executing a query. Large values could cause the server to run out of memory. Default value: 100 | |
Max pool size | Required. Maximum number of connections a pool will maintain at a time. Default value: 50 | |
Max life time | Required. Maximum lifetime of a connection in the pool. Ensure that the value you enter is a few seconds shorter than any database or infrastructure-imposed connection time limit. A value of 0 indicates an infinite lifetime, subject to the Idle Timeout value. An in-use connection is never retired. Connections are removed only after they are closed. Default value: 30 | |
Idle Timeout | Required. The maximum amount of time a connection is allowed to sit idle in the pool. A value of 0 indicates that idle connections are never removed from the pool. Default value: 5 | |
Checkout timeout | Required. Number of milliseconds to wait for a connection to be available when the pool is exhausted. Zero waits forever. An exception will be thrown after the wait time has expired. If you specify 0, the Snap waits infinitely until the connection is available. Therefore, we recommend you not to specify 0 for Checkout Timeout. Default value: 10000 | |
URL Properties | ||
URL property name | URL property name Default value: [None] | |
URL property value | URL property value Default value: [None] |
Account Encryption
Standard Encryption | If you are using Standard Encryption, the High sensitivity settings under Enhanced Encryption are followed. | |
---|---|---|
Enhanced Encryption | If you have the Enhanced Account Encryption feature, the following describes which fields are encrypted for each sensitivity level selected for this account. Account:
|
Azure SQL Active Directory Account
Label | Required. User provided label for the account instance. | |
---|---|---|
Account properties | Required. Enter in the information to create a connection to the database. | |
Hostname | Required. The server's address to connect to. Default value: [None] | |
Port Number | Required. The database server's port to connect to. Default value: 1433 | |
Database name | Required. The database name to connect to. Default value: [None] | |
Authentication Mode | Select either of the following options for Azure SQL Authentication:
Default Value: Example: Active Directory Service Principal | |
Username
| Username that is allowed to connect to the database. Username will be used as the default username when retrieving connections. The username must be valid in order to set up the data source. Default value: [None] | |
Password
| Password used to connect to the data source. Password wil be used as the default password when retrieving connections. The password must be valid in order to set up the data source. Default value: [None] | |
Trust all certificates | Select if all SSL certificates are to be accepted for connecting to the database Default value: Deselected | |
Advanced properties | ||
Auto commit | When selected, each of the batches is committed immediately after it is executed. If the Snap fails, only the batch being executed at that moment is rolled back. When deselected, the Snap execution output is committed only after all the batches are executed. If the Snap fails, the entire transaction is rolled back, unless the Snap finds invalid input data before it sends the insert request to the server, and routes the error documents to the Error view. Default value: Selected | |
Disable connection pooling | Select this checkbox to prevent the sharing of session state. Connection pooling keeps the connections active. When the Snap uses a connection and creates a table during execution, the table gets locked and is not released even after the Snap is executed and the connection is returned to the pool. If another Snap or the same Snap uses the same connection from the pool and reads the metadata of the same table, it displays an error that the resource is locked. We recommend you to select this checkbox for Snaps that use session state, for example, creating a temporary table. Default Value: Deselected | |
Batch size | Required. Number of statements to execute at a time. Select queries are not batched. Using a large batch size could use up the JDBC placeholder limit of 2100. Default value: 50 | |
Fetch size | Required. Number of rows to fetch at a time when executing a query. Large values could cause the server to run out of memory. Default value: 100 | |
Max pool size | Required. Maximum number of connections a pool will maintain at a time. Default value: 50 | |
Max life time | Required. Maximum lifetime of a connection in the pool. Ensure that the value you enter is a few seconds shorter than any database or infrastructure-imposed connection time limit. A value of 0 indicates an infinite lifetime, subject to the Idle Timeout value. An in-use connection is never retired. Connections are removed only after they are closed. Default value: 30 | |
Idle Timeout | Required. The maximum amount of time a connection is allowed to sit idle in the pool. A value of 0 indicates that idle connections are never removed from the pool. Default value: 5 | |
Checkout timeout | Required. Number of milliseconds to wait for a connection to be available when the pool is exhausted. If you specify 0, the Snap waits infinitely until the connection is available. Therefore, we recommend you not to specify 0 for Checkout Timeout. Default value: 10000 | |
URL Properties | ||
URL property name | URL property name Default value: [None] | |
URL property value | URL property value Default value: [None] |
Account Encryption
Standard Encryption | If you are using Standard Encryption, the High sensitivity settings under Enhanced Encryption are followed. | |
---|---|---|
Enhanced Encryption | If you have the Enhanced Account Encryption feature, the following describes which fields are encrypted for each sensitivity level selected per each account.
|
Azure SQL Active Directory Dynamic Account
Expression-enabled authentication fields, such as Username, Password, and Client Secret, support Secrets Management, a SnapLogic add-on that allows you to store endpoint credentials in a third-party secrets manager, such as AWS Secrets Manager, Azure Key Vault, or HashiCorp Vault. During validation and execution, pipelines obtain the credentials directly from the secrets manager. Learn more: Configure Accounts to use secrets.
With the Dynamic Account, you can specify the Hostname, Username, Database name, and Password dynamically using Pipeline parameters since they support SnapLogic expressions. You will need to enable the expression-mode by clicking the button to pass values dynamically as Pipeline parameters.
Account Settings
Label | Required. User provided label for the account instance. | |
---|---|---|
Account properties | Required. Enter in the information to create a connection to the database. | |
Hostname | Required. The server's address to connect to. Default value: [None] | |
Port Number | Required. The database server's port to connect to. Default value: 1433 | |
Database name | Required. The database name to connect to. Default value: [None] | |
Authentication Mode | Select either of the following options for Azure SQL Authentication:
Default Value: Example: Active Directory Service Principal | |
Username | Username that is allowed to connect to the database. Username will be used as the default username when retrieving connections. The username must be valid in order to set up the data source. Default value: [None] | |
Password | Password used to connect to the data source. Password wil be used as the default password when retrieving connections. The password must be valid in order to set up the data source. Default value: [None] | |
Trust all certificates | Select if all SSL certificates are to be accepted for connecting to the database Default value: Not selected | |
Advanced properties | ||
Auto commit | When selected, each of the batches is committed immediately after it is executed. If the Snap fails, only the batch being executed at that moment is rolled back. When deselected, the Snap execution output is committed only after all the batches are executed. If the Snap fails, the entire transaction is rolled back, unless the Snap finds invalid input data before it sends the insert request to the server, and routes the error documents to the Error view. Default value: Selected | |
Batch size | Required. Number of statements to execute at a time. Select queries are not batched. Using a large batch size could use up the JDBC placeholder limit of 2100. Default value: 50 | |
Fetch size | Required. Number of rows to fetch at a time when executing a query. Large values could cause the server to run out of memory. Default value: 100 | |
Max pool size | Required. Maximum number of connections a pool will maintain at a time. Default value: 50 | |
Max life time | Required. Maximum lifetime of a connection in the pool. Ensure that the value you enter is a few seconds shorter than any database or infrastructure-imposed connection time limit. A value of 0 indicates an infinite lifetime, subject to the Idle Timeout value. An in-use connection is never retired. Connections are removed only after they are closed. Default value: 30 | |
Idle Timeout | Required. The maximum amount of time a connection is allowed to sit idle in the pool. A value of 0 indicates that idle connections are never removed from the pool. Default value: 5 | |
Checkout timeout | Required. Number of milliseconds to wait for a connection to be available when the pool is exhausted. If you specify 0, the Snap waits infinitely until the connection is available. Therefore, we recommend you not to specify 0 for Checkout Timeout. Default value: 10000 | |
URL Properties | ||
URL property name | URL property name Default value: [None] | |
URL property value | URL property value Default value: [None] |
Account Encryption
Standard Encryption | If you are using Standard Encryption, the High sensitivity settings under Enhanced Encryption are followed. | |
---|---|---|
Enhanced Encryption | If you have the Enhanced Account Encryption feature, the following describes which fields are encrypted for each sensitivity level selected per each account.
|
Snap Pack History
Release | Snap Pack Version | Date | Type | Updates |
---|---|---|---|---|
August 2024 | main27765 | Stable | Upgraded the org.json.json library from v20090211 to v20240303, which is fully backward compatible. | |
May 2024 | 437patches27180 | Latest | Fixed the following issues with the Azure SQL - Bulk Load Snap:
| |
May 2024 | main26341 | Stable | The following Azure SQL Active Directory Accounts have been renamed because Microsoft has rebranded Azure Active Directory to Microsoft Entra ID.
| |
February 2024 | 436patches25468 | Latest | The Azure SQL Bulk Extract Snap now supports Azure SQL Active Directory and Azure SQL Active Directory Dynamic Accounts. | |
February 2024 | main25112 | Stable | Updated and certified against the current SnapLogic Platform release. | |
November 2023 | main23721 | Stable | Updated and certified against the current SnapLogic Platform release. | |
August 2023 | main22460 |
| Stable | The Azure SQL Execute Snap now includes a new Query type field. When Auto is selected, the Snap determines the query type automatically. |
May 2023 | main21015 | Stable | Upgraded with the latest SnapLogic Platform release. | |
May 2023 | 432patches20967 | Latest | Fixed an issue with the connection pool in the Azure SQL accounts, which was affecting the Snap Pack's performance. You should now experience improved performance when using these accounts. | |
March 2023 | 432patches20318 | Latest | The Azure SQL - Bulk Extract Snap no longer fails with a | |
March 2023 | 432patches20219 | Latest | Fixed an issue with the Azure SQL - Bulk Load Snap involving special characters in JDBC URL properties, such as passwords. Special characters are properly escaped now | |
March 2023 | 432patches20049 | Latest | Intermittent connectivity issues no longer occur when using some Snaps in the Azure SQL Snap Pack. These issues caused the following message to display: The connection is broken and recovery is not possible. The connection is marked by the client driver as unrecoverable. No attempt was made to restore the connection. | |
February 2023 | main19844 | Stable | Upgraded with the latest SnapLogic Platform release. | |
January 2023 | 431patches19493 | Latest | The Azure SQL Active Directory and the Azure SQL Active Directory Dynamic accounts now include an Authentication Mode dropdown list, which allows you to choose the Active Directory authentication mode you would like to use. This enhancement supports Active Directory Service Principal authentication for the Snap Pack. | |
December 2022 | 431patches19410 |
| Stable Latest | Fixed the Azure SQL - Execute Snap using the Azure SQL Active Directory Account that failed with SQL operation failed errors in environments using federated authentication. |
December 2022 | 431patches19263 | Latest | The Azure Synapse SQL Insert Snap no longer includes the Preserve case-sensitivity checkbox because 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 | main18944 | Stable | The Azure SQL Snap Pack uses the 11.2x driver by default. If you specify any specific driver, ensure that you provide a version higher than 9.1 that is compatible with Microsoft Authentication Library for Java, as this Snap Pack uses the MSAL4J. Otherwise, you may run into issues. | |
August 2022 | main17386 | Stable | The Azure Active Directory Search Entries Snap includes a Display Properties field where you can specify the properties to display in the output for the user or group. For the Snap to correctly return the attributes in the output, you must specify the attribute name as described in User profile attributes in Azure Active Directory B2C. Learn more about Properties for a user and Properties for a group. | |
4.29 Patch | 429patches16545 | Latest | Fixed an issue with the Azure SQL-Stored Procedure Snap where the Snap failed with an | |
4.29 Patch | 429patches16460 | Latest | Fixed an issue with Azure SQL Bulk Load Snap where the Snaplex exited due to insufficient memory when a large number of rows are loaded into the target table and the input data contained a null value for a non-nullable column. | |
4.29 | main15993 | Stable | Enhanced the Azure SQL Account and Azure SQL Active Directory Account with the Disable connection pooling checkbox that allows you to manage session state sharing. | |
4.28 Patch | 428patches15164 | Latest | Fixed an issue with the Azure SQL - Update Snap where the Snap failed with an Incorrect syntax error when a column in a table is of NVARCHAR, NCHAR, or NTEXT data type and this column is part of another NVARCHAR, NCHAR, or NTEXT data type column name and the update condition is specified as an expression. | |
4.28 Patch | 428patches15114 | Latest | Fixed an issue with the Azure SQL - Bulk Load Snap where the decimal values lost precision when they were inserted into the database. | |
4.28 | main14627 | Stable | Upgraded with the latest SnapLogic Platform release. | |
4.27 | main12833 | Stable | Enhanced the Azure SQL - Execute Snap to invoke stored procedures. | |
4.26 | main11181 | Stable | Upgraded with the latest SnapLogic Platform release. | |
4.25 | main9554 | Stable | Upgraded with the latest SnapLogic Platform release. | |
4.24 | main8556 | Stable | Enhances the Azure SQL - 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 | main7430 | Stable | Enhances the Azure SQL - Bulk Extract Snap by adding a new check box Enable UTF-8 encoding to support UTF-8 encoded characters. This check box allows the Snap to update the BCP command to read the special characters. | |
4.22 Patch | 422Patches6751 | Latest | Enhances the Azure SQL - Bulk Extract Snap by adding a new check box Enable UTF-8 encoding to support UTF-8 encoded characters. Selected by default, this check box allows the Snap to update the BCP command to read these special characters. | |
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-historization fields 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:
| |
4.21 Patch | 421patches5864 | Latest | Adds support for UTF_8 characters with BCP (bulk copy program) command to the Azure SQL Bulk Extract Snap. | |
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 | snapsmrc542 |
| Stable | Upgraded with the latest SnapLogic Platform release. |
4.20 | snapsmrc535 | Stable | Upgraded with the latest SnapLogic Platform release. | |
4.19 Patch | db/azuresql8403 | Latest | Fixes an issue with the Azure SQL - Update Snap wherein the Snap is unable to perform operations when:
| |
4.19 | snaprsmrc528 | Stable | Enhanced the error handling in PolyBase Bulk Load Snap when writing to a data warehouse. The Snap writes a new blob in the Azure container. This new blob highlights the first invalid row that caused the bulk load operation to fail. | |
4.18 | snapsmrc523 | Stable | Upgraded with the latest SnapLogic Platform release. | |
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 |
| |
4.16 Patch | db/azuresql7179 | Latest | Fixes an issue with the Azure SQL Bulk Extract Snap wherein the Snap fails to process all the metadata information of the input table and schema. | |
4.16 | snapsmrc508 | Stable | Upgraded with the latest SnapLogic Platform release. | |
4.15 Patch | db/azuresql6327 | Latest | Replaced Max idle time and Idle connection test period 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 | 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 | azuresql4631 | Latest | Fixes an issue with the Azure Polybase Bulk Load Snap that failed with "Parse error" when there was no input. | |
4.11 Patch | db/azuresql4326 | Latest |
| |
4.11 | snapsmrc465 | Stable | Upgraded with the latest SnapLogic Platform release. | |
4.10 | snapsmrc414 | Stable |
| |
4.9 Patch | azuresql3078 | Latest | Fixes 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 Patch | azuresql2750 | Latest | Potential fix for JDBC deadlock issue. | |
4.8 | snapsmrc398 | Stable |
| |
4.7 Patch | azuresql2196 | Latest | Fixes an issue for database Select Snaps regarding Limit rows not supporting an empty string from a pipeline parameter. | |
4.7 | snapsmrc382 | Stable | Upgraded with the latest SnapLogic Platform release. | |
4.6 | snapsmrc362 | Stable | Upgraded with the latest SnapLogic Platform release. | |
4.5.1 | snapsmrc344 | Stable | Upgraded with the latest SnapLogic Platform release. | |
4.5 | snapsmrc344 | Stable | Upgraded with the latest SnapLogic Platform release. |
- No labels