Odbc connector
Author: m | 2025-04-24
MySQL Connector/ODBC Developer Guide. Introduction to MySQL Connector/ODBC. Connector/ODBC Versions. General Information About ODBC and Connector/ODBC. Connector/ODBC Architecture. ODBC Driver Managers. Connector/ODBC Installation. Installing Connector/ODBC on Windows.
ODBC Connector v16 - Installing the ODBC Connector on Windows
Posted on December 4, 2023 by MariaDB is pleased to announce the immediate availability of MariaDB Connector/ODBC 3.1.20 and 3.2.1 RC, Connector/C 3.3.8 and 3.1.23, and Connector/Java 3.3.1.Download NowRelease Notes and ChangelogsMariaDB Connector/ODBC 3.2.1 RCMariaDB Connector/ODBC 3.2.1 Release NotesMariaDB Connector/ODBC 3.2.1 ChangelogNotable items in this release include:Support ODBC 3.8 standard. The driver is now compliant with ODBC standard version 3.8. Mainly that means implementation of SQLCancelHandle API function and SQL_ATTR_RESET_CONNECTION connection attribute support.Add Prepared Statement Cache to the Connector. The driver now uses cache for server side prepared statements, that allows not to re-prepare statements, but use them from the cache. Application can configure the cache with PSCACHESIZE and MAXCACHEKEY connection string options. The former sets the size of the cache, i.e. the number of statements that will be cached, the latter is the maximal size of the cache key, that effectively limits the maximum query length, that will be the value of MAXCACHEKEY – length of the current schema name – 1.Connector/ODBC is now available as RPM and DEB packages for selected platforms (RHEL, Ubuntu, Debian)Improved protocol resilience in case of resultset streaming. In version 3.1 if the resultset streaming is used, it will block the connection, and the driver will return error on any new query. The 3.2.1 driver in this case will cache the rest of currently streamed resultset, and execute the new query without errorFixes for various issues.MariaDB Connector/ODBC 3.1.20MariaDB Connector/ODBC 3.1.20 Release NotesMariaDB Connector/ODBC 3.1.20 ChangelogNotable items in this release include:Add support of MADB_OPT_FLAG_NO_BIGINT option. Some classic applications do not support SQLBIGINT option. This option makes the column that normally would be of SQLBIGINT type to look like it is of SQLINTEGER typeConnector/ODBC is now available as RPM and DEB packages for selected platforms (RHEL, Ubuntu, Debian)Fixes for various issues.MariaDB Connector/C 3.3.8MariaDB Connector/C 3.3.8 Release NotesMariaDB Connector/C 3.3.8 ChangelogNotable items in this release include:Fixes for various issues.MariaDB Connector/C 3.1.23MariaDB Connector/C 3.1.23 Release NotesMariaDB Connector/C 3.1.23 ChangelogNotable items in this release include:Fixes for various issues.MariaDB Connector/Java 3.3.1MariaDB Connector/Java 3.3.1 Release NotesMariaDB Connector/Java 3.3.1 ChangelogNotable items in this release include:Fixes for various issues.See the release notes and changelogs for more details and visit mariadb.com/downloads/connectors to download.
MySQL :: MySQL Connector/ODBC Developer Guide :: 6 Connector/ODBC
These solutions include Simba Gateway connectivity as a service, standalone data connector, Simba SDK, as well as managed services with custom-built connectors via rigorous testing and authentication. For instance, the Simba BigQuery ODBC connector allows you to get data from BigQuery to your BI Tool.Seamlessly Integrate your Data into BigQuery With continuous real-time data movement, Hevo allows you to integrate your data sources and load it to the destination of your choice with a no-code, easy-to-setup interface. Try our 14-day full-feature access free trial! Get Started with Hevo for FreeConfiguration of BigQuery ODBC ConnectorStep 1: Install and Download Simba Google BigQuery ODBC ConnectorStep 2: License AllocationStep 3: Configuring Simba Google BigQuery ODBC ConnectorStep 1: Install and Download Simba Google BigQuery ODBC ConnectorStep 1: Visit the BigQuery ODBC JDBC Drivers page and download the connector for your Operating System. For this article, the windows version is selected. After downloading the MSI File, open it.Step 2: The BigQuery ODBC Connector Setup window will pop up on your screen. Click on the Next button. Step 3: For accepting the licensing agreement, click on the Next button.Step 4: Provide the location on your system where you want to install the connector and click on the Next button. Step 5: Finally, click on the Install button. After the BigQuery ODBC connector is completely installed, click on the Finish button to close the setup window. Step 2: License AllocationAfter you have submitted the form, the driver’s license is sent to your email. Ensure that the file is stored in the /lib/ folder underneath where the connector has been installed.Step 3: Configuring Simba Google BigQuery ODBC ConnectorStep 1: In your Windows system, click on the SEARCH and navigate to ODBC Administrator. Step 2: In the ODBC Administrator window, click on the System DSN tab. Search and clickMySQL :: MySQL Connector/ODBC Developer Guide :: 8.3 Connector/ODBC
MySQL Connector/ODBC 5.1.4 is available! Posted by: Jim Winstead Date: April 16, 2008 11:38AM Dear MySQL users,MySQL Connector/ODBC 5.1.4, a new version of the ODBC driver for theMySQL database management system, has been released. This release isthe first generally available (production) release of the 5.1 series andis suitable for use with any MySQL server version since MySQL 4.1,including MySQL 5.0, 5.1, and 6.0. (It will not work with 4.0 orearlier releases.)The release is now available in source and binary form for a number ofplatforms from our download pages at mirror sites. Note that not all mirror sites may be up to date at thispoint in time, so if you can't find this version on some mirror, please tryagain later or choose another download site.We welcome and appreciate your feedback, bug reports, bug fixes, patches,etc.: notes:* The installers for Microsoft Windows require that you uninstall any previous version of Connector/ODBC 5.1 (not 3.51) before installing.* The installer for 64-bit Windows installs both the 32-bit and 64-bit drivers. Microsoft has made available a 64-bit OLE DB provider for ODBC for Windows 2003 available at There is no binary package for Mac OS X on 64-bit PowerPC because Apple does not currently provide a 64-bit PowerPC version of iODBC.* The HP-UX 11.23 IA64 binary package does not include the GUI bits because of problems building Qt on that platform.Changes since the last 5.1 release: Bugs fixed: * SQLGetDiagRec() sometimes returned SQL_SUCCESS but no error message. (Bug #33910) * Driver installer (myodbc-installer.exe) fails to create a new DSN (Bug #35776) * Get wrong result with decimal(8,2) field type (Bug #35920) Includes changes from Connector/ODBC 3.51.25. Built using MySQL 5.0.56sp1.Enjoy!Jim WinsteadMySQL/Sun Subject Views Written By Posted MySQL Connector/ODBC 5.1.4 is available! 26076 April 16, 2008 11:38AM Sorry, you can't reply to this topic. It has been closed. Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.. MySQL Connector/ODBC Developer Guide. Introduction to MySQL Connector/ODBC. Connector/ODBC Versions. General Information About ODBC and Connector/ODBC. Connector/ODBC Architecture. ODBC Driver Managers. Connector/ODBC Installation. Installing Connector/ODBC on Windows. MySQL Connector/ODBC Developer Guide. Introduction to MySQL Connector/ODBC. Connector/ODBC Versions. General Information About ODBC and Connector/ODBC. Connector/ODBC Architecture. ODBC Driver Managers. Connector/ODBC Installation. Installing Connector/ODBC on Windows.SugarCRM ODBC Driver Download - ODBC connector for
To use MySQL Connector, you must download and install the JDBC and ODBC drivers on your Windows or Linux machine where the Secure Agent is installed.Before you use MySQL Connector, complete the following tasks:1Install the MySQL JDBC driver. 2Install the MySQL ODBC driver. Installing MySQL JDBC driverBefore you use MySQL Connector, install the MySQL JDBC driver and MySQL ODBC driver on the Windows or Linux machine where you installed the Secure Agent.Perform the following steps to install the MySQL JDBC drivers on Windows or Linux:2Select the required Product Version.3Select the Operating System as Platform Independent.4Download the .zip or .tar file based on your Windows or Linux system.5Extract the downloaded file and copy the mysql-connector-java-.jar file.6Paste the mysql-connector-java-.jar file in the following directory on the Secure Agent machine:- On Windows: \apps\Data_Integration_Server\ext\drivers- On Linux: /apps/Data_Integration_Server/ext/drivers7Set the MySQL_JDBC_DRIVER_JARNAME parameter to mysql-connector-java-.jar for the Data Integration Server service in the Secure Agent's system configuration details in Administrator.8Restart the Secure Agent.Installing MySQL ODBC driverBefore you use MySQL Connector, you must install the MySQL ODBC driver on the Windows or Linux machine where you installed the Secure Agent.Installing MySQL ODBC driver on WindowsPerform the following steps to install the MySQL ODBC driver on Windows:2Select the required Product Version.3Select the Operating System as Microsoft Windows.4Select the OS Version as Windows (x86, 64-bit).5Download the ZIP Archive mysql-connector-odbc-noinstall--winx64.zip file.Note: Do not use the MSI installer because it removes the existing MySQL ODBC driver versions from the system.6Extract the .zip file. 7Open the Command Prompt as an administrator and navigate to the extracted .zip file location. 8Run the following command in the command prompt: Install.bat After you install the MySQL ODBC driver, check if the installed MySQL ODBC Unicode Driver name appears as one of the available ODBC drivers under the ODBC Data Source Administrator (64-bit) dialog box:The following image shows the MySQL ODBC 8.0 Unicode Driver driver name in the ODBC Data Source Administrator (64-bit) dialog box when you try to create a new data source:Installing MySQL ODBC driver on LinuxPerform the following steps to install the MySQL ODBC driver on Linux:2Select the required Product Version.3Select the Operating System as Linux- Generic.4Select the OS Version as All.5Download the Linux - Generic (glibc 2.12) (x86, 64-bit) file.6Extract the downloaded file to a local directory in your system. Note: When you extract the file, ensure that you copy all files from the downloaded driver package.7Edit the /odbcinst.ini file and add the following values:[MySQL ODBC 8.0 Unicode Driver]Description = ODBC for MySQLDriver = /lib/libmyodbc8w.soSetup = /lib/libmyodbc8w.soFileUsage = 1In the Driver and Setup fields, you must specify the file path of the libmyodbc8w.so file that you extracted to the local directory in your system.Prerequisites to configure SSL with serverless runtime environmentYou can use the serverless runtime environment with MySQL Connector to connect to an SSL-enabled MySQL database.Before you configure a secure MySQL connection using the serverless runtime environment, complete the following prerequisite tasks to add the SSL certificates to the serverless runtime location:1Create the following structure for the serverless agent configuration in AWSMariaDB ODBC Connector, and Python Connector 1.1.4
MySQL Connector/ODBC 5.3.9, a new version of the ODBC driver forthe MySQL database management system, has been released.The available downloads include both a Unicode driver and an ANSIdriver based on the same modern codebase. Please select the driver typeyou need based on the type of your application – Unicode or ANSI.Server-side prepared statements are enabled by default. It is suitablefor use with any MySQL version from 5.5.This is the fourth release of the MySQL ODBC driver conforming to theODBC 3.8 specification. It contains implementations of key 3.8 features,including self-identification as a ODBC 3.8 driver, streaming of outputparameters (supported for binary types only), and support of theSQL_ATTR_RESET_CONNECTION connection attribute (for the Unicode driveronly).Also, Connector/ODBC 5.3 introduces a GTK+-based setup libraryproviding a GUI DSN setup dialog on some Unix-based systems, currentlyincluded in the Debian 7/8/9, EL6/OL6, EL7/OL7 (64-bit only), Fedora 24/25/26,FreeBSD 10/11, SLES 12, Ubuntu 14/16/17 packages. Other newfeatures in the 5.3 driver are FileDSN and Bookmarks support.The release is now available in source and binary form for a number ofplatforms from our download pages at information on installing, please see the documentation at in MySQL Connector/ODBC 5.3.9 (2017-07-24, GeneralAvailability)Functionality Added or ChangedWhen compiling Connector/ODBC on Windows platforms, it can now be linked statically (equivalent to the /MT compiler option in Visual Studio) or dynamically (equivalent to the /MD compiler option in Visual Studio) to the Visual C++ runtime. The default option is to link dynamically; if you want to link statically. set the new CMake option, STATIC_MSVCRT, to true. Another new CMake option, WITH_NODEFAULTLIB, has been introduced for specifying the Visual C++ runtime you want to link Connector/ODBC to when using mixed link types (that is, when link type to the Visual C++ runtime differs for Connector/ODBC and the MySQL client library it links to). See Building Connector/ODBC from a SourceChanges in MySQL Connector/ODBC ( )
MySQL Connector/ODBC 8.0.23 has been released Dear MySQL users,MySQL Connector/ODBC 8.0.23 is a new version in the MySQL Connector/ODBC8.0 series, the ODBC driver for the MySQL Server.The available downloads include both a Unicode driver and an ANSI driverbased on the same modern codebase. Please select the driver type youneed based on the type of your application - Unicode or ANSI.Server-side prepared statements are enabled by default. It is suitablefor use with the latest MySQL server version 8.0.This release of the MySQL ODBC driver is conforming to the ODBC 3.8specification. It contains implementations of key 3.8 features,including self-identification as a ODBC 3.8 driver, streaming of out (forbinary types only), and support of the SQL_ATTR_RESET_CONNECTIONconnection attribute (for the Unicode driver only).The release is now available in source and binary form for a number ofplatforms from our download pages at information on installing, please see the documentation at and thanks for your support!Changes in MySQL Connector/ODBC 8.0.23 (2021-01-18, General Availability)Bugs Fixed * Using the commercial glib package (authentication_ldap_sasl) with auth using GSSAPI (authentication_ldap_sasl_auth_method_name='GSSAPI') did not function. Added the missing sasl2 modules package. (Bug #32175842) * On Debian based systems, the post-installation script uses dpkg-architecture ODBC drivers path, so the associated dpkg-dev package was added as a runtime dependency. (Bug #32157740) * Microsoft Access halted when opening a linked table with only a JSON column. The JSON column type is now supported, and JSON data is only editable if another column is used as a primary key. Because JSON is a long data type with the maximum length of 4GB, it can't be used as a primary key by Microsoft Access and therefore tables having only JSON columns are only available in read-only mode. (Bug #32114901) * Removed the mysql-client-plugins dependency. It remains required for connections using commercial MySQL server accounts with LDAP authentication, so must be manually installed for that situation. The mysql-client-plugins package has conflicts with MySQL server versions before 8.0.21, so earlier versions (such as MySQL 5.7) require an 8.0 server upgrade to use it. (Bug #31875490) * On macOS, Connector/ODBC would not report an error if SQL_ATTR_PARAMSET_SIZE was set but not supported; instead the setting was ignored. (Bug #29862441, Bug #95608)On Behalf of Oracle/MySQL Release Engineering Team,Hery Ramilison Subject Views Written By Posted MySQL Connector/ODBC 8.0.23 has been released 2339 January 18, 2021 12:31PM Sorry, you can't reply to this topic. It has been closed. Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.31.4 MySQL Connector/ODBC
Not applicable SingleStore 7.3.9 server MariaDB JDBC driver version 2.7.3 Not applicable SingleStore 7.3.10 server MariaDB JDBC driver version 2.7.3 Not applicable SingleStore 7.3.11 server MariaDB JDBC driver version 2.7.3 Not applicable SingleStore 7.3.12 server MariaDB JDBC driver version 2.7.3 Not applicable SingleStore 7.3.13 server MariaDB JDBC driver version 2.7.3 Not applicable SingleStore 7.5.6 server MariaDB JDBC driver version 2.7.3 Not applicable SingleStore 7.5.7 server MariaDB JDBC driver version 2.7.3 Not applicable SingleStore 7.5.8 server MariaDB JDBC driver version 2.7.3 Not applicable SAP HANA 2.0 SP05 server SAP Hana JDBC driver version 2.0.SP5 Not applicable TIBCO Composite Server 8.4 Tibco Composite JDBC driver version 8.4.0 Not applicable Mongo BI Connector Server 2.14.3 MySQL JDBC driver version 5.1.47 Not applicable Vertica 11.0.0 server Vertica JDBC Driver 10.00.0100 Windows ODBC Driver Version 10.01 Linux-x86- ODBC Driver Version 9.2.1 Teradata 17.10 server Teradata JDBC driver version 17.10.00.14 Teradata JDBC driver version 17.10.00.17 Windows Teradata ODBC Driver Version 17.10.00.10 Linux-x86-Teradata ODBC Driver Version 17.10.00.10 IBM Db2 iSeries JT400 Server 7.4 JTOpen JDBC Driver 10.6 Windows DB2 Data Server Client 11.05.0400 Linux-x86 - DB2 Data Server Client 11.05.0400 IBM Db2 Z Server 12.1.5 IBM JCC JDBC driver version 4.29.24 Windows - DB2 Data Server Client 11.05.0400 Linux-x86- DB2 Data Server Client 11.05.0400 IBM Db2 11.5.6 server IBM JCC JDBC driver version 4.29.24 Windows DB2 Data Server Client 11.05.0400 Linux-x86-DB2 Data Server Client 11.05.0400 Dremio 17.0.0 Dremio JDBC Driver 17.0.0-202107060524010627-31b5222b Not applicable PostgreSQL Server 12.7 PostgreSQL JDBC driver version 42.2.23 Windows ODBC driver 13.01.000 Linux-x86-ODBC driver 13.02.000 PostgreSQL Server 12.8 PostgreSQL JDBC driver version 42.2.23 Windows ODBC driver 13.01.000 Linux-x86-ODBC driver 13.02.000 PostgreSQL Server 13.3 PostgreSQL JDBC driver version 42.2.19 PostgreSQL JDBC driver version 42.2.20 PostgreSQL JDBC driver version 42.2.21 PostgreSQL JDBC driver version 42.2.22 PostgreSQL JDBC driver version 42.2.23 Windows ODBC driver 13.01.000 Linux-x86-ODBC driver 13.02.000 PostgreSQL Server 13.4 PostgreSQL JDBC driver version 42.2.23 Windows ODBC driver 13.01.000 Linux-x86-ODBC driver 13.02.000 Progress DataDirect Autonomous REST JDBC driver 6.0.0.004291 Not applicable MySQL 8.0.24 server MySQL JDBC driver version 8.0.24 Windows-MySQL Connector/ODBC 8.0.26 Linux-x86-MySQL Connector/ODBC 8.0.24 MySQL 8.0.25 server MySQL JDBC driver version 8.0.25 Windows-MySQL Connector/ODBC 8.0.26. MySQL Connector/ODBC Developer Guide. Introduction to MySQL Connector/ODBC. Connector/ODBC Versions. General Information About ODBC and Connector/ODBC. Connector/ODBC Architecture. ODBC Driver Managers. Connector/ODBC Installation. Installing Connector/ODBC on Windows.
Install the ODBC Connector - Salesforce
Changes in MySQL Connector/ODBC 8.0.26 (2021-07-20, General Availability)Deprecation and Removal NotesFunctionality Added or ChangedBugs FixedDeprecation and Removal Notes The TLSv1.0 and TLSv1.1 connection protocols are now deprecated and support for them is subject to removal in a future Connector/ODBC version. Additionally, a NO_TLS_1_3 connection option was added. (WL #14543) Deprecated the NO_I_S connection option, an option to get metadata without the information_schema by using SHOW statements. Setting NO_I_S=1 with SQLConnect() or SQLDriverConnect() now return SQL_SUCCESS_WITH_INFO instead of SQL_SUCCESS, and they a deprecation warning retrievable by SQLGetDiagRec(). (WL #14586)Functionality Added or Changed Applications that use Connector/ODBC now can define query attribute metadata on a per-query basis, without the use of workarounds such as specially formatted comments included in query strings. (WL #14217) Added the ability to connect to MySQL server accounts that use the authentication_kerberos plugin, including support for user-less and password-less Kerberos authentications. Connector/ODBC utilizes the MySQL client library for this functionality. (WL #14441)Bugs Fixed Fixed help (documentation) links in the ODBC Driver GUI. (Bug #32880421) Improved Access/VB6 query attribute handling. (Bug #32813838) Attempting to update a row with an existing unique key would not emit a diagnostic error that reported the problem, such as "Duplicate Entry". (Bug #32763378, Bug #103287) Systems with both GTK versions 2 and 3 could cause the UnixGUI to unexpectedly halt when using the MySQL GUI module. Now, separate GTK modules exist for each version as the two can't co-exist in the same process. (Bug #32623180) A buffer overrun inside SQLColumns() caused Connector/ODBC to unexpectedly halt; memory management was optimized to prevent this problem. A workaround was to either use the NO_I_S=1 connection option or enable "Don't use INFORMATION_SCHEMA for metadata" from the ODBC Data Source Administrator. (Bug #32612467, Bug #102891) Fixed insert_params() code to use the __LOCALE_SET and __LOCALE_RESTORE macros rather than setlocale directly. (Bug #32610685, Bug #102871) Setting NO_CACHE=1 in the ODBC connection string would cause function errors to go undetected. (Bug #27499789, Bug #89542)Connect with MariaDB Connector/ODBC
Install MySQL on Windows using an account that has administrator rights. Otherwise, you may encounter problems with certain operations such as editing the PATH environment variable or accessing the Service Control Manager. When installed, MySQL does not need to be executed using a user with Administrator privileges. For a list of limitations on the use of MySQL on the Windows platform, see Section 2.3.7, “Windows Platform Restrictions”. In addition to the MySQL Server package, you may need or want additional components to use MySQL with your application or development environment. These include, but are not limited to: To connect to the MySQL server using ODBC, you must have a Connector/ODBC driver. For more information, including installation and configuration instructions, see MySQL Connector/ODBC Developer Guide.Note MySQL Installer installs and configures Connector/ODBC for you. To use MySQL server with .NET applications, you must have the Connector/NET driver. For more information, including installation and configuration instructions, see MySQL Connector/NET Developer Guide.Note MySQL Installer installs and configures MySQL Connector/NET for you. MySQL distributions for Windows can be downloaded from See Section 2.1.3, “How to Get MySQL”. MySQL for Windows is available in several distribution formats, detailed here. Generally speaking, you should use MySQL Installer. It contains more features and MySQL products than the older MSI, is simpler to use than the compressed file, and you need no additional tools to get MySQL up and running. MySQL Installer automatically installs MySQL Server and additional MySQL products, creates an options file, starts the server, and enables. MySQL Connector/ODBC Developer Guide. Introduction to MySQL Connector/ODBC. Connector/ODBC Versions. General Information About ODBC and Connector/ODBC. Connector/ODBC Architecture. ODBC Driver Managers. Connector/ODBC Installation. Installing Connector/ODBC on Windows. MySQL Connector/ODBC Developer Guide. Introduction to MySQL Connector/ODBC. Connector/ODBC Versions. General Information About ODBC and Connector/ODBC. Connector/ODBC Architecture. ODBC Driver Managers. Connector/ODBC Installation. Installing Connector/ODBC on Windows.5.6.5 Using Connector/ODBC with
Linux-x86-MySQL Connector/ODBC 8.0.25 MySQL 8.0.26 server MySQL JDBC driver version 8.0.26 Windows-MySQL Connector/ODBC 8.0.26 Linux-x86-MySQL Connector/ODBC 8.0.26 Oracle Server 19.10 Oracle JDBC Driver 19.10.0.0.0 Windows-Oracle Client Version 19.3.0 Linux-x86-Oracle Client Version 19.3.0 Oracle Server 19.11 Oracle JDBC Driver 19.11.0.0.0 Windows-Oracle Client Version 19.3.0 Linux-x86-Oracle Client Version 19.3.0.0 Oracle Server 19.12 Oracle JDBC Driver 19.12.0.0.0 Windows-Oracle Client Version 19.3.0 Linux-x86-Oracle Client Version 19.12.0.0 Oracle Server 21.1 Oracle JDBC Driver 21.1.0.0.0 Windows-Oracle Client Version 19.10 Linux-x86-Oracle Client Version 19.12 Oracle Server 21.3 Oracle JDBC Driver 21.1.0.0.0 Windows-Oracle Client Version 19.10 Linux-x86-Oracle Client Version 19.12 Netezza Server 7.2.1 Netezza JDBC driver 7.2.1.10 Windows-IBM Netezza ODBC driver Version 7.2.1.11 Linux-x86-IBM Netezza ODBC driver Version-7.2.1.11 SQL Server 2017 CU24 Microsoft SQL Server JDBC driver version 9.2.0 Windows-SQL Server Native Client 11 (SQLNCLI11.DLL) Windows-ODBC Driver for SQL Server 17 Linux-x86-DataDirect ODBC Driver 8.0.2 SQL Server 2019 CU10 Microsoft SQL Server JDBC driver version 9.2.0 Windows-Microsoft OLE DB Driver for SQL Server 18.6 (MSOLEDBSQL.DLL) Windows-ODBC Driver for SQL Server 17 Linux-x86-DataDirect ODBC Driver 8.0.2 SQL Server 2019 CU11 Microsoft SQL Server JDBC driver version 9.2.0 Microsoft SQL Server JDBC driver version 9.4.0 Windows-Microsoft ODBC Driver 17.05 for SQL Server Linux-x86-DataDirect Version 08.02 SQL Server 2019 CU12 Microsoft SQL Server JDBC driver version 9.2.0 Microsoft SQL Server JDBC driver version 9.4.0 Windows-Microsoft ODBC Driver 17.05 for SQL Server Linux-x86-DataDirect Version 08.02 Informix V14.10.XC5 server Informix JDBC driver version 4.50.JC4W1 Windows-Informix SDK 4.10 TC14 Linux-x86-Informix SDK 4.10 TC15 Informix V14.10.XC6 server Informix JDBC driver version 4.50.JC4W1 Windows-Informix SDK 4.10 TC14 Linux-x86-Informix SDK 4.10 TC15 Sybase ASE Server 16 SP3 SAP JConnect JDBC driver version 16.1.3 SAP JConnect JDBC driver version 20.0.0 Windows-SAP Client-Library 16.0 Linux-x86-SAP Client-Library 16.0 SP4 Sybase IQ Server 16.1 SP3 SAP JConnect JDBC driver version 16.1.3 Windows-SAP IQ ODBC driver 16.0SP11 Linux-x86-SAP IQ ODBC driver 16.0 SP11 Sybase IQ Server 16.1 SP4 SAP JConnect JDBC driver version 20.0.0 Windows-SAP IQ ODBC driver 16.0SP11 Linux-x86-SAP IQ ODBC driver 16.0 SP11 IBM Performance server/Netezza 11.2.0.0 server Netezza nzjdbc 11.2.0.0 Windows- ODBC driver 11.2.0.0 Linux-x86- ODBC driver 11.2.1.1Comments
Posted on December 4, 2023 by MariaDB is pleased to announce the immediate availability of MariaDB Connector/ODBC 3.1.20 and 3.2.1 RC, Connector/C 3.3.8 and 3.1.23, and Connector/Java 3.3.1.Download NowRelease Notes and ChangelogsMariaDB Connector/ODBC 3.2.1 RCMariaDB Connector/ODBC 3.2.1 Release NotesMariaDB Connector/ODBC 3.2.1 ChangelogNotable items in this release include:Support ODBC 3.8 standard. The driver is now compliant with ODBC standard version 3.8. Mainly that means implementation of SQLCancelHandle API function and SQL_ATTR_RESET_CONNECTION connection attribute support.Add Prepared Statement Cache to the Connector. The driver now uses cache for server side prepared statements, that allows not to re-prepare statements, but use them from the cache. Application can configure the cache with PSCACHESIZE and MAXCACHEKEY connection string options. The former sets the size of the cache, i.e. the number of statements that will be cached, the latter is the maximal size of the cache key, that effectively limits the maximum query length, that will be the value of MAXCACHEKEY – length of the current schema name – 1.Connector/ODBC is now available as RPM and DEB packages for selected platforms (RHEL, Ubuntu, Debian)Improved protocol resilience in case of resultset streaming. In version 3.1 if the resultset streaming is used, it will block the connection, and the driver will return error on any new query. The 3.2.1 driver in this case will cache the rest of currently streamed resultset, and execute the new query without errorFixes for various issues.MariaDB Connector/ODBC 3.1.20MariaDB Connector/ODBC 3.1.20 Release NotesMariaDB Connector/ODBC 3.1.20 ChangelogNotable items in this release include:Add support of MADB_OPT_FLAG_NO_BIGINT option. Some classic applications do not support SQLBIGINT option. This option makes the column that normally would be of SQLBIGINT type to look like it is of SQLINTEGER typeConnector/ODBC is now available as RPM and DEB packages for selected platforms (RHEL, Ubuntu, Debian)Fixes for various issues.MariaDB Connector/C 3.3.8MariaDB Connector/C 3.3.8 Release NotesMariaDB Connector/C 3.3.8 ChangelogNotable items in this release include:Fixes for various issues.MariaDB Connector/C 3.1.23MariaDB Connector/C 3.1.23 Release NotesMariaDB Connector/C 3.1.23 ChangelogNotable items in this release include:Fixes for various issues.MariaDB Connector/Java 3.3.1MariaDB Connector/Java 3.3.1 Release NotesMariaDB Connector/Java 3.3.1 ChangelogNotable items in this release include:Fixes for various issues.See the release notes and changelogs for more details and visit mariadb.com/downloads/connectors to download.
2025-03-31These solutions include Simba Gateway connectivity as a service, standalone data connector, Simba SDK, as well as managed services with custom-built connectors via rigorous testing and authentication. For instance, the Simba BigQuery ODBC connector allows you to get data from BigQuery to your BI Tool.Seamlessly Integrate your Data into BigQuery With continuous real-time data movement, Hevo allows you to integrate your data sources and load it to the destination of your choice with a no-code, easy-to-setup interface. Try our 14-day full-feature access free trial! Get Started with Hevo for FreeConfiguration of BigQuery ODBC ConnectorStep 1: Install and Download Simba Google BigQuery ODBC ConnectorStep 2: License AllocationStep 3: Configuring Simba Google BigQuery ODBC ConnectorStep 1: Install and Download Simba Google BigQuery ODBC ConnectorStep 1: Visit the BigQuery ODBC JDBC Drivers page and download the connector for your Operating System. For this article, the windows version is selected. After downloading the MSI File, open it.Step 2: The BigQuery ODBC Connector Setup window will pop up on your screen. Click on the Next button. Step 3: For accepting the licensing agreement, click on the Next button.Step 4: Provide the location on your system where you want to install the connector and click on the Next button. Step 5: Finally, click on the Install button. After the BigQuery ODBC connector is completely installed, click on the Finish button to close the setup window. Step 2: License AllocationAfter you have submitted the form, the driver’s license is sent to your email. Ensure that the file is stored in the /lib/ folder underneath where the connector has been installed.Step 3: Configuring Simba Google BigQuery ODBC ConnectorStep 1: In your Windows system, click on the SEARCH and navigate to ODBC Administrator. Step 2: In the ODBC Administrator window, click on the System DSN tab. Search and click
2025-04-23To use MySQL Connector, you must download and install the JDBC and ODBC drivers on your Windows or Linux machine where the Secure Agent is installed.Before you use MySQL Connector, complete the following tasks:1Install the MySQL JDBC driver. 2Install the MySQL ODBC driver. Installing MySQL JDBC driverBefore you use MySQL Connector, install the MySQL JDBC driver and MySQL ODBC driver on the Windows or Linux machine where you installed the Secure Agent.Perform the following steps to install the MySQL JDBC drivers on Windows or Linux:2Select the required Product Version.3Select the Operating System as Platform Independent.4Download the .zip or .tar file based on your Windows or Linux system.5Extract the downloaded file and copy the mysql-connector-java-.jar file.6Paste the mysql-connector-java-.jar file in the following directory on the Secure Agent machine:- On Windows: \apps\Data_Integration_Server\ext\drivers- On Linux: /apps/Data_Integration_Server/ext/drivers7Set the MySQL_JDBC_DRIVER_JARNAME parameter to mysql-connector-java-.jar for the Data Integration Server service in the Secure Agent's system configuration details in Administrator.8Restart the Secure Agent.Installing MySQL ODBC driverBefore you use MySQL Connector, you must install the MySQL ODBC driver on the Windows or Linux machine where you installed the Secure Agent.Installing MySQL ODBC driver on WindowsPerform the following steps to install the MySQL ODBC driver on Windows:2Select the required Product Version.3Select the Operating System as Microsoft Windows.4Select the OS Version as Windows (x86, 64-bit).5Download the ZIP Archive mysql-connector-odbc-noinstall--winx64.zip file.Note: Do not use the MSI installer because it removes the existing MySQL ODBC driver versions from the system.6Extract the .zip file. 7Open the Command Prompt as an administrator and navigate to the extracted .zip file location. 8Run the following command in the command prompt: Install.bat After you install the MySQL ODBC driver, check if the installed MySQL ODBC Unicode Driver name appears as one of the available ODBC drivers under the ODBC Data Source Administrator (64-bit) dialog box:The following image shows the MySQL ODBC 8.0 Unicode Driver driver name in the ODBC Data Source Administrator (64-bit) dialog box when you try to create a new data source:Installing MySQL ODBC driver on LinuxPerform the following steps to install the MySQL ODBC driver on Linux:2Select the required Product Version.3Select the Operating System as Linux- Generic.4Select the OS Version as All.5Download the Linux - Generic (glibc 2.12) (x86, 64-bit) file.6Extract the downloaded file to a local directory in your system. Note: When you extract the file, ensure that you copy all files from the downloaded driver package.7Edit the /odbcinst.ini file and add the following values:[MySQL ODBC 8.0 Unicode Driver]Description = ODBC for MySQLDriver = /lib/libmyodbc8w.soSetup = /lib/libmyodbc8w.soFileUsage = 1In the Driver and Setup fields, you must specify the file path of the libmyodbc8w.so file that you extracted to the local directory in your system.Prerequisites to configure SSL with serverless runtime environmentYou can use the serverless runtime environment with MySQL Connector to connect to an SSL-enabled MySQL database.Before you configure a secure MySQL connection using the serverless runtime environment, complete the following prerequisite tasks to add the SSL certificates to the serverless runtime location:1Create the following structure for the serverless agent configuration in AWS
2025-04-13MySQL Connector/ODBC 5.3.9, a new version of the ODBC driver forthe MySQL database management system, has been released.The available downloads include both a Unicode driver and an ANSIdriver based on the same modern codebase. Please select the driver typeyou need based on the type of your application – Unicode or ANSI.Server-side prepared statements are enabled by default. It is suitablefor use with any MySQL version from 5.5.This is the fourth release of the MySQL ODBC driver conforming to theODBC 3.8 specification. It contains implementations of key 3.8 features,including self-identification as a ODBC 3.8 driver, streaming of outputparameters (supported for binary types only), and support of theSQL_ATTR_RESET_CONNECTION connection attribute (for the Unicode driveronly).Also, Connector/ODBC 5.3 introduces a GTK+-based setup libraryproviding a GUI DSN setup dialog on some Unix-based systems, currentlyincluded in the Debian 7/8/9, EL6/OL6, EL7/OL7 (64-bit only), Fedora 24/25/26,FreeBSD 10/11, SLES 12, Ubuntu 14/16/17 packages. Other newfeatures in the 5.3 driver are FileDSN and Bookmarks support.The release is now available in source and binary form for a number ofplatforms from our download pages at information on installing, please see the documentation at in MySQL Connector/ODBC 5.3.9 (2017-07-24, GeneralAvailability)Functionality Added or ChangedWhen compiling Connector/ODBC on Windows platforms, it can now be linked statically (equivalent to the /MT compiler option in Visual Studio) or dynamically (equivalent to the /MD compiler option in Visual Studio) to the Visual C++ runtime. The default option is to link dynamically; if you want to link statically. set the new CMake option, STATIC_MSVCRT, to true. Another new CMake option, WITH_NODEFAULTLIB, has been introduced for specifying the Visual C++ runtime you want to link Connector/ODBC to when using mixed link types (that is, when link type to the Visual C++ runtime differs for Connector/ODBC and the MySQL client library it links to). See Building Connector/ODBC from a Source
2025-04-03