-->No additional software needs to be installed on the SQL Server machine. Connect to SQL Server from Linux and Unix. The Easysoft ODBC-SQL Server Driver. Microsoft ODBC Driver 11 for SQL Server is a single dynamic-link library (DLL) containing run-time support for applications using native-code APIs to connect to Microsoft SQL Server 2005, 2008, 2008 R2, SQL Server 2012, SQL Server 2014 and Windows Azure SQL Database. Microsoft ODBC Driver 11 for SQL Server should be used to create new applications or enhance existing applications that need to take advantage of new SQL Server 2012 features.
This article contains instructions to install the unixODBC Driver Manager for use with all the versions of Microsoft ODBC Driver for SQL Server on Linux and macOS.
Important
Delete any driver manager packages installed on your computer before you install the unixODBC Driver Manager. Installing the unixODBC Driver Manager could cause a failure of an existing Driver Manager.
Installing the Driver Manager for Microsoft ODBC Driver 13, 13.1, and 17
The driver manager dependency is resolved automatically by the package management system when you install the Microsoft ODBC Driver 13, 13.1, or 17 for SQL Server on Linux or macOS by following the instructions in Installing the Microsoft ODBC Driver for SQL Server on Linux or macOS.
Installing the Driver Manager for Microsoft ODBC Driver 11 for SQL Server
(SUSE and Red Hat Linux only.)
Using the Installation Script
Important
These instructions refer to msodbcsql-11.0.2270.0.tar.gz, which is the installation file for Red Hat Linux. If you are installing the Preview for SUSE Linux, the file name is msodbcsql-11.0.2260.0.tar.gz.
To install the driver manager:
Make sure that you have root permission.
Go to the directory where the MicrosoftSQL Server ODBC Driver download placed the file called
msodbcsql-11.0.2270.0.tar.gz. Make sure that you have the *.tar.gz file that matches your version of Linux. To extract the files, execute the following command: tar xvzf msodbcsql-11.0.2270.0.tar.gz.Change to the
msodbcsql-11.0.2270.0directory and there you should see a file calledbuild_dm.sh. You can runbuild_dm.shto install the unixODBC Driver Manager.To see a list of the available options, execute the following command: ./build_dm.sh --help.
When you are ready to install, and if your computer can access an external site via FTP, execute the following command: ./build_dm.sh.
If your computer cannot access an external site via FTP, get unixODBC-2.3.0.tar.gz. You can get unixODBC-2.3.0.tar.gz from http://www.unixodbc.org. Click the Download link on the left side of the page to go to the download page. Then click the appropriate link to download unixODBC-2.3.0 (not unixODBC-2.3.1). unixODBC-2.3.1 is not supported with this release of the Microsoft ODBC Driver 11 for SQL Server. Execute the following command to begin the unixODBC Driver Manager installation: ./build_dm.sh --download-url=file://unixODBC-2.3.0.tar.gz.
Type YES to proceed with unpacking the files. This part of the process can take up to five minutes to complete.
After the script stops running, follow the instructions on the screen to install the unixODBC Driver Manager.
You are now ready to install the driver. For more information, see Installing the Microsoft ODBC Driver for SQL Server on Linux and macOS. Specs microsoft word for mac.
Manual Installation
If the installation script is unable to complete, configure and build the proper driver manager yourself.
Remove any older installed version of unixODBC (for example, unixODBC 2.2.11). On Red Hat Enterprise Linux 5 or 6, execute the following command: yum remove unixODBC. On SUSE Linux Enterprise, zypper remove unixODBC.
Go to http://www.unixodbc.org. Click the Download link on the left side of the page to go to the download page. Then click the appropriate link to save the file unixODBC-2.3.0.tar.gz to your computer. UnixODBC-2.3.1 is not supported with this release of the Microsoft ODBC Driver 11 for SQL Server.
On your Linux computer, execute the command: tar xvzf unixODBC-2.3.0.tar.gz.
Change to the unixODBC-2.3.0 directory.
At a command prompt, execute the command: CPPFLAGS='-DSIZEOF_LONG_INT=8'.
At a command prompt, execute the command: export CPPFLAGS.
At a command prompt, execute the command: './configure --prefix=/usr --libdir=/usr/lib64 --sysconfdir=/etc --enable-gui=no --enable-drivers=no --enable-iconv --with-iconv-char-enc=UTF8 --with-iconv-ucode-enc=UTF16LE'.
At a command prompt (logged in as root), execute the command: make.
At a command prompt (logged in as root), execute the command: make install.
You are now ready to install the driver. For more information, see Installing the Microsoft ODBC Driver for SQL Server on Linux and macOS.
See Also
-->This article contains a list of known issues with the Microsoft ODBC Driver 13, 13.1, and 17 for SQL Server on Linux and macOS.
Additional issues will be posted on the Microsoft ODBC driver team blog.
Due to system library limitations, Alpine Linux supports fewer character encodings and locales. For example, en_US.UTF-8 is not available. See musl libc - functional differences from glibc for more information.
Windows, Linux, and macOS convert characters from the Private Use Area (PUA) or End User-Defined Characters (EUDC) differently. Conversions performed on the server within Transact-SQL use the Windows conversion library. Conversions in the driver use the Windows, Linux, or macOS conversion libraries. Each library may produce different results when performing these conversions. For more information, see End-User-Defined and Private Use Area Characters.
If the client encoding is UTF-8, the driver manager does not always correctly convert from UTF-8 to UTF-16. Currently, data corruption occurs when one or more characters in the string are not valid UTF-8 characters. ASCII characters are mapped correctly. The driver manager attempts this conversion when calling the SQLCHAR versions of the ODBC API (for example, SQLDriverConnectA). The driver manager will not attempt this conversion when calling the SQLWCHAR versions of the ODBC API (for example, SQLDriverConnectW).
The ColumnSize parameter of SQLBindParameter refers to the number of characters in the SQL type, while BufferLength is the number of bytes in the application's buffer. However, if the SQL data type is
varchar(n)orchar(n), the application binds the parameter as SQL_C_CHAR or SQL_C_VARCHAR, and the character encoding of the client is UTF-8, you may get a 'String data, right truncation' error from the driver even if the value of ColumnSize is aligned with the size of the data type on the server. This error occurs since conversions between character encodings may change the length of the data. For example, a right apostrophe character (U+2019) is encoded in CP-1252 as the single byte 0x92, but in UTF-8 as the 3-byte sequence 0xe2 0x80 0x99.
For example, if your encoding is UTF-8 and you specify 1 for both BufferLength and ColumnSize in SQLBindParameter for an out-parameter, and then attempt to retrieve the preceding character stored in a char(1) column on the server (using CP-1252), the driver attempts to convert it to the 3-byte UTF-8 encoding, but cannot fit the result into a 1-byte buffer. In the other direction, it compares ColumnSize with the BufferLength in SQLBindParameter before doing the conversion between the different code pages on the client and server. Because a ColumnSize of 1 is less than a BufferLength of (for example) 3, the driver generates an error. To avoid this error, ensure that the length of the data after conversion fits into the specified buffer or column. Note that ColumnSize cannot be greater than 8000 for the varchar(n) type.
See Also
Programming Guidelines
Release Notes
- Author: admin
- Category: Category
No additional software needs to be installed on the SQL Server machine. Connect to SQL Server from Linux and Unix. The Easysoft ODBC-SQL Server Driver. Microsoft ODBC Driver 11 for SQL Server is a single dynamic-link library (DLL) containing run-time support for applications using native-code APIs to connect to Microsoft SQL Server 2005, 2008, 2008 R2, SQL Server 2012, SQL Server 2014 and Windows Azure SQL Database. Microsoft ODBC Driver 11 for SQL Server should be used to create new applications or enhance existing applications that need to take advantage of new SQL Server 2012 features.
This article contains instructions to install the unixODBC Driver Manager for use with all the versions of Microsoft ODBC Driver for SQL Server on Linux and macOS.
Important
Delete any driver manager packages installed on your computer before you install the unixODBC Driver Manager. Installing the unixODBC Driver Manager could cause a failure of an existing Driver Manager.
Installing the Driver Manager for Microsoft ODBC Driver 13, 13.1, and 17
The driver manager dependency is resolved automatically by the package management system when you install the Microsoft ODBC Driver 13, 13.1, or 17 for SQL Server on Linux or macOS by following the instructions in Installing the Microsoft ODBC Driver for SQL Server on Linux or macOS.
Installing the Driver Manager for Microsoft ODBC Driver 11 for SQL Server
(SUSE and Red Hat Linux only.)
Using the Installation Script
Important
These instructions refer to msodbcsql-11.0.2270.0.tar.gz, which is the installation file for Red Hat Linux. If you are installing the Preview for SUSE Linux, the file name is msodbcsql-11.0.2260.0.tar.gz.
To install the driver manager:
Make sure that you have root permission.
Go to the directory where the MicrosoftSQL Server ODBC Driver download placed the file called
msodbcsql-11.0.2270.0.tar.gz. Make sure that you have the *.tar.gz file that matches your version of Linux. To extract the files, execute the following command: tar xvzf msodbcsql-11.0.2270.0.tar.gz.Change to the
msodbcsql-11.0.2270.0directory and there you should see a file calledbuild_dm.sh. You can runbuild_dm.shto install the unixODBC Driver Manager.To see a list of the available options, execute the following command: ./build_dm.sh --help.
When you are ready to install, and if your computer can access an external site via FTP, execute the following command: ./build_dm.sh.
If your computer cannot access an external site via FTP, get unixODBC-2.3.0.tar.gz. You can get unixODBC-2.3.0.tar.gz from http://www.unixodbc.org. Click the Download link on the left side of the page to go to the download page. Then click the appropriate link to download unixODBC-2.3.0 (not unixODBC-2.3.1). unixODBC-2.3.1 is not supported with this release of the Microsoft ODBC Driver 11 for SQL Server. Execute the following command to begin the unixODBC Driver Manager installation: ./build_dm.sh --download-url=file://unixODBC-2.3.0.tar.gz.
Type YES to proceed with unpacking the files. This part of the process can take up to five minutes to complete.
After the script stops running, follow the instructions on the screen to install the unixODBC Driver Manager.
You are now ready to install the driver. For more information, see Installing the Microsoft ODBC Driver for SQL Server on Linux and macOS. Specs microsoft word for mac.
Manual Installation
If the installation script is unable to complete, configure and build the proper driver manager yourself.
Remove any older installed version of unixODBC (for example, unixODBC 2.2.11). On Red Hat Enterprise Linux 5 or 6, execute the following command: yum remove unixODBC. On SUSE Linux Enterprise, zypper remove unixODBC.
Go to http://www.unixodbc.org. Click the Download link on the left side of the page to go to the download page. Then click the appropriate link to save the file unixODBC-2.3.0.tar.gz to your computer. UnixODBC-2.3.1 is not supported with this release of the Microsoft ODBC Driver 11 for SQL Server.
On your Linux computer, execute the command: tar xvzf unixODBC-2.3.0.tar.gz.
Change to the unixODBC-2.3.0 directory.
At a command prompt, execute the command: CPPFLAGS='-DSIZEOF_LONG_INT=8'.
At a command prompt, execute the command: export CPPFLAGS.
At a command prompt, execute the command: './configure --prefix=/usr --libdir=/usr/lib64 --sysconfdir=/etc --enable-gui=no --enable-drivers=no --enable-iconv --with-iconv-char-enc=UTF8 --with-iconv-ucode-enc=UTF16LE'.
At a command prompt (logged in as root), execute the command: make.
At a command prompt (logged in as root), execute the command: make install.
You are now ready to install the driver. For more information, see Installing the Microsoft ODBC Driver for SQL Server on Linux and macOS.
See Also
-->This article contains a list of known issues with the Microsoft ODBC Driver 13, 13.1, and 17 for SQL Server on Linux and macOS.
Additional issues will be posted on the Microsoft ODBC driver team blog.
Due to system library limitations, Alpine Linux supports fewer character encodings and locales. For example, en_US.UTF-8 is not available. See musl libc - functional differences from glibc for more information.
Windows, Linux, and macOS convert characters from the Private Use Area (PUA) or End User-Defined Characters (EUDC) differently. Conversions performed on the server within Transact-SQL use the Windows conversion library. Conversions in the driver use the Windows, Linux, or macOS conversion libraries. Each library may produce different results when performing these conversions. For more information, see End-User-Defined and Private Use Area Characters.
If the client encoding is UTF-8, the driver manager does not always correctly convert from UTF-8 to UTF-16. Currently, data corruption occurs when one or more characters in the string are not valid UTF-8 characters. ASCII characters are mapped correctly. The driver manager attempts this conversion when calling the SQLCHAR versions of the ODBC API (for example, SQLDriverConnectA). The driver manager will not attempt this conversion when calling the SQLWCHAR versions of the ODBC API (for example, SQLDriverConnectW).
The ColumnSize parameter of SQLBindParameter refers to the number of characters in the SQL type, while BufferLength is the number of bytes in the application's buffer. However, if the SQL data type is
varchar(n)orchar(n), the application binds the parameter as SQL_C_CHAR or SQL_C_VARCHAR, and the character encoding of the client is UTF-8, you may get a 'String data, right truncation' error from the driver even if the value of ColumnSize is aligned with the size of the data type on the server. This error occurs since conversions between character encodings may change the length of the data. For example, a right apostrophe character (U+2019) is encoded in CP-1252 as the single byte 0x92, but in UTF-8 as the 3-byte sequence 0xe2 0x80 0x99.
For example, if your encoding is UTF-8 and you specify 1 for both BufferLength and ColumnSize in SQLBindParameter for an out-parameter, and then attempt to retrieve the preceding character stored in a char(1) column on the server (using CP-1252), the driver attempts to convert it to the 3-byte UTF-8 encoding, but cannot fit the result into a 1-byte buffer. In the other direction, it compares ColumnSize with the BufferLength in SQLBindParameter before doing the conversion between the different code pages on the client and server. Because a ColumnSize of 1 is less than a BufferLength of (for example) 3, the driver generates an error. To avoid this error, ensure that the length of the data after conversion fits into the specified buffer or column. Note that ColumnSize cannot be greater than 8000 for the varchar(n) type.
See Also
Programming Guidelines
Release Notes