Problem Note 70686: SAS/ACCESS® Interface to Snowflake automatically switches AUTOCOMMIT to OFF before a transaction and then back to ON after a transaction in Snowflake
Currently, SAS/ACCESS Interface to Snowflake automatically switches AUTOCOMMIT to OFF in Snowflake before a transaction and then sets AUTOCOMMIT back to ON after a transaction. This issue occurs due to the default AUTOCOMMIT=NO setting in SAS®.
The default setting for AUTOCOMMIT has been changed to YES with the SAS® Viya® Platform Stable 2024.02 cadence and with SAS® 9.4M8 (TS1M8) with the application of Hot Fix L9B004 or later.
The advantage of this change is increased efficiency when working with Snowflake when doing query operations. You might want to set AUTOCOMMIT to NO if your workload is more transactional and you want the ability to roll back operations that have been made since the last commit.
Without the change, you can set AUTOCOMMIT=YES yourself on your LIBNAME or CONNECT TO statements to change to the new default behavior.
To revert to the prior behavior, set the options to NO. There is also the following environment variable option:
options set=SAS_SNOWFLAKE_AUTOCOMMIT="NO";
Click the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
SAS System | SAS/ACCESS Interface to Snowflake (on SAS Viya) | Linux for x64 | V.03.04 | Stable 2024.02 | Viya | Viya |
Microsoft® Windows® for x64 | V.03.04 | | Viya | |
SAS System | SAS/ACCESS Interface to Snowflake | Linux for x64 | | | 9.4 TS1M6 | |
Microsoft® Windows® for x64 | | | 9.4 TS1M6 | |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
Type: | Problem Note |
Priority: | high |
Date Modified: | 2024-03-12 13:05:59 |
Date Created: | 2024-03-04 14:26:45 |