Problem Note 55704: SAS® Studio 3.2 requires additional steps to work with SAS/ACCESS® Interface to ODBC and MySQL
In SAS Studio 3.2, the encoding to read and write text files is set to UTF-8 and cannot be changed. In order to use SAS/ACCESS Interface to ODBC with MySQL with an encoding of UTF-8, the following configuration steps are required:
- Along with the other environment variables for using ODBC, you must set EASYSOFT_UNICODE to YES.
- If SAS/ACCESS Interface to ODBC is installed on a UNIX system, complete these steps:
- Open the sasenv_local file, located in !SASROOT/bin.
- Add this command to the file: export EASYSOFT_UNICODE=YES
- You must add CHARSET=UTF8 in the MySQL DSN stanzas in the global odbc.ini file.
- To avoid socket-related errors when trying to use SAS/ACCESS Interface to ODBC to connect to MySQL, you might need to set the ODBCSYSINI environment variable to the directory containing the odbc.ini file.
- It might also be necessary to set the ODBCINI environment variable.
- To find the encoding for a MySQL database, you can use the unixODBC ISQL query tool and submit commands similar to the following:
show variables like 'character\_set\_%'
show create database <database>
Starting with SAS® Studio 3.3, the text encoding can be changed. These steps are still required if an encoding of UTF-8 is used.
Operating System and Release Information
SAS System | SAS Studio | Microsoft® Windows® for x64 | 3.2 | 3.3 | 9.4 TS1M2 | 9.4 TS1M2 |
Microsoft Windows 8 Enterprise 32-bit | 3.2 | 3.3 | 9.4 TS1M2 | 9.4 TS1M2 |
Microsoft Windows 8 Enterprise x64 | 3.2 | 3.3 | 9.4 TS1M2 | 9.4 TS1M2 |
Microsoft Windows 8 Pro 32-bit | 3.2 | 3.3 | 9.4 TS1M2 | 9.4 TS1M2 |
Microsoft Windows 8 Pro x64 | 3.2 | 3.3 | 9.4 TS1M2 | 9.4 TS1M2 |
Microsoft Windows 8.1 Enterprise 32-bit | 3.2 | 3.3 | 9.4 TS1M2 | 9.4 TS1M2 |
Microsoft Windows 8.1 Enterprise x64 | 3.2 | 3.3 | 9.4 TS1M2 | 9.4 TS1M2 |
Microsoft Windows 8.1 Pro | 3.2 | 3.3 | 9.4 TS1M2 | 9.4 TS1M2 |
Microsoft Windows 8.1 Pro 32-bit | 3.2 | 3.3 | 9.4 TS1M2 | 9.4 TS1M2 |
Microsoft Windows Server 2008 | 3.2 | 3.3 | 9.4 TS1M2 | 9.4 TS1M2 |
Microsoft Windows Server 2008 R2 | 3.2 | 3.3 | 9.4 TS1M2 | 9.4 TS1M2 |
Microsoft Windows Server 2008 for x64 | 3.2 | 3.3 | 9.4 TS1M2 | 9.4 TS1M2 |
Microsoft Windows Server 2012 Datacenter | 3.2 | 3.3 | 9.4 TS1M2 | 9.4 TS1M2 |
Microsoft Windows Server 2012 R2 Datacenter | 3.2 | 3.3 | 9.4 TS1M2 | 9.4 TS1M2 |
Microsoft Windows Server 2012 R2 Std | 3.2 | 3.3 | 9.4 TS1M2 | 9.4 TS1M2 |
Microsoft Windows Server 2012 Std | 3.2 | 3.3 | 9.4 TS1M2 | 9.4 TS1M2 |
Windows 7 Enterprise 32 bit | 3.2 | 3.3 | 9.4 TS1M2 | 9.4 TS1M2 |
Windows 7 Enterprise x64 | 3.2 | 3.3 | 9.4 TS1M2 | 9.4 TS1M2 |
Windows 7 Home Premium 32 bit | 3.2 | 3.3 | 9.4 TS1M2 | 9.4 TS1M2 |
Windows 7 Home Premium x64 | 3.2 | 3.3 | 9.4 TS1M2 | 9.4 TS1M2 |
Windows 7 Professional 32 bit | 3.2 | 3.3 | 9.4 TS1M2 | 9.4 TS1M2 |
Windows 7 Professional x64 | 3.2 | 3.3 | 9.4 TS1M2 | 9.4 TS1M2 |
Windows 7 Ultimate 32 bit | 3.2 | 3.3 | 9.4 TS1M2 | 9.4 TS1M2 |
Windows 7 Ultimate x64 | 3.2 | 3.3 | 9.4 TS1M2 | 9.4 TS1M2 |
64-bit Enabled AIX | 3.2 | 3.3 | 9.4 TS1M2 | 9.4 TS1M2 |
64-bit Enabled Solaris | 3.2 | 3.3 | 9.4 TS1M2 | 9.4 TS1M2 |
HP-UX IPF | 3.2 | 3.3 | 9.4 TS1M2 | 9.4 TS1M2 |
Linux for x64 | 3.2 | 3.3 | 9.4 TS1M2 | 9.4 TS1M2 |
Solaris for x64 | 3.2 | 3.3 | 9.4 TS1M2 | 9.4 TS1M2 |
*
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: | 2015-05-06 15:52:27 |
Date Created: | 2015-05-04 11:41:36 |