This article provides commands for installing the ODBC driver from the bash shell. If you want to download the packages directly, see Download ODBC Driver for SQL Server. Microsoft ODBC 17. The following sections explain how to install the Microsoft ODBC driver 17 from the bash shell for different Linux distributions. Alpine Linux; Debian. Odbc free download - ODBC Manager, Actual ODBC Driver for Access, Actual ODBC Driver for Oracle, and many more programs.
-->This article explains how to install the Microsoft ODBC Driver for SQL Server on Linux. It also includes instructions for the optional command-line tools for SQL Server (
bcp
and sqlcmd
) and the unixODBC development headers.This article provides commands for installing the ODBC driver from the bash shell. If you want to download the packages directly, see Download ODBC Driver for SQL Server.
Microsoft ODBC 17
The following sections explain how to install the Microsoft ODBC driver 17 from the bash shell for different Linux distributions.
Download game big farm permainan berkebun pc. Important
If you installed the v17
msodbcsql
package that was briefly available, you should remove it before installing the msodbcsql17
package. This will avoid conflicts. The msodbcsql17
package can be installed side by side with the msodbcsql
v13 package.Alpine Linux
Note
Driver version 17.5 or higher is required for Alpine support.
Debian
Note
Excel Mac Odbc
You can substitute setting the environment variable 'ACCEPT_EULA' with setting the debconf variable 'msodbcsql/ACCEPT_EULA' instead:
echo msodbcsql17 msodbcsql/ACCEPT_EULA boolean true | sudo debconf-set-selections
Crack mac app.Red Hat Enterprise Server and Oracle Linux
SUSE Linux Enterprise Server
Ubuntu
Note
- Driver version 17.2 or higher is required for Ubuntu 18.04 support.
- Driver version 17.3 or higher is required for Ubuntu 18.10 support.
Note
You can substitute setting the environment variable 'ACCEPT_EULA' with setting the debconf variable 'msodbcsql/ACCEPT_EULA' instead:
echo msodbcsql17 msodbcsql/ACCEPT_EULA boolean true | sudo debconf-set-selections
Previous versions
The following sections provide instructions for installing previous versions of the Microsoft ODBC driver on Linux. The following driver versions are covered:
ODBC 13.1
The following sections explain how to install the Microsoft ODBC driver 13.1 from the bash shell for different Linux distributions.
Debian 8
RedHat Enterprise Server 6
RedHat Enterprise Server 7
SUSE Linux Enterprise Server 11
SUSE Linux Enterprise Server 12
Ubuntu 15.10
Ubuntu 16.04
Ubuntu 16.10
ODBC 13
The following sections explain how to install the Microsoft ODBC driver 13 from the bash shell for different Linux distributions.
RedHat Enterprise Server 6
RedHat Enterprise Server 7
Ubuntu 15.10
Ubuntu 16.04
SUSE Linux Enterprise Server 12
Offline installation
If you prefer/require the Microsoft ODBC Driver 13 to be installed on a computer with no internet connection, you will need to resolve package dependencies manually. The Microsoft ODBC Driver 13 has the following direct dependencies:
- Ubuntu: libc6 (>= 2.21), libstdc++6 (>= 4.9), libkrb5-3, libcurl3, openssl, debconf (>= 0.5), unixodbc (>= 2.3.1-1)
- Red Hat:
glibc, e2fsprogs, krb5-libs, openssl, unixODBC
- SUSE:
glibc, libuuid1, krb5, openssl, unixODBC
Each of these packages in turn has their own dependencies, which may or may not be present on the system. For a general solution to this issue, refer to your distribution's package manager documentation: Redhat, Ubuntu, and SUSE
It is also common to manually download all the dependent packages and place them together on the installation computer, then manually install each package in turn, finishing with the Microsoft ODBC Driver 13 package.
Redhat Linux Enterprise Server 7
- Download the latest
msodbcsql
.rpm
from https://packages.microsoft.com/rhel/7/prod/. - Install dependencies and the driver.
Ubuntu 16.04
- Download the latest
msodbcsql
.deb
from https://packages.microsoft.com/ubuntu/16.04/prod/pool/main/m/msodbcsql/. - Install dependencies and the driver.
SUSE Linux Enterprise Server 12
- Download the latest
msodbcsql
.rpm
from https://packages.microsoft.com/sles/12/prod/. - Install the dependencies and the driver.
After you have completed the package installation, you can verify that the Microsoft ODBC Driver 13 can find all its dependencies by running ldd and inspecting its output for missing libraries:
ODBC 11
The following sections explain how to install the Microsoft ODBC driver 11 on Linux. Before you can use the driver, install the unixODBC driver manager. For more information, see Installing the Driver Manager.
Installation Steps
Important
These instructions refer to
msodbcsql-11.0.2270.0.tar.gz
, which is 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:
- Make sure that you have root permission.
- Change to the directory where the download placed the file
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.0
directory and there you should see a file called install.sh. - To see a list of the available installation options, execute the following command: ./install.sh.
- Make a backup of odbcinst.ini. The driver installation updates odbcinst.ini. odbcinst.ini contains the list of drivers that are registered with the unixODBC Driver Manager. To discover the location of odbcinst.ini on your computer, execute the following command:
odbc_config --odbcinstini
. - Before you install the driver, execute the following command:
./install.sh verify
. The output of./install.sh verify
reports if your computer has the required software to support the ODBC driver on Linux. - When you are ready to install the ODBC driver on Linux, execute the command:
./install.sh install
. If you need to specify an install command (bin-dir
orlib-dir
), specify the command after the install option. - After reviewing the license agreement, type YES to continue with the installation.
Installation puts the driver in
/opt/microsoft/msodbcsql/11.0.2270.0
. The driver and its support files must be in /opt/microsoft/msodbcsql/11.0.2270.0
.To verify that the Microsoft ODBC driver on Linux was registered successfully, execute the following command:
odbcinst -q -d -n 'ODBC Driver 11 for SQL Server'
.Uninstall
Alpari mt4 demo. You can uninstall the ODBC driver 11 on Linux by executing the following commands:
rm -f /usr/bin/sqlcmd
rm -f /usr/bin/bcp
rm -rf /opt/microsoft/msodbcsql
odbcinst -u -d -n 'ODBC Driver 11 for SQL Server'
Driver files
The ODBC driver on Linux consists of the following components:
Component | Description |
---|---|
libmsodbcsql-17.X.so.X.X or libmsodbcsql-13.X.so.X.X | The shared object (so ) dynamic library file that contains all of the driver's functionality. This file is installed in /opt/microsoft/msodbcsql17/lib64/ for the Driver 17 and in /opt/microsoft/msodbcsql/lib64/ for Driver 13. |
msodbcsqlr17.rll or msodbcsqlr13.rll | The accompanying resource file for the driver library. This file is installed in [driver .so directory]./share/resources/en_US/ |
msodbcsql.h | The header file that contains all of the new definitions needed to use the driver. Note: You cannot reference msodbcsql.h and odbcss.h in the same program. msodbcsql.h is installed in /opt/microsoft/msodbcsql17/include/ for Driver 17 and in /opt/microsoft/msodbcsql/include/ for Driver 13. |
LICENSE.txt | The text file that contains the terms of the End-User License Agreement. This file is placed in /usr/share/doc/msodbcsql17/ for Driver 17 and in /usr/share/doc/msodbcsql/ for Driver 13. |
RELEASE_NOTES | The text file that contains release notes. This file is placed in /usr/share/doc/msodbcsql17/ for Driver 17 and in /usr/share/doc/msodbcsql/ for Driver 13. |
Resource file loading
The driver needs to load the resource file in order to function. This file is called
msodbcsqlr17.rll
or msodbcsqlr13.rll
depending on the driver version. The location of the .rll
file is relative to the location of the driver itself (so
or dylib
), as noted in the table above. As of version 17.1 the driver will also attempt to load the .rll
from the default directory if loading from the relative path fails. The default resource file path on Linux is /opt/microsoft/msodbcsql17/share/resources/en_US/
.Troubleshooting
If you are unable to make a connection to SQL Server using the ODBC driver, see the known issues article on troubleshooting connection problems.
Next steps
After installing the driver, you can try the C++ ODBC example application. For more information about developing ODBC applications, see Developing Applications.
For more information, see the ODBC driver release notes and system requirements.
Similar to Windows, macOS utilizes named data sources (DSNs) for connecting ODBC-based client applications to Snowflake.
In this Topic:
Prerequisites¶
Operating System¶
For a list of the operating systems supported by Snowflake clients, see Operating System Support.
iODBC¶
The Snowflake ODBC driver for Mac requires iODBC, which is available for download from:
To install iODBC:
- After downloading iODBC, double-click on the downloaded .dmg file. Google chrome download mac ipad.
- Double-click on the installer file,
iODBC-SDK.pkg
, and follow the prompts.
Note
iODBC provides a GUI administrator tool for configuring drivers and DSNs; however, this tool has not been tested for use with Snowflake and, therefore, should not be used to create or manage DSNs. Use ODBC Manager instead. Mac os x sierra download free.
ODBC Manager — Optional/Recommended¶
ODBC Manager is a GUI tool for configuring drivers and creating/managing DSNs. The tool is optional because you can also create DSNs manually by editing the appropriate
odbc.ini
file. ODBC Manager is available from:To install ODBC Manager:
- After downloading ODBC Manager, double-click on the downloaded .dmg file.
- Double-click on the installer file,
ODBCManager.pkg
, and follow the prompts.
The installer installs ODBC Manager in the
~/Applications/Utilities
directory.Step 1: Install the ODBC Driver¶
To install the Snowflake ODBC driver for macOS:
- If you haven’t already downloaded the driver, download it now. For details, see Downloading the ODBC Driver.
- Double-click on the downloaded .dmg file,
snowflake_odbc_mac-<version>.dmg
. - Double-click on the installer file,
snowflakeODBC_<version>.pkg
, and follow the prompts.You will likely be prompted for the administrator/sudo password for the machine on which you are installing the driver.
If you choose the default directory when prompted, the installer installs the ODBC driver files in the following directories:
Step 2: Configure the ODBC Driver¶
To configure the ODBC driver for macOS, create one or more data source (DSNs), which are stored in the following files, depending on the type of DSN you create:
- User DSNs:
~/Library/ODBC/odbc.ini
- System DSNs:
/Library/ODBC/odbc.ini
To create a DSN, either use ODBC Manager or edit the appropriate
odbc.ini
file.Creating a DSN Using ODBC Manager¶
To create a DSN in ODBC Manager:
- Start ODBC Manager.
- Click on User DSN or System DSN.
- Click the Add button.
- Select the driver to use (Snowflake) and click OK.
- Enter the name of the DSN and optionally a description.
- Create a Keyword/Value pair for each DSN parameter:
- Click Add to create a Keyword/Value pair.
- Select Keyword and replace it with the parameter name.
- Select Value and replace it with the value for the parameter. https://energydistribution.weebly.com/best-free-offline-games-for-android-download.html.
Repeat this process for each parameter. For details about the parameters that can be set for each DSN, see ODBC Configuration and Connection Parameters. - Click OK to create the DSN.
If you are creating the first user or system DSN for the ODBC driver, ODBC Manager creates the
odbc.ini
file in the corresponding directory for the type of DSN you are creating. If you are creating additional DSNs, ODBC Manageradds entries for each DSN to the existing odbc.ini
file. Image enhancing software for mac.Creating a DSN by Adding an Entry in the odbc.ini
File¶
If a user or system DSN has already been created for the driver, add the new entry to the
odbc.ini
file that already exists in the corresponding directory for the type of DSN you are creating. If you are creating the first DSNfor the driver, you must manually create the odbc.ini
file and add the entry to the file.For each DSN, specify:
- DSN name and driver name (Snowflake), in the form of
<dsn_name>=<driver_name>
. - Directory path and name of the driver file, in the form of
Driver=/opt/snowflake/snowflakeodbc/lib/universal/libSnowflake.dylib
. - Connection parameters, such as
server
anduid
(user login name). Any connection parameters you add to the DSN do not need to be specified in the ODBC connect string. - Any additional parameters, such as default
role
,database
, andwarehouse
.
Free Download Odbc Driver For Mac
Parameters are specified in the form of
<parameter_name>=<value>
. For details about the parameters that can be set for each DSN, see ODBC Configuration and Connection Parameters.The following example illustrates an
odbc.ini
file containing two drivers, testodbc1
for account xy12345
(located in the AWS US West region) and testodbc2
for account yz23456
(located in the AWS US East region):Note the following:
- Both
testodbc1
andtestodbc2
have default roles. testodbc2
also has a default database and warehouse.
Step 3: Test the ODBC Driver¶
You can use the
iodbctest
command line utility provided with iODBC to test the DSNs you create.When prompted for the ODBC connect string, enter the required connection parameters (DSN name, server, user login name, and password), as well as any other parameters that you would like to enter as part of the connect string. Theconnect string takes parameters in the form of
<parameter_name>=<value>
, e.g. dsn=testodbc2
, with each parameter separated by a semi-colon (;
) and no blank spaces. For the list of supported parameters, seeODBC Configuration and Connection Parameters.Note
If you set the server and user login name in the DSN, the only required parameters in the connect string are the DSN name and user password.
For example: