What's New in SAS/ACCESS 9.4 for Relational Databases

Overview

Here are the new features and enhancements in SAS 9.4 for SAS/ACCESS for Relational Databases.

In SAS 9.4M1, the BL_ESCAPE= data set option is new for multiple interfaces.

In SAS 9.4M2, Cloudera Impala is a new SAS/ACCESS interface.

In SAS 9.4M3, these features are new or enhanced:

In SAS 9.4M5, these features are new or enhanced:

In SAS Viya 3.3, integration was added between SAS/ACCESS and SAS Viya.

In SAS Viya 3.4, support for the JDBC interface on SAS Viya 3.4 was added.

In SAS 9.4M6, support for the JDBC interface on SAS 9.4 was added.

In the August 2019 release of SAS/ACCESS on SAS 9.4M6, support for the Google BigQuery and Snowflake interfaces was added.

In SAS Viya 3.5, sample programs were moved from an installation directory onto a GitHub repository. Samples for most interfaces are available from https://github.com/sassoftware/sas-access-samples

In SAS 9.4M7, support was added for the Spark interface and for the Yellowbrick interface. Also, in this release, SAS/ACCESS Interface to Spark is no longer available on SAS Viya 3.4 or SAS Viya 3.5.

In SAS 9.4M8, Databricks access is supported with the Spark engine.

System Options

DBIDIRECTEXEC

In SAS 94M8, the DBIDIRECTEXEC system option is enabled by default for all data sources. This is a change for these data sources:

DB2 under UNIX and PC Hosts Netezza
DB2 under z/OS Oracle
Greenplum PostgreSQL
Hadoop SAP ASE
Impala SAP HANA
Informix SAP IQ
Microsoft SQL Server Teradata
MySQL Vertica

SQLGENERATION=

In SAS 9.4M3, the default value of the SQLGENERATION= system option became (NONE DBMS='TERADATA DB2 ORACLE NETEZZA ASTER GREENPLM HADOOP SAPHANA IMPALA HAWQ').

In SAS 9.4M4, the default value of the SQLGENERATION= system option became (NONE DBMS='TERADATA DB2 ORACLE NETEZZA ASTER GREENPLM HADOOP SAPHANA IMPALA HAWQ POSTGRES REDSHIFT SQLSVR VERTICA'). The corresponding LIBNAME option also supports these engines.

In SAS 9.4M7, the default value for the SQLGENERATION= system option became (NONE DBMS='TERADATA DB2 ORACLE NETEZZA ASTER GREENPLM HADOOP SAPHANA IMPALA HAWQ POSTGRES REDSHIFT SQLSVR VERTICA BIGQUERY SNOW YBRICK'). The corresponding LIBNAME option also supports these engines.

In the August 2021 update for SAS Viya 3.5, the default for SQLGENERATION was changed to (NONE DBMS='TERADATA DB2 ORACLE NETEZZA ASTER GREENPLM HADOOP SAPHANA IMPALA HAWQ POSTGRES REDSHIFT SQLSVR VERTICA SNOW').

In SAS 9.4M8, the default value for the SQLGENERATION= system option was updated to include MYSQL.

SAS/ACCESS Interface to Amazon Redshift

In the April 2016 release of SAS/ACCESS on SAS 9.4M3, support was added for the Amazon Redshift interface.

In SAS 9.4M4, support was added for these features or enhancements:

In SAS Viya 3.3, integration was added between SAS/ACCESS Interface to Amazon Redshift and SAS Viya. This support includes an associated data connector that enables you to load data to the CAS server.

In SAS Viya 3.4, the following changes or enhancements were made:

In SAS 9.4M6, support was added for these features:

In SAS 9.4M7, the default value for the INSERTBUFF= LIBNAME option is now 250.

In the April 2022 update to SAS/ACCESS for SAS 9.4M7 and SAS Viya 3.5, the USE_ODBC_CL= LIBNAME option is not supported.

In SAS 9.4M8, support was added for the SAS_REDSHIFT_UPDATE_WARNING= environment variable to facilitate working with NLS data that would otherwise trigger errors in SAS.

In SAS 9.4M9, the following changes and enhancements were added:

SAS/ACCESS Interface to Aster

In SAS 9.4, support was added for the BL_DATAFILE_PATH= data set option and the BL_MAPFILE= data set option.

In SAS 9.4M1, support was added for AIX and Solaris hosts for SPARC.

In SAS 9.4M2,support was added for bulk loading and bulk unloading. This support includes the BULKUNLOAD= LIBNAME option and BULKUNLOAD= data set option.

In SAS 9.4M3, support for these options was added:

In SAS Viya 3.4, support for the BL_DEFAULT_DIR= LIBNAME option was added.

In SAS 9.4M6, support for the CONOPTS= LIBNAME option was added.

Starting with SAS 9.4M8, SAS/ACCESS Interface to Aster is no longer available. If you have an instance of SAS/ACCESS Interface to Aster and plan to upgrade to SAS 9.4M8 or later, SAS recommends that you unconfigure and uninstall it. For more information, see Unconfiguring and Uninstalling Retired Products.

SAS/ACCESS Interface to DB2 under UNIX and PC Hosts

In SAS 9.4, support was added for the PROGRAM_NAME= LIBNAME option for DB2 monitoring.

In SAS 9.4M1, support for these options was added:

In SAS 9.4M2, the maximum length for column names is now 32 characters (rather than 30).

In SAS 9.4M3, support for these options was added:

In SAS 9.4M4, support for the SAS_DB2_TS_REDUCE_SCALE environment variable was added.

In SAS 9.4M5, support was added for these options:

In SAS Viya 3.3, integration was added between SAS/ACCESS Interface to DB2 under UNIX and PC Hosts and SAS Viya. This includes support for the DB2 data connector, which enables you to load data to the CAS server.

In SAS Viya 3.4, changes were made to the following options:

In SAS 9.4M6, the default value for the PRESERVE_COL_NAMES= and PRESERVE_TAB_NAMES= LIBNAME options is NO.

In SAS 9.4M7, the BL_METHOD= data set option now supports the values IMPORT and LOAD in addition to CLILOAD.

In the March 2021 update of SAS/ACCESS for SAS 9.4M7, syntax for the BL_OPTIONS= data set option now shows that commas are not required between multiple bulk-load option values.

In SAS 9.4M8, support was added for the PRESERVE_COMMENTS= LIBNAME option and DB2_SQL_COMMENT macro variable. These options enable you to pass comments down to your data source in a query.

In the August 2023 update for SAS/ACCESS on SAS 9.4M8, the behavior of DBCLIENT_MAX_BYTES= was updated to better handle graphic data types.

In SAS 9.4M9, the following changes and enhancements were made:

SAS/ACCESS Interface to DB2 under z/OS

In SAS 9.4M1, support for the ALLOWED_SQLCODES= LIBNAME option was added.

In SAS 9.4M2, these features are new or updated:

In SAS 9.4M3, support for these options was added:

In SAS 9.4M6, support was added for the ALLOW_SQLCODES= LIBNAME option.

SAS/ACCESS Interface to Google BigQuery

In the August 2019 release of SAS/ACCESS for SAS 9.4M6, support was added for the Google BigQuery interface.

In the November 2019 release of SAS 9.4M6 and SAS Viya 3.5, support was added for the ARRAY, GEOGRAPHY, NUMERIC, and RECORD data types.

In the April 2020 release of SAS/ACCESS for SAS 9.4M6 and SAS Viya 3.5, the following LIBNAME options were added to support OAuth authentication: CLIENT_ID=, CLIENT_SECRET=, and REFRESH_TOKEN=. The PROXY= LIBNAME option was added to support using a connection proxy. Support was also added for the DBCLIENT_MAX_BYTES= LIBNAME option.

Beginning in the May 2020 release of SAS/ACCESS for SAS 9.4M6 and SAS Viya 3.5, the SCHEMA= LIBNAME option is required to access Google BigQuery data. The PROJECT= LIBNAME option is also required.

In SAS 9.4M7, the following enhancements were made:

In the March 2021 update for SAS/ACCESS on SAS 9.4M7, a restriction was added for the CRED_PATH= option. The value of this option must be enclosed in single quotation marks ( ' ).

In the April 2021 update for SAS/ACCESS on SAS 9.4M7 and SAS Viya 3.5, the following updates were made:

In the January 2024 update of SAS/ACCESS for SAS 9.4M7 and in the March 2024 update of SAS/ACCESS for SAS 9.4M8 and SAS Viya 3.5, support was added for generating logging information for the Go layer for Google BigQuery. To do this, use the GO_ENABLE_LOGGING= LIBNAME and related options. For more information, see GO_ENABLE_LOGGING= LIBNAME Statement Option.

In the March 2024 update of SAS/ACCESS for SAS 9.4M7, SAS 9.4M8, and SAS Viya 3.5, support was added for the GOMEMLIMIT= environment variable. For more information, see Troubleshooting LIBNAME Connections: Set a GOMEMLIMIT= Value.

In the September 2024 update for SAS/ACCESS on SAS 9.4M7 and in the December 2024 update for SAS/ACCESS on SAS 9.4M8, support was added for the FETCH_NUMERIC_TYPE= LIBNAME and data set options. Use these options to control how NUMERIC data is read into SAS. To preserve more than 15 digits of precision, set FETCH_NUMERIC_TYPE=NUMERIC and use the DBSASTYPE= data set option to store values as CHAR values. For more information, see FETCH_NUMERIC_TYPE= LIBNAME Statement Option.

In the December 2024 update for SAS/ACCESS on SAS 9.4M8, support was added for the BIGNUMERIC data type. For more information, see Data Types and Conversions for Google BigQuery.

In the February 2025 update for SAS/ACCESS on SAS 9.4M8, support was added for the READ_MODE= LIBNAME and data set options. For more information, see READ_MODE= LIBNAME Statement Option.

In SAS 9.4M9, the following changes and enhancements were added:

In the December 2025 update on SAS 9.4M8, support was added for the following changes or features:

SAS/ACCESS Interface to Greenplum

In SAS 9.4, support was added for the BL_DATAFILE_EXISTS= data set option.

In SAS 9.4M2, support was added for these options:

In SAS 9.4M3, these features are new or enhanced:

In SAS 9.4M4, support was added for the READ_LOCK_TYPE= and UPDATE_LOCK_TYPE= LIBNAME options.

In SAS Viya 3.3, support was added for the Greenplum interface in SAS Viya.

In SAS Viya 3.4, the following changes or enhancements were made:

In SAS 9.4M6, support was added for the CONOPTS= LIBNAME option.

In SAS 9.4M9, the following changes and enhancements were made:

SAS/ACCESS Interface to Hadoop

In SAS 9.4, support was added for these changes and enhancements:

In SAS 9.4M2, support was added for these enhancements or changes:

In SAS 9.4M3, support was added for these features and changes:

In SAS 9.4M4, these features are new or enhanced:

In SAS Viya 3.2, integration was added between SAS/ACCESS Interface to Hadoop and SAS Viya. This includes support for a data connector. You can also transfer data in parallel if you have licensed SAS In-Database Technologies.

In SAS 9.4M5 , support was added for these features and changes:

In SAS Viya 3.4, support was added for these changes and enhancements:

SAS 9.4M6 includes these changes:

In SAS Viya 3.5, the TRANSCODE_FAIL= LIBNAME option is deprecated. Use the SUB_CHAR= LIBNAME option instead.

In SAS 9.4M7, support was added for the DRIVERCLASS= LIBNAME option.

In the June 2022 update for SAS/ACCESS on SAS 9.4M7, support was added for the SUB_CHAR= LIBNAME option and the SUB_CHAR= data set option.

In SAS 9.4M8, the following enhancements and changes were made:

In the November 2023 update to SAS 9.4M7 and SAS 9.4M8, a new environment variable was added to enable bulk loading to Cloudera Data Platform Private Cloud - Data Services.

In SAS 9.4M9, the following changes or enhancements were made:

SAS/ACCESS Interface to HAWQ

In SAS 9.4M3, support was added for the HAWQ interface.

In SAS 9.4M4, support was added for the READ_LOCK_TYPE= and UPDATE_LOCK_TYPE= LIBNAME options.

In SAS Viya 3.3, support was added for the HAWQ interface in SAS Viya.

In SAS Viya 3.4, support was added for these options:

In SAS Viya 3.5, support for the following options has changed:

Starting with SAS 9.4M8, SAS/ACCESS Interface to HAWQ is no longer available. If you have an existing installation of SAS/ACCESS Interface to HAWQ and plan to upgrade to SAS 9.4M8 or later, SAS recommends that you first unconfigure and uninstall SAS/ACCESS Interface to HAWQ. For more information, see Unconfiguring and Uninstalling Retired Products.

As an alternative to HAWQ, consider storing your data on Greenplum and accessing it with SAS/ACCESS Interface to Greenplum.

SAS/ACCESS Interface to Impala

In SAS 9.4M2, support was added for the Impala interface.

In SAS 9.4M2, support was added for these features:

In SAS 9.4M2, you can use an environment variable and these options for bulk loading:

In SAS 9.4M3, these features are new or enhanced:

SAS 9.4M5 supports these features:

In SAS Viya 3.3, integration was added between SAS/ACCESS Interface to Impala and SAS Viya. This integration includes a data connector to load data to the CAS server.

In SAS Viya 3.4, support was added for these options:

In SAS 9.4M6, support was added for the CONOPTS= LIBNAME= option.

In SAS Viya 3.5, support for the SCRATCH_DB= LIBNAME and data set option was added.

In the May 2020 update for SAS/ACCESS on SAS 9.4M6 and SAS Viya 3.5, the default value for the DBCLIENT_MAX_BYTES= LIBNAME option now matches the maximum number of bytes per single character of the SAS session encoding.

In SAS 9.4M8, the CONFIG= LIBNAME option and the CONFIG= data set option are deprecated. It is preferable to use the tracer tool to configure the appropriate environment variables. For more information, see Running the Hadoop Tracer Script.

The following changes and enhancements were made in SAS 9.4M9:

SAS/ACCESS Interface to Informix

In SAS 9.4M3, these options were added:

In SAS 9.4M9, the following changes and enhancements were made:

SAS/ACCESS Interface to JDBC

In SAS Viya 3.4, support was added for the JDBC interface.

In SAS 9.4M6, support was added for the JDBC interface.

In SAS Viya 3.5, the TRANSCODE_FAIL= LIBNAME option is deprecated. Use the SUB_CHAR= LIBNAME option instead.

In SAS 9.4M8, the following changes and enhancements were made:

In SAS 9.4M9, the following changes or enhancements were made:

SAS/ACCESS Interface to Microsoft SQL Server

In SAS 9.4M3, support was added for these features:

In SAS 9.4M4, these features are new or enhanced:

SAS 9.4M5 adds support for the DBNULLWHERE= LIBNAME option and the DBNULLWHERE= data set option.

In SAS Viya 3.3, integration was added between SAS/ACCESS Interface to Microsoft SQL Server and SAS Viya. This integration includes a data connector to load data to the CAS server.

In SAS Viya 3.4, the following changes and enhancements were made:

In SAS 9.4M7, support was added for connecting to and bulk loading to Azure Synapse Analytics when using a Microsoft Azure Data Lake Storage Gen 2 storage account. Connecting to Azure Synapse Analytics requires that you specify values for the AZUREAUTHCACHELOC= and AZURETENANTID= system options. Support for bulk loading includes these options:

BL_ACCOUNTNAME= LIBNAME option and data set option
BL_APPLICATIONID= LIBNAME option and data set option
BL_COMPRESS= LIBNAME option and data set option
BL_DEFAULT_DIR= LIBNAME option and data set option
BL_DELETE_DATAFILE= LIBNAME option and data set option
BL_DELIMITER= LIBNAME option and data set option
BL_DNSSUFFIX= LIBNAME option and data set option
BL_FILESYSTEM= LIBNAME option and data set option
BL_FOLDER= LIBNAME option and data set option
BL_IDENTITY= LIBNAME option and data set option
BL_LOG= LIBNAME option and data set option
BL_MAXERRORS= LIBNAME option and data set option
BL_NUM_DATAFILES= data set option
BL_OPTIONS= LIBNAME option and data set option
BL_SECRET= LIBNAME option and data set option
BL_TIMEOUT= LIBNAME option and data set option
BL_USE_ESCAPE= LIBNAME option and data set option
BL_USE_LOG= LIBNAME option and data set option
BULKLOAD= LIBNAME option and data set option

In SAS 9.4M8, support was added for the PRESERVE_COMMENTS= LIBNAME option and SQLSERVER_SQL_COMMENT macro variable. These options enable you to pass comments down to your data source in a query.

In the June 2023 update for SAS/ACCESS on SAS 9.4M8, support was added for the USE_SP_TABLES= LIBNAME option. For more information, see USE_SP_TABLES= LIBNAME Statement Option.

In the September 2024 update for SAS/ACCESS on SAS 9.4M8, a clarification was added for the USE_ODBC_CL= LIBNAME option when running on UNIX. For more information, see USE_ODBC_CL= LIBNAME Statement Option.

In SAS 9.4M9, the following changes and enhancements were made:

SAS/ACCESS Interface to MySQL

In SAS 9.4, support was added for bulk loading.

In SAS 9.4M3, these features are new or enhanced:

In SAS 9.4M4, support was added for these LIBNAME options:

In SAS Viya 3.3, support was added for the MySQL interface in SAS Viya.

In SAS Viya 3.4, the following changes and enhancements were made:

In SAS Viya 3.5, support was added for the JSON data type.

In SAS 9.4M7, the default value for the INSERTBUFF= LIBNAME option has changed from 0 to 1.

In the September 2022 update for SAS/ACCESS for SAS 9.4M7 and SAS Viya 3.5, a restriction was modified that concerns using the MySQL interface to access SingleStore (formerly MemSQL) data sources. To access SingleStore, specify UTF-8 as your session encoding.

In SAS 9.4M8, support was added for the following features and enhancements:

In SAS 9.4M9, the following changes and enhancements were made:

SAS/ACCESS Interface to Netezza

In SAS 9.4, support was added for the SYNONYMS= LIBNAME option.

In SAS 9.4M2, support was added for the following features:

In SAS 9.4M3, these options were added:

In SAS 9.4M4, support was added for the PRESERVE_USER= LIBNAME option. A corresponding environment variable, SAS_NETEZZA_PRESERVE_USER, was also added.

In the April 2016 release for SAS/ACCESS on SAS 9.4, support for SAS/ACCESS Interface to Netezza on the Solaris for x64 platform is new.

SAS 9.4M5 adds support for the BL_DEFAULT_DIR= data set option.

In SAS Viya 3.3, support was added for the Netezza interface in SAS Viya.

In SAS Viya 3.4, these changes or enhancements were made:

In SAS 9.4M6, support was added for the CONOPTS= LIBNAME option and the SUB_CHAR= LIBNAME option.

In SAS 9.4M9, support was removed for the Solaris platform.

SAS/ACCESS Interface to ODBC

In SAS 9.4, support was added for the DATETIME2= LIBNAME and data set options.

SAS 9.4M5 adds support for the DBNULLWHERE= LIBNAME option and the DBNULLWHERE= data set option.

In SAS Viya 3.3, integration was added between SAS/ACCESS Interface to ODBC and SAS Viya. This integration includes a data connector that enables you to load data to the CAS server.

In SAS Viya 3.4, the following changes or enhancements were made:

In SAS Viya 3.5, the following changes or enhancements were added:

In SAS 9.4M8, the following changes and enhancements were made:

In SAS 9.4M9, the following changes and enhancements were made:

SAS/ACCESS Interface to OLE DB

In SAS 9.4, support for the BOOL_VAL environment variable was added.

In SAS 9.4M3, these features have been added or enhanced:

In SAS 9.4M4, support was added for the CHAR_AS_NCHAR= LIBNAME option.

SAS/ACCESS Interface to Oracle

In SAS 9.4, support was added for the OR_IDENTITY_COLS= data set option.

In SAS 9.4M1, the following options were added or modified:

SAS 9.4M2 has these enhancements:

In SAS 9.4M3, these options were added:

In SAS 9.4M4, support for the BL_USE_PIPE= data set option was added.

SAS 9.4M5 adds support for these options:

In SAS Viya 3.3, integration was added between SAS/ACCESS Interface to Oracle and SAS Viya. This includes a data connector that enables you to load data to the CAS server.

Beginning in the April 2020 release of SAS/ACCESS for SAS 9.4M6 and SAS Viya 3.5, BL_SQLLDR_PATH= is no longer supported.

In SAS 9.4M8, support was added for these changes and enhancements:

In SAS 9.4M9, the following changes and enhancements were made:

SAS/ACCESS Interface to PostgreSQL

In SAS 9.4, support was added for the PostgreSQL interface.

In SAS 9.4M1, these features are new or modified:

In SAS 9.4M3, these features were added or enhanced:

In SAS 9.4M4, support for in-database processing of these Base SAS procedures was added: FREQ, MEANS, RANK, REPORT, SORT, SUMMARY, and TABULATE.

In SAS 9.4M5, the default value for the DBINDEX= LIBNAME option and data set option is NO.

In SAS Viya 3.3, integration was added between SAS/ACCESS Interface to PostgreSQL and SAS Viya. This includes a data connector that enables you to load data to the CAS server in SAS Viya.

In SAS Viya 3.4, the following changes or enhancements were made:

In SAS 9.4M6, support was added for the CONOPTS= LIBNAME option and the SUB_CHAR= LIBNAME option.

In SAS Viya 3.5, support was added for the following features and changes:

In the March 2021 update for SAS/ACCESS for SAS 9.4M7 and SAS Viya 3.5, a clarification was added to the BL_ESCAPE= data set option. For PostgreSQL, because BL_ESCAPE= is applicable only to CSV files, you must also set BL_FORMAT=CSV.

In the April 2022 update for SAS/ACCESS for SAS 9.4M7 and SAS Viya 3.5, the following changes have been made:

In the September 2022 update for SAS/ACCESS for SAS 9.4M7 and SAS Viya 3.5, a restriction was added for the SSLMODE= LIBNAME option. All values must be specified in lowercase for this option.

In SAS 9.4M8, the following enhancements and changes were made:

In the September 2023 update for SAS/ACCESS for SAS 9.4M8, information was added about managing memory with large amounts of data. For more information, see Managing Memory with Large Amounts of Data.

In SAS 9.4M9, the following changes and enhancements were made:

SAS/ACCESS Interface to SAP ASE

In SAS 9.4M3, these options were added:

In SAS 9.4M4, the name SAS/ACCESS Interface to Sybase changed to SAS/ACCESS Interface to SAP ASE to match the changed SAP product name. In the LIBNAME statement, the engine name is now sapase, although the previous engine name, sybase, is still supported.

In SAS Viya 3.4, support was added for the SAP ASE interface in SAS Viya.

In SAS 9.4M9, support was removed for the Solaris platform.

SAS/ACCESS Interface to SAP HANA

In SAS 9.4, support was added for the SAP HANA interface.

In SAS 9.4M2, the saphana LIBNAME engine name was added.

In SAS 9.4M3, support was added for the following features

In SAS 9.4M4, support for the READ_LOCK_TYPE= and UPDATE_LOCK_TYPE= LIBNAME options was added.

SAS 9.4M5 adds support for the DBNULLWHERE= LIBNAME option and the DBNULLWHERE= data set option.

In SAS Viya 3.3, integration was added between SAS/ACCESS Interface to SAP HANA and SAS Viya. This includes a data connector that enables you to load data to the CAS server.

In SAS 9.4M6, the following changes and enhancements were made:

In the November 2020 update for SAS/ACCESS on SAS 9.4M7, support was added for the DBSASLABEL= LIBNAME option and the DBMS value in the DBSASLABEL= data set option.

In the August 2023 update for SAS/ACCESS on SAS 9.4M8, support was added for the DBCLIENT_MAX_BYTES= LIBNAME option.

In SAS 9.4M9, support was removed for the Solaris platform.

SAS/ACCESS Interface to SAP IQ

In SAS 9.4M3, these options were added:

In SAS 9.4M4, the name SAS/ACCESS Interface to Sybase IQ changed to SAS/ACCESS Interface to SAP IQ to match the changed SAP product name. In the LIBNAME statement, the engine name is now sapiq, although the previous engine name, sybaseiq, is still supported.

In SAS 9.4M6, support was added for the CONOPTS= LIBNAME option.

In SAS 9.4M7, the output from PROC CONTENTS and PROC DATASETS now includes the SAP IQ client version and server version. The output for PROC DATASETS also includes the LIBNAME engine.

In SAS 9.4M8, support was added for the DBCLIENT_MAX_BYTES= LIBNAME option.

In SAS 9.4M9, support was removed for the Solaris platform.

SAS/ACCESS Interface to Snowflake

In the August 2019 release of SAS 9.4M6 and SAS Viya 3.4, support was added for the Snowflake interface.

In SAS Viya 3.5, support was added for the 64-bit Microsoft Windows platform.

In the May 2020 update of SAS/ACCESS for SAS 9.4M6 and SAS Viya 3.5, the following changes and enhancements were made:

In the July 2021 update for SAS 9.4M7, support was added for the DBMSTEMP= LIBNAME option. This option is not supported on SAS Viya 3.5.

In SAS 9.4M8, support for the BL_FORMAT_OPT= data set option was added.

In the March 2024 release of SAS/ACCESS on SAS 9.4M8, the default value for the AUTOCOMMIT= LIBNAME option was changed to YES.

In SAS 9.4M9, the following changes and enhancements were made:

In the August 2025 update for SAS 9.4M6 and later, support was added for RSA key-pairs as a method to authenticate to Snowflake databases when MFA is not feasible. For more information, see Authentication to Snowflake.

SAS/ACCESS Interface to Spark

In SAS 9.4M7, support was added for the Spark interface on SAS 9.4. Also, in this release, SAS/ACCESS Interface to Spark is no longer available on SAS Viya 3.4 or on SAS Viya 3.5.

In SAS 9.4M8, the following changes and enhancements were made:

In SAS 9.4M9, the following changes or enhancements were made:

SAS/ACCESS Interface to Teradata

SAS 9.4 includes these new features or enhancements:

In SAS 9.4M3, these features are new or enhanced:

In SAS 9.4M4, support has been added for single sign-on with Kerberos authentication.

In SAS Viya 3.3, integration was added between SAS/ACCESS Interface to Teradata and SAS Viya. This includes a data connector that enables you to load data onto the CAS server. You can move data in parallel if you also license SAS In-Database Technologies.

The SAS Viya 3.5 release includes the following changes or enhancements:

In SAS 9.4M8, support was added for the following changes and enhancements:

In a July 2023 update for SAS/ACCESS on SAS 9.4M8, an update was made to the list of options that must match for a join between tables that are accessed from separate LIBNAME statements. These statements must also match on the DATABASE= option. For more information, see Passing Joins to Teradata.

In the August 2024 update for SAS/ACCESS on SAS 9.4M8, there is a change in behavior for users on the AIX platform for these options: BL_DATAFILE=, FASTEXPORT=, and FASTLOAD=. Setting TPT=NO, FASTEXPORT=NO, or FASTLOAD=NO is no longer honored. The TPT API is always used to export data.

In the October 2024 update for SAS/ACCESS on SAS 9.4M7, there is a change in behavior for users on the AIX platform for these options: BL_DATAFILE=, FASTEXPORT=, and FASTLOAD=. Setting TPT=NO, FASTEXPORT=NO, or FASTLOAD=NO is no longer honored. The TPT API is always used to export data.

In SAS 9.4M9, the following changes and enhancements were made:

SAS/ACCESS Interface to Vertica

SAS 9.4 includes support for the Vertica interface.

In SAS 9.4M3, these options were added:

In SAS 9.4M4, support for in-database processing of these Base SAS procedures was added: FREQ, MEANS, RANK, REPORT, SORT, SUMMARY, and TABULATE.

In SAS Viya 3.4, support was added for the SAS Data Connector to Vertica. The data connector enables you to transfer large amounts of data between your Vertica database and the CAS server.

In SAS 9.4M6, the following changes and enhancements were made:

In the November 2024 update for SAS 9.4M8, the default value for the TRACE= option changed from NO to none (no default).

In SAS 9.4M9, the following changes and enhancements were made:

SAS/ACCESS Interface to Yellowbrick

Support for the Yellowbrick interface was added in SAS 9.4M7. This includes support for bulk loading, bulk unloading, and in-database processing of summary procedures, such as PROC MEANS.

In the April 2022 update for SAS/ACCESS for SAS 9.4M7 and SAS Viya 3.5, the following changes have been made:

In the September 2022 update for SAS/ACCESS for SAS 9.4M7 and SAS Viya 3.5, a restriction was added for the SSLMODE= LIBNAME option. All values must be specified in lowercase for this option.

In SAS 9.4M8, information was added about how to work with long character values in Yellowbrick.

In SAS 9.4M9, support was removed for the Solaris platform.

Documentation Enhancements

This document includes these new and enhanced items.

Last updated: February 3, 2026