Download sql server odbc driver

Author: m | 2025-04-24

★★★★☆ (4.1 / 2649 reviews)

sq meter calculator

To download ODBC driver - Download ODBC Driver for SQL Server - ODBC Driver for SQL Server

panzer ellite

Download ODBC Driver for SQL Server - ODBC Driver for SQL Server

Wikipedia.Creating an ODBC Data SourceI'm going to assume that you have 1) MapInfo Pro installed and 2) a database system installed too. In my example, I will use PostgreSQL with PostGIS. The steps would be similar for another database system such as MS SQL Server.First, you need to download and install the specific PDBC driver for the database system. For PostgreSQL with PostGIS, you can find the drivers here: odbc.postgresql.org. For MS SQL Server, this is a good starting place: Download ODBC Driver for SQL Server.If you look in the latest Release Notes document, you can find a list of ODBC drivers that MapInfo Pro supports. These are drivers that have been tested with MapInfo Pro. We may also support newer/older versions but we can't be sure as we have tested these. As MapInfo Pro is a 64-bit application, you also need to ensure that you install a 64-bit driver.These are the supported drivers for MapInfo Pro v2021.1:Microsoft Access ODBC (64-bit)Microsoft SQL Server 2019Microsoft SQL Server 2017Microsoft SQL Server 2016Microsoft SQL Server 2012 QFE Native Client v11 (64-bit)PostgreSQL Unicode and ANSI ODBC driver 13.01 (64-bit)FDO toolkit 3.8 (used by SQLite and installed with MapInfo Pro)Oracle Instant Client 19.11 (64-bit)Microsoft ODBC Driver for SQL Server 17.8You may also have to reach out to your IT department to get the ODBC driver installed on your system.Once the ODBC Driver has been installed, it's time to create an ODBC Data Source. You can create this directly from within MapInfo Pro or from the If you are connecting to a SQL Server database on localhost you do not need to setup any additional libraries to use SQLines Data tool as they are supplied with Microsoft SQL Server.If you need to connect to a remote SQL Server database, you need to have SQL Server ODBC Driver (since SQL Server 2022) or Native Client (deprecated since SQL Server 2022) installed in your local system. Check if you already have SQL Server client libraries (most Windows systems already have them):Windows: %SYSTEMROOT%\System32\ (usually c:\Windows\System32) msodbcsql17.dll or msodbcsql18.dll- SQL Server 2022 or later sqlncli11.dll - SQL Server 2016, 2014 and 2012 sqlncli10.dll - SQL Server 2008 sqlsrv32.dll - SQL Server 2000Linux:/opt/microsoft//opt/microsoft/msodbcsql17/lib64/libmsodbcsql-17.7.so.2.1 If SQL Server client is not available, go to SQL Server download page to download a SQL Server ODBC Driver or Native Client. Note that SQL Server 2012 Native Client (sqlncli11.dll) is used with Microsoft SQL Server 2016, 2014 and 2012.Installing SQL Server ODBC Driver on LinuxFollow instructions provided on Microsoft site, search - Install the Microsoft ODBC driver for SQL Server (Linux)For example, for Red Hat Linux version 6 and ODBC Driver 17 for SQL Server curl > /etc/yum.repos.d/mssql-release.repo # Install driver and its dependency unixODBC 2.3.7 sudo ACCEPT_EULA=Y yum install -y msodbcsql17To connect to SQL Server, set both -sql_lib and -sql_driver command line or sqldata.cfg options to specify the library location and driver name, for example: -sql_lib=/opt/microsoft/msodbcsql17/lib64/libmsodbcsql-17.7.so.2.1 -sql_driver="ODBC Driver 17 for SQL Server"Troubleshoot Connection to SQL ServerTroubleshooting connection errors for SQL Server.Named Pipes Provider: Could not open a connection to SQL Server [53]Error 53 may mean you specified a bad network path. Check if the specified host name exists.Named Pipes Provider: Could not open a connection to SQL Server [2]Error 2 may mean you did not specified the instance name. Specify correct server_host\instance to connect to SQL Server.SQL Server Network Interfaces: Error Locating Server/Instance Specified [xFFFFFFFF]If you can get the following error message:Check if you specified the valid server and instance name, for example, localhost\SQLEXPRESS.

Download ODBC Driver for SQL Server - ODBC Driver for SQL Server

@zormaxo @ShadelessFoxI found a way to get DBeaver connected to localdb using ODBC, which persists across the localdb pipe name changes. You only need to have an ODBC Driver -- for SQL Server installed. Check it out:First verify you have a SQL Server ODBC driver installed. To do this, go to the Windows Control Panel >> Administrative Tools >> ODBC Data Sources (x64) >> "Drivers" Tab. The driver I have on my machine is ODBC Driver 17 for SQL Server. If you don't have the driver, you can download it here: driver will look like this:Once you have the ODBC driver, go to DBeaver and create a new connection by choosing the "ODBC" option, and click Next:Enter in the connection string as follows. Be sure to change the ODBC driver version number to the one that you have installed, as well as the localdb instance name:Driver={ODBC Driver 17 for SQL Server};Server=(localdb)\mssqllocaldbClick "Test Connection" and see if it works. Hopefully you don't have any problems. Let me know if this works well for you.. To download ODBC driver - Download ODBC Driver for SQL Server - ODBC Driver for SQL Server Download ODBC Driver for SQL Server - ODBC Driver for SQL Server

Download ODBC Driver for SQL Server - ODBC Driver for SQL Server

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.1 Skip to main content This browser is no longer supported. Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support. Download Microsoft Edge More info about Internet Explorer and Microsoft Edge Read in English Read in English Edit Share via Profiling ODBC Driver Performance (ODBC) Article01/10/2024 In this article -->Applies to: SQL Server Azure SQL Database Azure SQL Managed Instance Azure Synapse Analytics Analytics Platform System (PDW)The SQL Server ODBC driver has two driver-specific options for profiling the performance of the driver.The SQL Server ODBC driver can log performance statistics in file. The log file is a tab-delimited file that can be analyzed in any spreadsheet supporting tab-delimited files, such as Microsoft Excel.The driver can also log long-running queries (queries that do not get a response from the server in a specified length of time). These queries can later be analyzed by programmers and database administrators.In This SectionProfile Driver Performance Data (ODBC)Log Long-Running Queries (ODBC)See AlsoODBC How-to Topics --> Feedback Was this page helpful? Provide product feedback | Get help at Microsoft Q&A Additional resources In this article

Download ODBC Driver for SQL Server - ODBC Driver for SQL Server

Version autre que l’anglais et que vous souhaitez voir le contenu le plus à jour, sélectionnez Read in English en haut de cette page. Vous pouvez télécharger différentes langues à partir du site en version anglaise (États-Unis) en sélectionnant Langues disponibles.Langues disponiblesCette version de Microsoft ODBC Driver for SQL Server peut être installée dans les langues suivantes :Pilote ODBC Microsoft 18.4.1.1 pour SQL Server (x64) : Chinois (simplifié) | Chinois (traditionnel) | Anglais (États-Unis) | Français | Allemand | Italien | Japonais | Coréen | Portugais (Brésil) | Russe | EspagnolPilote ODBC Microsoft 18.4.1.1 pour SQL Server (x86) : Chinois (simplifié) | Chinois (traditionnel) | Anglais (États-Unis) | Français | Allemand | Italien | Japonais | Coréen | Portugais (Brésil) | Russe | EspagnolPilote ODBC Microsoft 18.4.1.1 pour SQL Server (ARM64) : Chinois (simplifié) | Chinois (traditionnel) | Anglais (États-Unis) | Français | Allemand | Italien | Japonais | Coréen | Portugais (Brésil) | Russe | EspagnolVersion 17La version 17.10.5 est la dernière version en disponibilité générale (GA) du pilote 17.x. Si vous possédez une version antérieure du pilote ODBC Microsoft 17 for SQL Server, le processus d'installation de la version 17.10.6 effectue une mise à niveau vers la version 17.10.6.Télécharger Microsoft ODBC Driver 17 for SQL Server (x64)Télécharger Microsoft ODBC Driver 17 for SQL Server (x86)Numéro de version : 17.10.6.1Publication : 9 avril 2024Cette version de Microsoft ODBC Driver for SQL Server peut être installée dans les langues suivantes :Pilote ODBC Microsoft 17.10.6.1 pour SQL Server (x64) : Chinois (simplifié) | Chinois (traditionnel) | Anglais (États-Unis) | Français | Allemand | Italien | Japonais | Coréen | Portugais (Brésil) | Russe | EspagnolPilote ODBC Microsoft 17.10.6.1 pour SQL Server (x86) : Chinois (simplifié) | Chinois (traditionnel) | Anglais (États-Unis) | Français | Allemand | Italien | Japonais | Coréen | Portugais (Brésil) | Russe | EspagnolNotes de publication pour WindowsPour plus d’informations sur cette version de Windows, consultez les notes de publication de Windows.Versions précédentes pour WindowsPour télécharger les versions précédentes pour Windows, consultez Versions précédentes de Microsoft ODBC Driver for SQL Server.Télécharger pour Linux et macOSMicrosoft ODBC Driver

Download ODBC Driver for SQL Server - ODBC Driver for SQL Server

Passer au contenu principal Ce navigateur n’est plus pris en charge. Effectuez une mise à niveau vers Microsoft Edge pour tirer parti des dernières fonctionnalités, des mises à jour de sécurité et du support technique. Télécharger un pilote ODBC pour SQL Server Article01/02/2025 Dans cet article -->S’applique à : SQL Server Base de données Azure SQL Azure SQL Managed Instance Azure Synapse Analytics Analytics Platform System (PDW) Point de terminaison d'analyse SQL dans Microsoft Fabric Entrepôt dans Microsoft Fabric Base de données SQL dans Microsoft FabricMicrosoft ODBC Driver for SQL Server est une bibliothèque de liens dynamiques (DLL) unique qui prend en charge l’exécution des applications utilisant les API en code natif pour se connecter à SQL Server. Utilisez Microsoft ODBC Driver 18 for SQL Server pour créer de nouvelles applications ou améliorer des applications existantes qui doivent tirer parti des fonctionnalités plus récentes de SQL Server.Téléchargement pour WindowsLe programme d’installation redistribuable pour Microsoft ODBC Driver 18 for SQL Server installe les composants clients, qui sont nécessaires au moment de l’exécution pour tirer parti des fonctionnalités les plus récentes de SQL Server. Il installe éventuellement les fichiers d’en-tête nécessaires au développement d’une application qui utilise l’API ODBC. À partir de la version 17.4.2, le programme d’installation comprend et installe également la Bibliothèque d’authentification Microsoft Active Directory (ADAL.dll).La version 18.4.1.1 constitue la dernière version en disponibilité générale (GA). Si vous possédez une version antérieure de Microsoft pilote ODBC 18 pour SQL Server, le processus d'installation de la version 18.4.1.1 effectue une mise à niveau vers la version 18.4.1.1. Microsoft ODBC Driver 18 for SQL Server peut être installé côte à côte avec Microsoft ODBC Driver 17 for SQL Server.Télécharger Microsoft ODBC Driver 18 for SQL Server (x64)Télécharger Microsoft ODBC Driver 18 for SQL Server (x86)Téléchargement de Microsoft pilote ODBC 18 for SQL Server (ARM64)RemarqueUtilisez le programme d’installation x86 pour les machines 32 bits ou le programme d’installation x64 pour installer les pilotes 64 bits et 32 bits sur une machine 64 bits.Informations sur la versionNuméro de version : 18.4.1.1Publication : 31 juillet 2024RemarqueSi vous accédez à cette page à partir d’une. To download ODBC driver - Download ODBC Driver for SQL Server - ODBC Driver for SQL Server

Download ODBC Driver for SQL Server - ODBC Driver for SQL Server

Devart ODBC drivers support a wide range of databases, including Oracle, MySQL, PostgreSQL, SQL Server, and SQLite.ODBC drivers help migration tools access data, send SQL queries to the source database, retrieve the results, and then insert or update the data with the mapped data types in the target database, allowing users to efficiently migrate MySQL to SQL Server. Install and configure ODBC driver for MySQLFor data conversion from a MySQL database to a SQL Server database, first, download the ODBC Driver for MySQL on the computer where you want to perform data migration.Once done, go to the Downloads folder and double-click the DevartODBCMySQL.exe setup file to install the driver on your computer. In the Setup wizard, go through all the installation steps and click Finish to close the wizard.Next, you must set up a data source name (DSN) for the ODBC driver. To do this, open the ODBC Data Source Administrator utility by typing ODBC Data Sources in the search bar. Select the 32-bit or 64-bit version of the ODBC Data Source Administrator utility, depending on your machine.In the ODBC Data Source Administrator window, you can create a User DSN, which means the DSN will be accessible to the user who created it in the system, or a System DSN, meaning the DSN will be accessible to anyone logged in. To proceed, on the User DSN or System DSN tab, click Add to create a new data source. In the dialog that opens, select Devart ODBC Driver for MySQL and click Finish.This will open the Devart ODBC Driver for MySQL Configuration dialog, where you need to specify the required details, including the data source name, MySQL server, username, password, and target database. The default port number is 3306. You can change it in the corresponding field. Note that the data source name you specify will subsequently appear in the list of data source names in dbForge Data Pump for SQL Server.If you click Test Connection, you can verify that the connection has been properly configured. If the configuration is correct, the notification window will appear. Click OK to close it. To save the DSN settings, click OK.The driver you’ve installed will appear on the corresponding DSN tab. Click OK to save the changes and close the dialog.Overview of Data Pump for SQL ServerFor data migration from MySQL to SQL Server, we’ll use dbForge Data Pump for SQL Server, which is a part of the SQL Tools pack. Data Pump is a SQL Server Management Studio (SSMS) add-in aimed to facilitate data migration from third-party databases to SQL Server. The tool also supports data import/export in popular data formats, including Excel, CSV, XML, JSON, Text, MS Access, etc. Data Pump allows saving templates for repetitive export scenarios or automating and scheduling export tasks using the command line.Convert your data from MySQL to SQL Server effortlesslyEverything has been prepared, so that we can start with data conversion from MySQL to SQL Server. First, let’s see the data we want to transfer from

Comments

User5754

Wikipedia.Creating an ODBC Data SourceI'm going to assume that you have 1) MapInfo Pro installed and 2) a database system installed too. In my example, I will use PostgreSQL with PostGIS. The steps would be similar for another database system such as MS SQL Server.First, you need to download and install the specific PDBC driver for the database system. For PostgreSQL with PostGIS, you can find the drivers here: odbc.postgresql.org. For MS SQL Server, this is a good starting place: Download ODBC Driver for SQL Server.If you look in the latest Release Notes document, you can find a list of ODBC drivers that MapInfo Pro supports. These are drivers that have been tested with MapInfo Pro. We may also support newer/older versions but we can't be sure as we have tested these. As MapInfo Pro is a 64-bit application, you also need to ensure that you install a 64-bit driver.These are the supported drivers for MapInfo Pro v2021.1:Microsoft Access ODBC (64-bit)Microsoft SQL Server 2019Microsoft SQL Server 2017Microsoft SQL Server 2016Microsoft SQL Server 2012 QFE Native Client v11 (64-bit)PostgreSQL Unicode and ANSI ODBC driver 13.01 (64-bit)FDO toolkit 3.8 (used by SQLite and installed with MapInfo Pro)Oracle Instant Client 19.11 (64-bit)Microsoft ODBC Driver for SQL Server 17.8You may also have to reach out to your IT department to get the ODBC driver installed on your system.Once the ODBC Driver has been installed, it's time to create an ODBC Data Source. You can create this directly from within MapInfo Pro or from the

2025-04-07
User2215

If you are connecting to a SQL Server database on localhost you do not need to setup any additional libraries to use SQLines Data tool as they are supplied with Microsoft SQL Server.If you need to connect to a remote SQL Server database, you need to have SQL Server ODBC Driver (since SQL Server 2022) or Native Client (deprecated since SQL Server 2022) installed in your local system. Check if you already have SQL Server client libraries (most Windows systems already have them):Windows: %SYSTEMROOT%\System32\ (usually c:\Windows\System32) msodbcsql17.dll or msodbcsql18.dll- SQL Server 2022 or later sqlncli11.dll - SQL Server 2016, 2014 and 2012 sqlncli10.dll - SQL Server 2008 sqlsrv32.dll - SQL Server 2000Linux:/opt/microsoft//opt/microsoft/msodbcsql17/lib64/libmsodbcsql-17.7.so.2.1 If SQL Server client is not available, go to SQL Server download page to download a SQL Server ODBC Driver or Native Client. Note that SQL Server 2012 Native Client (sqlncli11.dll) is used with Microsoft SQL Server 2016, 2014 and 2012.Installing SQL Server ODBC Driver on LinuxFollow instructions provided on Microsoft site, search - Install the Microsoft ODBC driver for SQL Server (Linux)For example, for Red Hat Linux version 6 and ODBC Driver 17 for SQL Server curl > /etc/yum.repos.d/mssql-release.repo # Install driver and its dependency unixODBC 2.3.7 sudo ACCEPT_EULA=Y yum install -y msodbcsql17To connect to SQL Server, set both -sql_lib and -sql_driver command line or sqldata.cfg options to specify the library location and driver name, for example: -sql_lib=/opt/microsoft/msodbcsql17/lib64/libmsodbcsql-17.7.so.2.1 -sql_driver="ODBC Driver 17 for SQL Server"Troubleshoot Connection to SQL ServerTroubleshooting connection errors for SQL Server.Named Pipes Provider: Could not open a connection to SQL Server [53]Error 53 may mean you specified a bad network path. Check if the specified host name exists.Named Pipes Provider: Could not open a connection to SQL Server [2]Error 2 may mean you did not specified the instance name. Specify correct server_host\instance to connect to SQL Server.SQL Server Network Interfaces: Error Locating Server/Instance Specified [xFFFFFFFF]If you can get the following error message:Check if you specified the valid server and instance name, for example, localhost\SQLEXPRESS.

2025-04-11
User7731

@zormaxo @ShadelessFoxI found a way to get DBeaver connected to localdb using ODBC, which persists across the localdb pipe name changes. You only need to have an ODBC Driver -- for SQL Server installed. Check it out:First verify you have a SQL Server ODBC driver installed. To do this, go to the Windows Control Panel >> Administrative Tools >> ODBC Data Sources (x64) >> "Drivers" Tab. The driver I have on my machine is ODBC Driver 17 for SQL Server. If you don't have the driver, you can download it here: driver will look like this:Once you have the ODBC driver, go to DBeaver and create a new connection by choosing the "ODBC" option, and click Next:Enter in the connection string as follows. Be sure to change the ODBC driver version number to the one that you have installed, as well as the localdb instance name:Driver={ODBC Driver 17 for SQL Server};Server=(localdb)\mssqllocaldbClick "Test Connection" and see if it works. Hopefully you don't have any problems. Let me know if this works well for you.

2025-04-09
User7693

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.1

2025-03-25
User7409

Skip to main content This browser is no longer supported. Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support. Download Microsoft Edge More info about Internet Explorer and Microsoft Edge Read in English Read in English Edit Share via Profiling ODBC Driver Performance (ODBC) Article01/10/2024 In this article -->Applies to: SQL Server Azure SQL Database Azure SQL Managed Instance Azure Synapse Analytics Analytics Platform System (PDW)The SQL Server ODBC driver has two driver-specific options for profiling the performance of the driver.The SQL Server ODBC driver can log performance statistics in file. The log file is a tab-delimited file that can be analyzed in any spreadsheet supporting tab-delimited files, such as Microsoft Excel.The driver can also log long-running queries (queries that do not get a response from the server in a specified length of time). These queries can later be analyzed by programmers and database administrators.In This SectionProfile Driver Performance Data (ODBC)Log Long-Running Queries (ODBC)See AlsoODBC How-to Topics --> Feedback Was this page helpful? Provide product feedback | Get help at Microsoft Q&A Additional resources In this article

2025-04-23
User4557

Version autre que l’anglais et que vous souhaitez voir le contenu le plus à jour, sélectionnez Read in English en haut de cette page. Vous pouvez télécharger différentes langues à partir du site en version anglaise (États-Unis) en sélectionnant Langues disponibles.Langues disponiblesCette version de Microsoft ODBC Driver for SQL Server peut être installée dans les langues suivantes :Pilote ODBC Microsoft 18.4.1.1 pour SQL Server (x64) : Chinois (simplifié) | Chinois (traditionnel) | Anglais (États-Unis) | Français | Allemand | Italien | Japonais | Coréen | Portugais (Brésil) | Russe | EspagnolPilote ODBC Microsoft 18.4.1.1 pour SQL Server (x86) : Chinois (simplifié) | Chinois (traditionnel) | Anglais (États-Unis) | Français | Allemand | Italien | Japonais | Coréen | Portugais (Brésil) | Russe | EspagnolPilote ODBC Microsoft 18.4.1.1 pour SQL Server (ARM64) : Chinois (simplifié) | Chinois (traditionnel) | Anglais (États-Unis) | Français | Allemand | Italien | Japonais | Coréen | Portugais (Brésil) | Russe | EspagnolVersion 17La version 17.10.5 est la dernière version en disponibilité générale (GA) du pilote 17.x. Si vous possédez une version antérieure du pilote ODBC Microsoft 17 for SQL Server, le processus d'installation de la version 17.10.6 effectue une mise à niveau vers la version 17.10.6.Télécharger Microsoft ODBC Driver 17 for SQL Server (x64)Télécharger Microsoft ODBC Driver 17 for SQL Server (x86)Numéro de version : 17.10.6.1Publication : 9 avril 2024Cette version de Microsoft ODBC Driver for SQL Server peut être installée dans les langues suivantes :Pilote ODBC Microsoft 17.10.6.1 pour SQL Server (x64) : Chinois (simplifié) | Chinois (traditionnel) | Anglais (États-Unis) | Français | Allemand | Italien | Japonais | Coréen | Portugais (Brésil) | Russe | EspagnolPilote ODBC Microsoft 17.10.6.1 pour SQL Server (x86) : Chinois (simplifié) | Chinois (traditionnel) | Anglais (États-Unis) | Français | Allemand | Italien | Japonais | Coréen | Portugais (Brésil) | Russe | EspagnolNotes de publication pour WindowsPour plus d’informations sur cette version de Windows, consultez les notes de publication de Windows.Versions précédentes pour WindowsPour télécharger les versions précédentes pour Windows, consultez Versions précédentes de Microsoft ODBC Driver for SQL Server.Télécharger pour Linux et macOSMicrosoft ODBC Driver

2025-04-02

Add Comment