Download mac odbc mysql driver

Skip to main content. This browser is no longer supported. Download Microsoft Edge More info. Contents Exit focus mode. Please rate your experience Yes No.

Any additional feedback? Important If you installed the v17 msodbcsql package that was briefly available, you should remove it before installing the msodbcsql17 package. Submit and view feedback for This product This page.

View all page feedback. In this article. The dynamic library dylib file that contains all of the driver's functionality. The accompanying resource file for the driver library. This file is installed in [driver. The header file that contains all of the new definitions needed to use the driver.

Note: You cannot reference msodbcsql. The text file that contains the terms of the End-User License Agreement. The text file that contains release notes. The openlink. OpenLink's Multi-Tier brokers read the oplrqb. The oplrqb. OpenLink Software produces two, graphical Administrative Assistants.

This assistant allows users to create Multi-Tier data source names, configure Multi-Tier Server components, configure rules-based security, and debug ODBC connectivity problems. The Multi-Tier server component comprises a request broker and one or more database agents. The request broker is a generic, listening process. The broker reviews these requests and spawns the appropriate database agent.

The database agent is the only portion of the Multi-Tier product portfolio that is written to a specific CLI. Specifically, the database agent speaks the CLI of the database to which it is meant to connect. Hence, the agent is able to submit the SQL request to the database, retrieve its results, and convey those results to the client application.

ODBC data source names are collections of parameters, which enable the OpenLink driver to identify and connect to the data store. There are several means, which users may employ to create ODBC data source names. There are three methods, which users may employ to configure Darwin data source names. Expert users may configure the odbc. The odbc. Users may open this file with vi or a similar text editor.

The following table describes sections, which users will encounter in odbc. These data sources names are associated with formal data source specifications, which appear later in the file. The data source specification lists parameters, which are necessary to establish the ODBC connection. Here is the OpenLink data source specification format:.

The following table explains the parameters that appear in the data source specification sections. The following table explains additional values, which may be added to Multi-Tier data source name specifications. OpenLink produces the Multi-Tier Administrative Assistant for all server operating systems, which it supports.

This Web-based assistant is powered by OpenLink's server components, and it provides utilities to configure these components. Use the following instructions to create data source names with the Multi-Tier Administrative Assistant. The following instructions will enable users to create Multi-Tier data source names on Mac Classic. There are two methods, which users may employ to configure Mac OS X data source names. Expert users may configure the ODBC. The ODBC. Users may open this file with TextEdit or a similar text editor.

The following table describes sections, which users will encounter in ODBC. Here is the OpenLink Multi-Tier data source specification format:. The following table explains the parameters that appear in the Multi-Tier data source specification sections. All OpenLink Single-Tier drivers recognize a common subset of specifications parameters. Individual Single-Tier drivers recognize an additional set of parameters, which are specialized for the database to which they connect.

Different driver managers are installed by different OpenLink install bundles and client applications. Apple dylibs are dynamic shared libraries. One copy of a. These libraries are similar in theory to Unix dynamic libraries.

However, their use and implementation are different. Apple frameworks are special bundles or packages, which contain dynamic shared libraries, header files, documentation, and other resources that are necessary to use the library. The Code Fragment Manager loads code fragments libraries, applications, code, etc.

For instance, the setup routine will replace Server with Net 8 Service Name, if you choose an Oracle domain. This distinction is critical. The frameworks format driver manager provides the applications developer with versatility that is not available with dylibs.

Frameworks bundles contain multiple revisions of the iODBC driver manager. Moreover, the driver manager library name points to the latest revision of the component. Therefore, developers do not need to set environment variables to point to the appropriate file. However, applications developers can choose to instantiate legacy revisions. In other words, developers can hard link applications to older driver managers to access functionality that is not present in recent revisions.

It identifies the correct driver manager format, which to load. These technologies are based on the principle of interoperability. This principle dictates that one client application can access diverse, back-end database management systems, without knowledge of proprietary database protocols.

Thereby, this powerful technology allows application developers to develop, compile, and ship applications, which speak to any, ODBC-compliant data source. The application developer does not need to cater to any specific vendor's DBMS. The application and DBMS may reside on one or more machines. These machines may comprise similar or dissimilar operating systems and hardware. The specification defines the ability to:. The two driver formats also provide the following features:.

Users may also encounter another driver manager created by Visigenic and maintained by Intersolv, Merant, and Data Direct respectively. Data sources The term data source has two, distinct meanings. Use of these drivers requires knowledge of the following items: Environment Variables Client Libraries Header Files Configuration Files Administrative Assistants Server Components Environment Variables Environment variables pass the locations of files and directories, which the operating system or applications need to accomplish tasks.

The following table lists environment variables, which must be set on Darwin clients. This variable is not required for ODBC connectivity. PATH Passes the full path to directories, which contain executables. For example: Users may also add the variables to their. Filename Description libiodbc. Older, iODBC driver manager libraries are linked to the latest revision libiodbc. Configuring Darwin Data Source Names There are three methods, which users may employ to configure Darwin data source names.

It also pairs the appropriate ODBC driver name with the data source name. Data Source Specifications This section lists the actual data source names. Each data source name is composed of a formal name and a parameter list. Here is the OpenLink data source specification format: Here is a sample data source specification: The following table explains the parameters that appear in the data source specification sections.

ServerType Passes a valid OpenLink domain alias. This domain alias must match a valid domain alias in the Single-Tier openlink. The drivers use these domain aliases as starting points from which to assess rules, environment variables, and agent binaries to instantiate for connections. Username Passes a valid database username. Password Passes a valid database password. Progress users should pass the full path to their databases. Users may also use the field to pass database native communications parameters to establish three-tier connections.

For instance, users may pass Sybase instance names, Oracle aliases, or Ingres vnodes to connect database agents--through local database native clients--to remote databases. FetchBufferSize Passes an integer, which represents the number of rows that the driver will return during an individual fetch. Deferred fetching causes large, binary objects to be fetched after other, smaller data.

This enhances performance. JetFix facilitates translation of data types by Microsoft's Jet Engine. This feature is intended primarily for use with Microsoft client applications on Windows.

Description Passes a description of the use or nature of the data source name. Hostname Passes the hostname or IP address of the machine, which contains the OpenLink request broker. Port Passes the TCP port on which the request broker listens. Locate the [Startup] section. Record the value passed to HttpPort. For example: Exit the file. Run the following command: Open a Web browser.

Provide the administrator username and password. Both fields default to admin. Click Add. Click Next. Use setup screens 1 to 5 to provide connection parameters and to disable or enable optional features. Figures describes Single-Tier parameters and options. Figure describes Multi-Tier parameters and options.

Comment Passes a description of the use or nature of the data source name. No Login Dialog Box Enables or disables the login popup box. Defer Fetching of long data Passes a Yes or No value to enable or disable deferred fetching. Row buffer size Passes an integer, which represents the number of rows that the driver will return during an individual fetch operation. This feature is intended for use with MS Access client applications.

Environment Passes a valid OpenLink domain alias. Domain Passes a valid OpenLink domain alias. This domain alias must match a valid domain alias in the Multi-Tier oplrqb.

Port Passes the TCP port, on which the request broker listens. Protocol Passes a valid OpenLink network protocol. No Login Dialog Box Enables or disables login popup box.

Row buffer size Passes an integer, which represents the number of rows that the driver will return during an individual fetch. Click the Save button, which appears on the sixth setup screen.