Supported Databases for Data Storage
SAS ODBC Data Sources
For information about SAS drivers (rebranded DataDirect drivers), see the Data Direct online documentation. This documentation is found in the ODBC folder in the installation directory for SAS Data Management Studio. Here is an example path:
C:\Program Files (x86)\SAS\ODBC\8.0\doc\userguide\help.htm
The version numbers available for each driver are listed in the beginning of the topic for that driver. You can find these topics in Part 2, Part 3, and Part 4 of the Data Direct documentation.
SAS Data Management Studio can use SAS ODBC 8.0 drivers to access data in the following databases:
Driver | Database Version |
---|---|
Apache Hadoop Hive | 1.2.x, 2.0.x, and 2.1.x |
Apache Hive ™ | Apache Hadoop Hive 0.10.x, 0.11.x, 0.12.x, 13.x, and 14.x |
Apache Hive | Cloudera’s Distribution Including Apache Hadoop: CDH 5.3, 5.4, 5.5, 5.6, 5.7, 5.8, 5.9, 5.10, 5.11, and 5.12 |
Apache Hive | Hortonworks Distribution for Apache Hadoop: HDP 2.3, 2.4, 2.5, and 2.6 |
Apache Hive | MapR Distribution for Apache Hadoop: MapR 5.0, 5.1, and 5.2 |
Amazon Redshift | Not applicable |
Btrieve® | Btrieve 6.15 |
Btrieve | Pervasive.SQL™ 7.0, 8.5, and 2000 |
Impala Wire Protocol | Cloudera Impala™ Server 1.0, 1.1, 1.2, 1.3, 1.4, 2.0, 2.1, 2.2, 2.3, 2.4, 2.5, and 2.6. If your ODBC Impala connection needs to use Kerberos authentication, then your Kerberos administrator should follow the instructions available at http://media.datadirect.com/download/docs/odbc/allodbc/help.html#page/odbc/kerberos-authentication.html#wwconnect_header. |
dBASE | Clipper™ |
dBASE | dBASE IV and V |
dBASE | FoxPro 2.5, 2.6, and 3.0 |
dBASE | FoxPro 6.0 (with 3.0 functionality only) |
dBASE | FoxPro 3.0 Database Containers (DBC) |
DB2® Wire Protocol | IBM® DB2 v9.1, v9.5, v9.7, and v9.8 for Linux®, UNIX, and Windows® |
DB2 Wire Protocol | IBM DB2 v10.1, 10.5, and 11.5 for Linux, UNIX, and Windows |
DB2 Wire Protocol | IBM DB2 Universal Database™ (UDB) v8.x for Linux, UNIX, and Windows |
DB2 Wire Protocol | IBM DB2 v9.1, v10, and v11 for z/OS |
DB2 Wire Protocol | IBM DB2 UDB v8.x for z/OS |
DB2 Wire Protocol | IBM DB2 DB2 i 7.1and 7.2 using DRDA and DB2 i 6.1 using DRDA |
DB2 Wire Protocol | IBM DB2 UDB V5R4 for iSeries® |
Greenplum Wire Protocol | Greenplum Database 3.3, 4.0, 4.1, 4.2, 4.3, 5, 5.1, 5.2, 5.3, 5.4, 5.5 and 6.0 |
Greenplum Wire Protocol | Pivotal HAWQ 1.1 and 1.2 |
IBM BigInsights | 4.2 and 4.3 |
Informix© (client) | Informix Dynamic Server 9.2, 9.3, 9.4, 10.0, 11.0, 11.5, and 11.7 |
Informix Wire Protocol | Informix Dynamic Server 9.2, 9.3, 9.4, 10.0, 11.0, 11.5, 11.7, and 12.1 |
MySQL Enterprise Edition | 8.0 |
MySQL™ Wire Protocol | MySQL 5.0x, 5.1, 5.5, and 5.6 |
Netezza ODBC Driver | 7.2.0.5. Netezza cannot be used to store a SAS repository. Also, note that the Netezza driver is not a Data Direct driver. It must be downloaded from the Netezza site. |
Oracle® (client) | Oracle 8i R3 (8.1.7) |
Oracle (client) | Oracle 9i R1 and R2 (9.0.1 and 9.2) |
Oracle (client) | Oracle 10g R1 and R2 (10.1 and 10.2) |
Oracle (client) | Oracle 11g R1 and R2 (11.1 and 11.2) |
Oracle (client) | Oracle 12c R1 (12.1) |
Oracle Wire Protocol | Oracle 8i R3 (8.1.7) |
Oracle Wire Protocol | Oracle 9i R1 and R2 (9.0.1 and 9.2) |
Oracle Wire Protocol | Oracle 10g R1 and R2 (10.1 and 10.2) |
Oracle Wire Protocol | Oracle 11g R1 and R2 (11.1 and11.2) |
Oracle Wire Protocol | Oracle 12c R1 (12.1) and 12c R2 (12.2) |
Oracle Wire Protocol | 18c R1 (18.1) and 18c R3 (18.3) |
Oracle Wire Protocol | 19c R1 (19.1) |
Pivotal HD Enterprise (PHD) | PHD 3.0 |
PostgreSQL® Wire Protocol | PostgreSQL 8.2, 8.3, 8.4, 9.0, 9.1, 9.2, 9.3, 9.4, 9.5, 9.6, 11, and 12 |
Progress OpenEdge Wire Protocol | Progress OpenEdge 10.1x, 10.2x, 11.0, 11.1, 11.2, 11.3, 11.4, 11.5, and 11.6 |
Salesforce | Salesforce (API Version 26). To use this driver, you must install a 32-bit version of Java. If you use the Oracle 8 JRE or JDK, download and install the Visual C++ 2010 (x86) redistributable from Microsoft. |
SQL Server Wire Protocol | Microsoft SQL Server 2005 |
SQL Server Wire Protocol | Microsoft SQL Server 2008 R1 and R2 |
SQL Server Wire Protocol | Microsoft SQL Server 2012 |
SQL Server Wire Protocol | Microsoft SQL Server 2014 |
SQL Server Wire Protocol | Microsoft SQL Server 2016, 2017, and 2019 |
SQL Server Wire Protocol | Windows Azure SQL Database v11.0 and 12.0 |
Sybase® Wire Protocol | Sybase Adaptive Server® 11.9 |
Sybase Wire Protocol | Sybase Adaptive Server Enterprise® 12.0, 12.5, 12.5x, 15.0, 15.5, 15.7, and 16.0 |
Sybase IQ | Sybase IQ 15.0, 15.1, 15.2, 15.3, 15.4, and 16.0 |
Teradata® | Teradata 12.0, 13.0, 13.1, 14.0, 14.1, 15.0, and 15.1 |
Teradata | Teradata V2R6.0, V2R6.1, and V2R6.2 |
Text | Text Files |
XML | XML Documents (tabular and hierarchical formatted) |
Other Data Sources
In addition to the data sources mentioned above, SAS Data Management Studio can access the following data sources:
Data Source | Supported Versions |
---|---|
SAS data sets |
SAS Data Management Studio 2.6 and above and SAS Data Management Server 2.6 and above use the SAS Threaded Kernel Table Services Driver for Base SAS 9.4. Accordingly, they can access any SAS version 8 data set or any SAS version 9 dataset. Prior versions of the client and server can access any SAS version 8 data set or any SAS version 9 dataset that was not created with the Extend Observation Counter turned on. See Adding SAS Data Set Connections. |
Databases (including SAP and Hadoop) managed by the SAS® Federation Server |
For information about the supported databases, see the documentation page for SAS Federation Server. |
SAP® |
The custom connection method that is described in Adding Custom SAP Connections uses the SAS/ACCESS Interface to R/3 software. Accordingly, this method requires SAP Kernel Release 4.6C or higher. The SAS/ACCESS Interface to R/3 software for Windows and UNIX requires the 64-bit SAP Unicode RFC library, Release 7.20 or higher, which is provided by SAP AG. Refer to SAP Note 413708 for the current version, download and installation instructions. SAP data can also be accessed with the SAS Federation Server. For information, see the documentation page for SAS Federation Server. |