DOCUMENTATION
Sign In

Get access to My SAS, trials, communities and more.

System Requirements
 

Data Source Requirements

Data Source Requirements

Your software order included SAS/ACCESS products to support your data sources. Data access requires additional customization of your Kubernetes deployment and in some cases also requires installation of other software.

Individual SAS product offerings might support a subset of these data sources. Refer to the lists of data sources that are supported by individual offerings. Then consult the list of requirements for the SAS/ACCESS product that supports your data source for additional system requirements that apply to your environment.

Supported Data Sources

SAS/ACCESS interface products are included with the SAS Viya platform to access external data sources. The following external data sources are supported by most offerings that run on the SAS Viya platform, including SAS Visual Analytics, SAS Viya, SAS Viya Advanced, and SAS Viya Enterprise:

  • Amazon Redshift
  • Google BigQuery
  • Greenplum
  • Hadoop with Hive
  • IBM Db2
  • IBM Netezza
  • Impala
  • IBM Informix
  • Data sources accessible with a JDBC driver
  • Microsoft SQL Server
  • MongoDB
  • MySQL
  • Data sources accessible with an ODBC driver
  • Oracle
  • PC files
  • PI System
  • PostgreSQL
  • Salesforce
  • SAP ASE
  • SAP HANA
  • SAP IQ
  • SAP R/3
  • SingleStore
  • Snowflake
  • Spark
  • Teradata
  • Vertica
  • Yellowbrick

SAS In-Database products are also available for multiple data sources.

Support for Data Storage in Amazon S3 and MinIO

The SAS Viya platform can access data that is stored in Amazon Simple Storage Service (S3) or in MinIO Enterprise Object Store. You can use the CASLIB statement to connect the CAS server with an S3 or MinIO instance. The FILENAME statement lets you connect the Compute Server with your S3 or MinIO data source. The Parquet LIBNAME statement enables you to connect a SAS Compute server with Parquet tables in Amazon S3 or in Google Cloud Storage.

Note: Parquet LIBNAME with MinIO is not supported at this time.

For the S3 procedure, FILENAME S3, a CAS S3 data source, and the CAS S3 action set, only AWS and MinIO are supported. The FILENAME S3 statement for the Compute server uses only the Amazon S3 REST APIs. EC2 Instance Metadata Service 1 and 2 are supported. When you deploy the SAS Viya platform cluster in Amazon EKS, the SAS Viya platform uses IMDS to obtain an IAM role that enables access to S3 resources.

SAS provides S3 support only for Amazon S3 and MinIO Enterprise Object Store. Third-party compatible providers that implement the public Amazon S3 API might work, but SAS has not validated these providers. As a result, SAS cannot provide direct technical support for other S3-compatible providers.

Before you can use the S3 procedure, an AWS key ID and secret are required. If you are using temporary credentials, a security token is also required. For more information, see the Amazon S3 documentation.

For more information, see Amazon S3 Data Source in SAS Cloud Analytic Services: User’s Guide.

Data Sources for SAS Anti-Money Laundering

SAS Anti-Money Laundering requires a database for its own external data store (known as the external database). The requirements for SAS Anti-Money Laundering external data sources are described in Additional Requirements for SAS Anti-Money Laundering.

Data Sources for SAS Micro Analytic Service

SAS Micro Analytic Service supports a subset of the data sources that the SAS Viya platform supports. For more information, see Data Sources Supported for Use with SAS Micro Analytic Service in SAS Micro Analytic Service: Programming and Administration Guide.

Data Sources for SAS Visual Investigator

SAS Visual Investigator supports a subset of the data sources that the SAS Viya platform supports. You can use the following data sources with SAS Visual Investigator:

  • IBM Db2
  • Microsoft Azure SQL Database
  • Microsoft Azure SQL Managed Instance
  • Microsoft SQL Server (2017 or later)
  • Microsoft SQL Server on Azure Virtual Machines
  • MySQL
  • Oracle
  • PostgreSQL
  • Teradata

General Requirements for SAS/ACCESS

Before you start the deployment, collect the third-party libraries and configuration files that are required for your data sources. Examples of these requirements include the following:

  • Third-party drivers
  • ODBC drivers
  • JDBC drivers
  • Hadoop configuration files

When you have collected these files, place them on storage that is accessible to your Kubernetes cluster. This storage could be a mount or a storage device with a persistent volume configured.

SAS recommends organizing your software in a consistent manner on your mount or storage device. Take note of the details for your specific storage solution, as well as the paths to the configuration files within it. You will need this information before you start the deployment.

Encryption Libraries

SAS uses the Iron Bank Red Hat Universal Base Image (UBI) as the source base image for all SAS Viya 4 containers. Starting with 2025.10, the base image is upgraded to UBI9.

The client software that is required for some data sources might have a dependency on operating-system encryption (TLS) libraries. Each time you upgrade your data source, SAS recommends that you verify that your client is compatible with the encryption libraries provided by the Iron Bank Red Hat UBI9 image. Find out more about the versions of libraries that are installed into the UBI9 base image in the Red Hat Ecosystem Catalog.

Password Encryption

SAS strongly recommends using the SCRAM-SHA-256 algorithm for password encryption. For some data sources, including PostgreSQL, recent versions use SCRAM-SHA-256 for password encryption by default. In environments where components are configured for MD5 password encryption, login failures can occur. Password encryption mismatches can also cause attempts to access data for processing with the CAS or Compute server to fail with the following error: Could not connect to the database.

In a Federal Information Processing Standards (FIPS) environment, MD5 password encryption is not supported. Using an MD5-encrypted password for a file system can result in the failures described previously or a permissions issue from PostgreSQL that resembles the following: ERROR: permission denied for table pg_authid. For more information about these errors, see Troubleshooting: "Could not connect to the database" Error Message.

If you must perform a password-encryption configuration change from MD5 to SCRAM-SHA-256, be aware that all SAS users must update their passwords to use the newer encryption standard.

Requirements for SAS/ACCESS Interface to Amazon Redshift

SAS/ACCESS Interface to Amazon Redshift includes SAS Data Connector to Amazon Redshift.

Amazon Redshift and Amazon Redshift Serverless are supported.

The required client software is included with your SAS Viya platform installation. Using a Data Source Name (DSN) to connect to Amazon Redshift requires post-installation configuration of your Kubernetes deployment.

Requirements for SAS/ACCESS Interface to DB2

SAS/ACCESS Interface to DB2 includes SAS Data Connector to DB2.

IBM Db2 Connect™ must also be licensed if you plan to connect to IBM Db2 databases that are running on AS/400, VSE, VM, MVS, and z/OS systems. The following DBMS products are supported:

  • IBM Db2 version 11.5 or later
  • IBM Integrated Analytics System (IIAS)
  • Client utilities for IBM Db2 version 11.5 or later

SAS recommends installing the latest FixPack on the client and server.

Requirements for SAS/ACCESS Interface to DuckDB

SAS/ACCESS Interface to DuckDB is available with 2025.07 and later.

SAS/ACCESS Interface to DuckDB supports DuckDB 1.2.0 and later. Amazon S3, Azure blob store, and Google Cloud Storage data sources are supported.

Required client software is included with your SAS Viya platform installation. No additional software is required.

Because DuckDB is an in-process query engine, it runs in Compute server sessions and uses pod memory resources rather than external memory. SAS recommends provisioning Compute server pods for DuckDB with additional RAM, CPU, and persistent storage resources. However, DuckDB is designed for efficiency and can operate effectively with minimal system resources. It uses all available resources for optimal performance.

DuckDB should work well with the SAS/ACCESS default resource settings: 2 GiB of RAM and 4 VCPUs (or 2 physical cores). No additional resources are required. However, if you plan to work with larger data sets or with complex queries, you might want to consider the environment recommendations from DuckDB. DuckDB is a vectorized query processing system and scales very well as more resources are allocated.

Requirements for SAS/ACCESS Interface to Google BigQuery

SAS/ACCESS Interface to Google BigQuery includes SAS Data Connector to Google BigQuery.

Required client software is included with your SAS Viya platform installation. No additional software is required.

Requirements for SAS/ACCESS Interface to Greenplum

SAS/ACCESS Interface to Greenplum includes SAS Data Connector to Greenplum.

SAS/ACCESS Interface to Greenplum supports Greenplum Database versions 6.5 or later, and the required client software is included with your SAS Viya platform deployment. Using a Data Source Name (DSN) to connect to Greenplum requires post-installation configuration of your Kubernetes deployment.

To use the gpfdist:// protocol for bulk loading, you must install and configure the Greenplum file distribution utility, gpfdist. This utility must be available on the host that stores the external tables. The gpfdist utility is part of the Greenplum Clients package for the platform where SAS is running. You can download it from VMware Tanzu Greenplum.

For more information about bulk-loading data into Greenplum using gpfdist, see Using Protocols to Access External Tables in SAS/ACCESS for Relational Databases: Reference.

Requirements for SAS/ACCESS Interface to Hadoop

SAS/ACCESS Interface to Hadoop includes SAS Data Connector for Hadoop. The requirements in this section also apply to the HADOOP procedure, the FILENAME: HADOOP access method, and SPD Engine in HDFS.

Apache Hive 1.1 or later is required.

SAS/ACCESS Interface to Hadoop supports the following Hadoop distributions:

  • Amazon EMR 5.x (version 5.13 or later), 6.x, or 7.x
  • Cloudera Data Platform (CDP) 7.1 or later (Private Cloud), CDP 7.2 or later (Public Cloud), or CDP 7.3 or later (Public/Private Cloud)

    Cloudera Data Platform (CDP) Private Cloud - Data Services is supported (for Hive).

  • Google Dataproc 2.0.45 and later
  • Microsoft Azure HDInsight 3.6, 4, and 5.0

Support for Google Dataproc and Microsoft Azure HDInsight 5.0 starts with release 2022.11 on the SAS Viya platform.

The SAS policy that applies to alternative releases or distributions of Hadoop is documented on the SAS Support website.

IMPORTANT Starting in 2025.03, SAS is replacing the CData JDBC driver for Apache Hive that was previously included with SAS/ACCESS Interface to Hadoop. The Simba Apache Hive JDBC Data Connector replaces the CData driver to enable Hive connections. Programmers must remove properties that are specific to CData from LIBNAME and CASLIB statements. For more information, see Troubleshooting Hadoop Connection Problems in SAS/ACCESS for Relational Databases: Reference

In order to access files in the Hadoop Distributed File System (HDFS), you must run the Hadoop Tracer Script in order to install required JAR files. The script has the following requirements:

  • The user who is running the script must have authorization to issue HDFS and Hive commands.
  • If your Hadoop deployment is secured with Kerberos, obtain a Kerberos ticket for the user before running the script.
  • Python and the strace Linux library must be installed on the Hadoop cluster. If necessary, install them from the package repositories for your Linux distribution.

    Python 2.6 or later is required.

Requirements for SAS/ACCESS Interface to Impala

SAS/ACCESS Interface to Impala includes SAS Data Connector to Impala.

SAS/ACCESS Interface to Impala supports Impala Server 3.2 or a later version.

SAS/ACCESS Interface to Impala is supported on Cloudera Data Platform (CDP) Public and Private Cloud.

Starting with 2025.03, SAS/ACCESS Interface to Impala includes ODBC Client software. Previously, the Cloudera Impala driver client was required. Obtaining and installing the client driver is no longer required in order to connect to an Impala server on a Cloudera cluster. However, because SAS/ACCESS to Impala now uses the Simba Impala driver client, some changes to configuration files might be required. For more information, see the Deployment Note titled SAS/ACCESS Interface to Impala: Before Deployment Commands.

In order to take advantage of SAS/ACCESS bulk loading functionality, you must run the Hadoop Tracer Script. The script installs required JAR files that enable the SAS Viya platform servers to access files in Hadoop. For more information, see Obtain and Run Hadoop Tracer Script in SAS Viya Platform: Deployment Guide.

Requirements for SAS In-Database Products

SAS In-Database products are included with multiple SAS product offerings. This category of products includes products that support distributed data sources and have distinct system requirements.

IMPORTANT To use SAS In-Database products, SAS Embedded Process must be installed. Work with your designated on-site SAS support personnel to ensure that your SAS Embedded Process order is delivered from a SAS Viya platform repository. Previously, the SAS Embedded Process was delivered from SAS Viya 3.5 repositories.

Requirements for Azure Synapse Analytics

Note: Prior to 2026.06, SAS Data Accelerator was named SAS In-Database Technologies for Azure Synapse Analytics.

SAS Data Accelerator supports Microsoft Azure Synapse Analytics.

Apache Spark 3.5 and SAS Embedded Process for Spark are required.

Starting with 2026.04, only the accelserver RPM file is eligible to be used for the SAS Embedded Process deployment. Previously, two different RPM files were eligible.

IMPORTANT Microsoft announced an end of support for Apache Spark 3.4 with Azure Synapse Runtime, effective March 31, 2026.

As a result of the change to Microsoft Azure Synapse Runtime, some additional requirements apply to your deployment:

  • You can no longer deploy the SAS Embedded Process from the sepcorespark RPM in Azure Synapse.
  • You must perform a one-time pre-installation task to download an additional object library and create a wheel file. Then you must install that wheel file when you install the sasindb wheel.
  • The SCOREACCEL procedure, the Model Publishing and Scoring action set, and the SAS Embedded Process for Spark action set are no longer supported for Azure Synapse.

    Use the ACCELERATOR procedure for in-database scoring and to stop and start the SAS Embedded Process instead.

  • When you deploy the accelserver RPM, you can also use the in-database DATA step, which was not supported under the sepcorespark RPM.

For more information about these changes, see Deployment and Administration for Azure Synapse Analytics in SAS In-Database Products: Deployment and Administration Guide.

Requirements for SAS In-Database Technologies for Cloudera Data Platform

SAS In-Database Technologies for Cloudera Data Platform requires SAS Embedded Process for Hadoop.

It supports the following distributions of Cloudera:

  • Cloudera CDP 7.1 Private Cloud
  • Cloudera CDP 7.2 Public Cloud
  • Cloudera CDP 7.3 (both Public Cloud and Private Cloud deployments are supported)

    Additional configuration is required. For more information, see Additional Configuration for Cloudera in the SAS In-Database Products Deployment Guide.

Execution against Hive tables requires Spark 2.4 or later.

Requirements for Databricks

Note: Prior to 2026.06, SAS Data Accelerator was named SAS In-Database Technologies for Databricks.

SAS Data Accelerator supports Databricks for Microsoft Azure. To use SAS Data Accelerator for Databricks, you deploy SAS Embedded Process for Spark. SAS Embedded Process imposes some additional requirements.

Databricks clusters that are configured to run in Shared Access Mode (also known as User Isolation Security Mode) are not supported. Use clusters that are configured for dedicated (single-user) mode instead.

An additional RPM file is available for a SAS Embedded Process for Spark deployment: the accelserver RPM file. The previous deployment for SAS Embedded Process for Hadoop, referred to as the sepcorehadp RPM file, is now deprecated. When you deploy the accelserver RPM, additional functionality is available. The newer SAS Embedded Process deployment has different requirements:

  • SAS Embedded Process for Spark deployed from the accelserver RPM:

    Databricks runtime (All-purpose compute): 14-17 (Apache Spark 3.5 and 4.0 are supported)

    This type of deployment requires additional commands in the initialization script. For more information, see Create an Initialization Script in SAS In-Database Products: Deployment and Administration Guide.

  • SAS Embedded Process for Hadooop deployed from the sepcorespark RPM:

    Databricks runtime (All-purpose compute): 12-13 (Apache Spark 3.3 and 3.4 are supported)

    Databricks announced an end of support for Databricks Runtime 13.3 LTS as of August 22, 2026. SAS customers are encouraged to advance to a more-recent version of Databricks, which requires deployment of the accelserver RPM. The sepcorespark RPM does not support Databricks versions later than Databricks 13.

For more information about SAS Data Accelerator, see SAS In-Database Products: Deployment and Administration Guide.

Requirements for SAS In-Database Technologies for Hadoop Cloud Services

SAS In-Database Technologies for Hadoop Cloud Services supports Amazon EMR 7.x and later.

Note: Amazon EMR 5.x and 6.x are no longer supported. Microsoft Azure HDInsight is no longer supported.

You can publish scoring models to a table in Hive. Amazon EMR allows optional external connections to Hive through a JDBC connection.

Parallel data transfer activities with the Hadoop data connector for Amazon EMR require the SAS Viya platform to be deployed in AWS. Amazon EMR can be deployed in a separate cluster, but routing must be configured to enable SAS Viya platform components to connect to Amazon EMR.

Requirements for Teradata

Note: Prior to 2026.08, SAS Data Accelerator was named SAS In-Database Technologies for Teradata. The deployment of SAS Embedded Process for Teradata has not changed.

SAS Data Accelerator supports the following products:

  • Teradata Vantage Advanced SQL Engine version 17.20, or 20.0 or later
  • Teradata CLIv2 client libraries, TTU 17.20 or later within TTU 17, or TTU 20.xx or later within TTU 20 for Linux (64-bit libraries)

SAS Data Accelerator also supports Teradata Vantage on the following cloud platforms:

  • Amazon Web Services
  • Google Cloud Platform
  • Microsoft Azure
  • VMware

Requirements for SAS/ACCESS Interface to Informix

SAS/ACCESS Interface includes SAS Data Connector to Informix.

SAS/ACCESS Interface to Informix uses an ODBC connection. The required ODBC driver is included and deployed automatically.

The following products are also required:

  • IBM Informix Client SDK 4.10FC4 or later
  • IBM Informix Server version 12.10 or later

In order to support bulk loading and bulk unloading, a database access utility (DBACCESS) is required. The Informix DBACCESS utility must be running on Red Hat Enterprise Linux 7.9 or later.

Enable the utility by copying two libraries into the SDK installation library path: 

cp /lib64/libncurses.so.5  /Informix-SDK-installation-directory/lib

cp /lib64/libtinfo.so.5  /Informix-SDK-installation-directory/lib

ls -l /Informix-SDK-installation-directory/lib

The two libraries should be available to the SAS programming runtime environment (the sas-programming-environment pod). You can enable the sas-programming-environment pod to access them by configuring a soft link for each library and including a volume mount in the soft link path.

The Informix bulk-load DBACCESS utility requires authenticated UNIX credentials within the sas-programming-environment pod. The credentials must consist of a user name and POSIX attributes (UID and GID). To provide these credentials, you must configure SSSD for compute servers. Instructions are provided in the README file, $deploy/sas-bases/examples/kerberos/sssd/README.md (for Markdown format) or $deploy/sas-bases/docs/configuration_settings_for_compute_server.htm (for HTML). For more information, see Use Kerberos Connections to Connect to the CAS Server in SAS Viya Platform: Deployment Guide.

By default, the identities service does not use the required POSIX attributes provided by an external LDAP server. For information about how to configure the identities service to use these attributes, see How to Configure the sas.identities Settings in SAS Viya Platform: Identity Management and Scenario: POSIX Attributes in LDAP, Using a Shared File System in SAS Viya Platform: Identity Management.

When authentication is not configured correctly, you might see an error like the following: 25590: Authentication error.

Requirements for SAS/ACCESS Interface to JDBC

SAS/ACCESS Interface to JDBC includes SAS Data Connector to JDBC. SAS/ACCESS Interface to JDBC enables access to relational databases by means of SQL and the Java Database Connectivity (JDBC) API.

A JDBC driver is required for the data source from which you want to access data. JDBC drivers are available from DBMS vendors and other third-party JDBC driver developers.

Requirements for SAS/ACCESS Interface to Microsoft SQL Server

SAS/ACCESS Interface to Microsoft SQL Server includes SAS Data Connector to Microsoft SQL Server.

SAS/ACCESS Interface to Microsoft SQL Server supports the following products:

  • Amazon RDS Microsoft SQL Server (Microsoft SQL Server 2017 or later)
  • Google Cloud Platform Cloud SQL for SQL Server version 2017 or later
  • Microsoft SQL Server 2017 or later
  • Microsoft Azure SQL Database
  • Microsoft Azure SQL Database Managed Instance
  • Microsoft Azure SQL Server Big Data Clusters
  • Microsoft Azure Synapse
  • Microsoft Fabric Data Warehouse
  • Microsoft Fabric Lakehouse

Required client software is included with your SAS Viya platform installation. Using a Data Source Name (DSN) to connect requires some post-installation configuration of your Kubernetes deployment.

A DataDirect ODBC driver that is included with SAS/ACCESS to Microsoft SQL Server enables you to use a Microsoft SQL Server data source with SAS Micro Analytic Service. SAS/ACCESS Interface to Microsoft SQL Server has been tested and certified against DataDirect Technologies Connect ODBC and DataDirect SequeLink ODBC products.

As a best practice, set the EnableScrollableCursors ODBC driver option to 3.

Support for Microsoft Fabric Data Warehouse and Microsoft Fabric Lakehouse was added in 2025.06. Both require Microsoft Entra ID for authentication.

Requirements for SAS/ACCESS Interface to MongoDB

SAS/ACCESS Interface to MongoDB includes SAS Data Connector to MongoDB.

SAS/ACCESS Interface to MongoDB requires the MongoDB C Driver version 1.17 or later (“libmongoc,” the official client library for C applications). You can obtain the latest MongoDB C driver from the following website: http://mongoc.org/.

SAS/ACCESS Interface to MongoDB supports the following databases:

  • MongoDB Server 6.0 or later and Client 1.23 or later
  • MongoDB Atlas tiers M10 and higher

Starting with 2024.02, SAS no longer supports versions of MongoDB that require OpenSSL 1.0.2 because the required libraries are no longer supported by the vendor. Verify that your version of MongoDB supports a version of OpenSSL that is later than 1.0.2.

Requirements for SAS/ACCESS Interface to MySQL

SAS/ACCESS Interface to MySQL includes SAS Data Connector to MySQL.

SAS/ACCESS Interface to MySQL requires MySQL Client version 5.7 or later.

The following DBMS products are supported:

  • Amazon Aurora (MySQL engine version 5.7 or later)
  • Amazon RDS MariaDB (engine version 10.1 or later)
  • Amazon RDS MySQL (engine version 5.7 or later)
  • Azure Database for MySQL (engine version 5.7 or later)
  • Google Cloud SQL for MySQL (engine version 5.7 or later)
  • MySQL Server version 5.7 or later
  • MariaDB 10.1 or later
  • Oracle MySQL Database

SAS/ACCESS Interface to MySQL requires the MySQL C API client (libmysqlclient). The MySQL C API client must be accessible from a persistent volume, and the full path to the library must be set using the MYSQL variable: MYSQL=$PATH_TO_MYSQL_LIBS. Before you use SAS/ACCESS Interface to MySQL, verify that the location of the MySQL client library file has been appended to the LD_LIBRARY_PATH system variable.

Note: MySQL client libraries might have additional requirements, such as OpenSSL libraries. Check the MySQL documentation for more information about setting up these libraries.

For information about encryption (TLS) libraries that are compatible with the SAS Viya platform, see Encryption Libraries.

The ability to access a SingleStore instance using SAS/ACCESS Interface to MySQL has been deprecated. SAS recommends that you use SAS/ACCESS Interface to SingleStore, which is included with your SAS software order.

Requirements for SAS/ACCESS Interface to Netezza

SAS/ACCESS Interface to Netezza includes SAS Data Connector to Netezza.

SAS/ACCESS Interface to Netezza requires the IBM Netezza ODBC driver from IBM. To obtain the appropriate IBM Netezza ODBC driver, contact IBM Technical Support at (877) 426-6006 or visit the IBM Fix Central website: http://www.ibm.com/support/fixcentral.

SAS/ACCESS Interface to Netezza supports the following DBMS products:

  • IBM Netezza 7.2.1 or later
  • IBM Netezza Performance Server 11.2.0.0 and 11.2.1.x

Requirements for SAS/ACCESS Interface to ODBC

SAS/ACCESS Interface to ODBC includes SAS Data Connector to ODBC. SAS/ACCESS Interface to ODBC enables access to multiple data source types by means of a generic ODBC driver.

Before you can use the SAS Viya platform with ODBC, an ODBC driver is required for the data source from which you want to access data. ODBC drivers are often available from DBMS vendors and other third-party ODBC driver developers. Your ODBC driver must comply with the ODBC 3.5 (or later) specification.

Note: The ODBC driver that you select might require additional DBMS software in order to enable network access.

Requirements for SAS/ACCESS Interface to Oracle

SAS/ACCESS Interface to Oracle (on SAS Viya platform) includes SAS Data Connector to Oracle.

SAS/ACCESS Interface to Oracle requires the Oracle client 19c or later (64-bit libraries). Starting in 2024.05, the required client is included in the deployment.

The following Oracle instances are supported:

  • Amazon RDS Oracle 19c or later
  • Oracle Cloud Platform 19c or later
  • Oracle Database 19c or later
  • Oracle Autonomous Database

Requirements for SAS/ACCESS Interface to PC Files

SAS/ACCESS Interface to PC Files includes SAS Data Connector to PC Files.

SAS/ACCESS Interface to PC Files enables access to the following file formats:

  • .jmp
  • .spss
  • .stata
  • .xlsx or .xls

Additional Microsoft file formats can be accessed via the PCFILES LIBNAME engine, which is included with SAS/ACCESS Interface to PC Files.

No additional software is required.

Requirements for SAS/ACCESS Interface to the PI System

SAS/ACCESS Interface to the PI System uses the PI System Web API, which is HTTPS-based and RESTful. No PI System client software is required to be installed on the nodes where SAS is running.

However, the PI System Web API (PI Web API 2019 or later) must be installed and activated on the host machine through which the user connects (that is, the PI System server).

Requirements for SAS/ACCESS Interface to PostgreSQL

SAS/ACCESS Interface to PostgreSQL (on SAS Viya platform) includes SAS Data Connector to PostgreSQL.

SAS/ACCESS Interface to PostgreSQL supports all the following:

  • Amazon Aurora PostgreSQL 12.x or later
  • Amazon RDS PostgreSQL 12.x or later
  • Azure Database for PostgreSQL 12.x or later
  • CockroachDB 21.1.5 or later

    Bulk load and bulk unload are not supported at this time.

  • EnterpriseDB PostgreSQL 12.x or later
  • Google Cloud Platform Cloud SQL for PostgreSQL 12.x or later
  • PostgreSQL Database 12.x or later
Note: Amazon Aurora PostgreSQL, Amazon RDS PostgreSQL, Azure Database for PostgreSQL, and Google Cloud Platform Cloud SQL for PostgreSQL are not supported for use with SAS Anti-Money Laundering at this time.

Required client software is included with your SAS Viya platform installation. Using a Data Source Name (DSN) to connect requires some post-installation configuration of your Kubernetes deployment.

An optional requirement supports PostgreSQL LIBNAME connections if you intend to run PROC COPY in the PostgreSQL DBMS. For more information, see Required PostgreSQL Extensions.

SAS recommends the SCRAM-SHA-256 algorithm for database password encryption. With older versions of PostgreSQL, MD5 encryption algorithms might be in use, and the mismatch can cause login and permissions errors. For more information, see Troubleshooting: "Could not connect to the database" Error Message.

Requirements for SAS/ACCESS Interface to Salesforce

SAS/ACCESS Interface to Salesforce includes SAS Data Connector to Salesforce.

SAS/ACCESS Interface to Salesforce requires a Salesforce user account that has API access enabled. SAS/ACCESS Interface to Salesforce supports Salesforce API access, version 46.0 or later.

Requirements for SAS/ACCESS Interface to SAP ASE

SAS/ACCESS Interface to SAP ASE requires SAP ASE (formerly Sybase) Open Client SDK, Release 15.7 or later (64-bit libraries).

The database administrator must install two SAP ASE (Sybase) stored procedures on the target SAP server. These files are available in a compressed TGZ archive for download from the SAS Support site at https://support.sas.com/downloads/package.htm?pid=2458.

Note: For compatibility with version 16 of the SAP ASE Open Client SDK, use the SAP ASE 15.x stored procedures:
  • sas-spdf_15.txt
  • sassp2df_15.txt

Requirements for SAS/ACCESS Interface to SAP HANA

SAS/ACCESS Interface to SAP HANA includes SAS Data Connector to SAP HANA.

SAS/ACCESS Interface to SAP HANA supports SAP HANA SPS 11 Server or a later version and requires SAP HANA ODBC Client (64-bit) for SPS 11 or later.

Requirements for SAS/ACCESS Interface to SAP IQ

SAS/ACCESS Interface to SAP IQ includes SAS Data Connector to SAP IQ. The SAS/ACCESS LIBNAME engine for SAP IQ supports bulk loading.

The following components are required:

  • SAP IQ Network Client version 16.1 or later
  • SAP IQ Database version 16.0 or later

Requirements for SAS/ACCESS Interface to R/3

SAS/ACCESS Interface to SAP R/3 supports SAP NetWeaver 7.0 (Application Server ABAP) or later and requires the 64-bit SAP NetWeaver RFC Library, Release 7.20 or later, which is provided by SAP AG.

Requirements for SAS/ACCESS Interface to SingleStore

SAS/ACCESS Interface to SingleStore includes SAS Standard Data Connector to SingleStore. This data connector provides the standard ability to connect the CAS server with your SingleStore database.

SAS/ACCESS Interface to SingleStore supports SingleStoreDB 8.1 or later.

The SingleStore LIBNAME engine supports single sign-on to Microsoft Entra ID (formerly Azure Active Directory). For more information, see SAS/ACCESS Interface to SingleStore in SAS/ACCESS for Relational Databases: Reference

An additional data connector for SingleStore is available if you purchase SAS SpeedyStore, a separately licensed product. For more information, see Two Data Connectors: When to Use SingleStore Standard and When to Use SAS SpeedyStore in SAS Cloud Analytic Services: User’s Guide. The SAS SpeedyStore data connector also provides parallel data transfer and integrated, in-database features in addition to the standard features.

Note: The product known as SAS with SingleStore has been renamed to SAS® SpeedyStore.

Requirements for SAS/ACCESS Interface to Snowflake

SAS/ACCESS Interface to Snowflake includes SAS Data Connector to Snowflake. The required client software is also included with your SAS Viya platform installation.

Using a Data Source Name (DSN) to connect to Snowflake requires post-installation configuration of your Kubernetes deployment.

Requirements for SAS/ACCESS Interface to Spark

SAS/ACCESS Interface to Spark includes SAS Data Connector to Spark.

Spark SQL 3.1 or later is required.

SAS/ACCESS Interface to Spark supports the following data sources:

  • Databricks on Google Cloud 10.4 LTS or later
  • Databricks on Amazon Web Services (AWS) 10.4 LTS or later
  • Microsoft Azure Databricks 10.4 Long Term Support (LTS) or later
  • Microsoft Azure HDInsight 5.0 (support starts with Spark 3.1 and SAS Viya platform 2022.11)

SAS/ACCESS Interface to Spark redistributes JDBC drivers in order to connect to additional data sources. Starting in 2025.03, SAS has replaced the CData JDBC drivers that were previously included. The following drivers are now included with SAS/ACCESS Interface to Spark:

  • Simba Databricks JDBC Data Connector
    IMPORTANT The Simba Databricks JDBC Connector requires additional configuration by an administrator. For more information, see Fetch Error for Simba Databricks in SAS Viya Platform: Deployment Guide.
  • Simba Apache Spark Data Connector

To avoid errors using either of these drivers, programmers must remove properties that are specific to CData from LIBNAME and CASLIB statements. For more information, see Troubleshooting Spark Connection Problems in SAS/ACCESS for Relational Databases: Reference.

SAS/ACCESS Interface to Spark supports single sign-on to Databricks in Microsoft Azure. Microsoft Entra ID (Azure Active Directory) must be configured as an OIDC provider. For more information, see Scenario: OIDC with Microsoft Entra ID in SAS Viya Platform: Authentication.

Requirements for SAS/ACCESS Interface to Teradata

SAS/ACCESS Interface to Teradata includes SAS Data Connector to to Teradata.

SAS recommends TTU 17.20 or 20.00 for use with Teradata Database 17.00 or later.

Starting in 2025.03, SAS/ACCESS Interface to Teradata includes the required Teradata client libraries. If you have the required client (CLIv2) from a previous SAS/ACCESS deployment, updating to 2025.03 preserves your Teradata client. Teradata Wallet is not included with the client that SAS distributes; however, it is supported if you want to install it.

SAS/ACCESS Interface to Teradata also supports the following platforms:

  • Teradata VantageCloud Lake
  • Teradata Vantage on Amazon Web Services
  • Teradata Vantage on Google Cloud Platform
  • Teradata Vantage on Microsoft Azure

SAS/ACCESS Interface to Teradata supports TLS 1.2 with Teradata Database 17.10 and later. To support TLS, you must use TTU 17.10, 17.20, or 20.00. You can then encrypt data that is transferred between Teradata and the SAS Viya platform. Some additional configuration is required. For more information, see Configure TLS for SAS/ACCESS Connection to Teradata in SAS Viya Platform Encryption: Data in Motion.

Requirements for SAS/ACCESS Interface to Vertica

SAS/ACCESS Interface to Vertica includes SAS Data Connector to Vertica.

SAS/ACCESS Interface to Vertica supports Vertica Analytic Database version 9.1 or later.

SAS/ACCESS Interface to Vertica includes the required Vertica ODBC Client software. Installing the client driver is not required.

Requirements for SAS/ACCESS Interface to Yellowbrick

SAS/ACCESS Interface to Yellowbrick includes the required PostgreSQL ODBC driver.

Yellowbrick Database version 4.0.0-23452 or later is supported.

Last updated: September 30, 2026