Amazon Redshift provides 64-bit ODBC drivers for Linux, Windows, and macOS X operating systems. The 32-bit ODBC drivers are discontinued. Further updates will not be released, except for urgent security patches.
Use the following procedure to download the Amazon Redshift ODBC drivers for Windows operating systems. Only use a driver other than these if you're running a third-party application that is certified for use with Amazon Redshift and that requires a specific driver.
Sas Oledb Drivers For Mac
Use the steps in this section to download and install the Amazon Redshift ODBC drivers on a supported Linux distribution. The installation process installs the driver files in the following directories:
When you have finished installing the drivers, configure them for use on your system. For more information on driver configuration, see Use an ODBC driver manager to configure the driver on Linux and macOS X operating systems.
On Linux and macOS X operating systems, you use an ODBC driver manager to configure the ODBC connection settings. ODBC driver managers use configuration files to define and configure ODBC data sources and drivers. The ODBC driver manager that you use depends on the operating system that you use:
For more information about the supported ODBC driver managers to configure the Amazon Redshift ODBC drivers, see System requirements for Linux operating systems and System requirements for macOS X operating systems. Also, see "Specifying ODBC Driver Managers on Non- Windows Machines" in the Amazon Redshift ODBC connector installation and configuration guide.
To install the OLE DB Driver for SQL Server, you need the msoledbsql.msi installer.Run the installer and make your preferred selections. The OLE DB Driver for SQL Server can be installed side-by-side with earlier versions of Microsoft OLE DB providers.
The files for OLE DB Driver for SQL Server (msoledbsql19.dll/msoledbsql.dll, msoledbsqlr19.dll/msoledbsqlr.rll) are installed in %SYSTEMROOT%\system32\ . Additionally, the x64 msoledbsql.msi installs 32-bit binaries in %SYSTEMROOT%\SysWOW64\.
The header and library files for OLE DB Driver for SQL Server (msoledbsql.h and msoledbsql.lib/msoledbsql19.lib) are installed in %PROGRAMFILES%\Microsoft SQL Server\Client SDK\OLEDB\\SDK. Additionally, the x64 msoledbsql.msi installs the same files in %PROGRAMFILES(x86)%\Microsoft SQL Server\Client SDK\OLEDB\\SDK.
You can distribute OLE DB Driver for SQL Server through msoledbsql.msi. You might have to install OLE DB Driver for SQL Server when you deploy an application. One way to install multiple packages in what seems to the user to be a single installation is to use chainer and bootstrapper technology. For more information, see Authoring a Custom Bootstrapper Package for Visual Studio 2005 and Adding Custom Prerequisites.
The x64 msoledbsql.msi also installs the 32-bit version of OLE DB Driver for SQL Server. If your application targets a platform other than the one it was developed on, you can download versions of msoledbsql.msi for x64 and x86.
When you invoke msoledbsql.msi, only the client components are installed by default. The client components are files that support running an application that was developed using OLE DB Driver for SQL Server. To also install the SDK components, specify ADDLOCAL=All on the command line. For example:
When you try to create an ODBC DSN for drivers that are provided by Microsoft Access in the Data Sources ODBC Administrator, the attempt fails. This problem occurs if you're using a Click-to-Run (C2R) installation of Office that doesn't expose the Access Database Engine outside of the Office virtualization bubble. Depending on the version of Office, you may encounter any of the following issues when you try this operation:
This article describes how to configure the Databricks ODBC and JDBC drivers to connect your tools or clients to Databricks. For tool or client specific connection instructions, see the Databricks integrations.
Legacy Spark JDBC drivers accept SQL queries in ANSI SQL-92 dialect and translate the queries to the Databricks SQL dialect before sending them to the server. However, if your application generates Databricks SQL directly or your application uses any non-ANSI SQL-92 standard SQL syntax specific to Databricks, Databricks recommends that you set UseNativeQuery=1 as a connection configuration.With that setting, the driver passes the SQL queries verbatim to Databricks.
This article describes the latest versions of Microsoft Analysis Services OLE DB Provider for Microsoft SQL Server (MSOLAP) and where you can download the providers.Microsoft Excel uses MSOLAP to connect to Microsoft SQL Server. However, Excel cannot connect to a SQL Server Analysis Services database if an incorrect version of MSOLAP is used. For example, Excel 2010 cannot use Analysis Services OLE DB Provider for SQL Server 2008 R2 (MSOLAP.4) to retrieve data from a Microsoft SQL Server 2012 cube. To retrieve the data, Excel 2010 must use Analysis Services OLE DB Provider for SQL Server 2012 (MSOLAP.5) instead. Note If you want to connect to SQL Server 2012 Service Pack 1 (SP1), you have to upgrade the provider to the latest version of MSOLAP.5. You can obtain the corresponding providers and drivers for SQL Server from the feature pack for each version of SQL Server.The providers for SQL Server are backward compatible. Therefore, if a provider tries to retrieve data from a data source server, and the version of the data source server corresponds to a version of the provider that is later than the version of the provider that is installed, the provider may experience certain issues. However, if the version of the data source server corresponds to a version of the provider that is earlier than the version of the provider that is installed, the provider can retrieve data from the data source server. We recommend that you install the version of MSOLAP that matches the latest version of the data source server that you are using.Note Some features that are supported in later versions of SQL Server may not be available in versions of Excel that are not written specifically to take advantage of the features.To connect to SQL Server Analysis Services, download the appropriate version of MSOLAP for your operating system. To determine which version of MSOLAP you are using, check the version number of the msolapxxx.dll file on your system. To do this, right-click msolapxxx.dll, and then check the version number in the Details tab in the Properties menu.Note xxxrepresents the version number of MSOLAP. For example, the version number may be 100 (Msolap100.dll) for MSOLAP.4 and 110 (Msolap110.dll) for MSOLAP.5. To connect to SQL Server relational databases, we recommend that you download the appropriate Microsoft SQL Native Client instead of using the old Microsoft/Windows Data Access Components (MDAC/WDAC) drivers for your operating system. To determine which version of SQL Server Native Client that you have installed on your system, follow the steps that are described earlier in this article to check the version of the sqlnclixx.dll file.
Open Database Connectivity (ODBC) provides an API for accessing databases. Database vendors provide ODBC drivers for their database products. An application written to the ODBC standard can be ported to other databases that also provide an ODBC interface.
Of course, there are many applications -- used primarily by analysts and other business users -- which do not support direct MySQL connections and therefore, rely on ODBC to gain access to external SQL data sources. These ODBC connections are managed by underlying drivers that handle communication and the transfer of data between client applications and a defined data source.
Given that the BI Connector provides a MySQL interface we have been asked why not just utilize the existing MySQL, or similar, ODBC drivers? There are a few reasons for this but our primary motivation was to improve the end-user experience by making installation and set up simple and easy.
Many problems can be resolved by upgrading your Connector/ODBC drivers to the latest available release. On Windows, make sure that you have the latest versions of the Microsoft Data Access Components (MDAC) installed.
This is not a bug, but is related to the way Windows x64 editions operate with the ODBC driver. On Windows x64 editions, the Connector/ODBC driver is installed in the %SystemRoot%\SysWOW64 folder. However, the default ODBC Data Source Administrator that is available through the Administrative Tools or Control Panel in Windows x64 Editions is located in the %SystemRoot%\system32 folder, and only searches this folder for ODBC drivers.
On Windows x64 editions, use the ODBC administration tool located at %SystemRoot%\SysWOW64\odbcad32.exe, this will correctly locate the installed Connector/ODBC drivers and enable you to create a Connector/ODBC DSN.
There is a known issue with a specific version of the msjet40.dll that exhibits this issue. The version affected is 4.0.9025.0. Reverting to an older version will enable you to create the links. If you have recently updated your version, check your WINDOWS directory for the older version of the file and copy it to the drivers directory.
Release 6.x (and Release 5.2 on some platforms) and newer drivers ship with the separate OpenLink License Manager, oplmgr. General Guidance, for Windows, Linux, and other Unix-like OS (except macOS)
Special Guidance for Release 6.x or 7.x on macOS Snow Leopard (10.8.x) and later
Related Documentation
Changes in the Gatekeeper in Snow Leopard (10.8.x), Mavericks (10.9.x), Yosemite (10.10.x), El Capitan (10.11.x), Sierra (10.12.x), High Sierra (10.13.x), Mojave (10.14.x), and Catalina (10.15.x) required updated License Manager binaries and startup scripts. Installers produced after 2014-12-04 for Release 6.x and 7.x, and all installers for Release 8.x, include these updates. Updated oplmgr installers are also available for users with drivers installed, or driver installers dated, prior to 2014-12-04. 2ff7e9595c
Comments