title | description | author | ms.author | ms.date | ms.service | ms.subservice | ms.topic |
---|---|---|---|---|---|---|---|
System Requirements, Installation, and Driver Files |
This article describes the system requirements for the Microsoft ODBC Driver for SQL Server. |
David-Engel |
v-davidengel |
08/08/2022 |
sql |
connectivity |
conceptual |
System requirements, installation, and driver files
[!INCLUDEDriver_ODBC_Download]
This article discusses the ODBC drivers that connect to SQL Server.
SQL version compatibility
Compatibility indicates that a driver was tested for compatibility against existing releases of SQL at the time of the driver’s release. SQL Server releases generally try to maintain backwards compatibility with existing client drivers. But new features in SQL Server releases may not be available with older client drivers.
Database version → ↓ Driver Version |
Azure SQL Database | Azure Synapse Analytics | Azure SQL Managed Instance | SQL Server 2019 | SQL Server 2017 | SQL Server 2016 | SQL Server 2014 | SQL Server 2012 | SQL Server 2008 R2 | SQL Server 2008 | SQL Server 2005 |
---|---|---|---|---|---|---|---|---|---|---|---|
18.1 | Yes | Yes | Yes | Yes | Yes | Yes | Yes | ||||
18.0 | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | |||
17.10 | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | |||
17.9 | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | |||
17.8 | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | |||
17.7 | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | |||
17.6 | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | |||
17.5 | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | |||
17.4 | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | |||
17.3 | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | |
17.2 | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | ||
17.1 | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | ||
17.0 | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | ||
13.1 | Yes | Yes | Yes | Yes | Yes | Yes | |||||
13 | Yes | Yes | Yes | Yes | Yes | ||||||
11 | Yes | Yes | Yes | Yes | Yes |
Connection string details
The driver name that you specify in a connection string is one of the following:
ODBC Driver 11 for SQL Server
ODBC Driver 13 for SQL Server
(for both 13 and 13.1)ODBC Driver 17 for SQL Server
ODBC Driver 18 for SQL Server
Supported operating systems
The following matrix indicates driver version support for Windows operating system versions:
Operating system → ↓ Driver version |
Windows Server 2022 | Windows Server 2019 | Windows Server 2016 | Windows Server 2012 R2 | Windows Server 2012 | Windows Server 2008 R2 | Windows 11 | Windows 10 | Windows 8.1 | Windows 7 | Windows Vista SP2 |
---|---|---|---|---|---|---|---|---|---|---|---|
18.1 | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | |||
18.0 | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | |||
17.10 | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | |||
17.9 | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | |||
17.8 | Yes | Yes | Yes | Yes | Yes | Yes | |||||
17.7 | Yes | Yes | Yes | Yes | Yes | Yes | |||||
17.6 | Yes | Yes | Yes | Yes | Yes | Yes | |||||
17.5 | Yes | Yes | Yes | Yes | Yes | Yes | |||||
17.4 | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | |||
17.3 | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | |||
17.2 | Yes | Yes | Yes | Yes | Yes | Yes | Yes | ||||
17.1 | Yes | Yes | Yes | Yes | Yes | Yes | Yes | ||||
17.0 | Yes | Yes | Yes | Yes | Yes | Yes | Yes | ||||
13.1 | Yes | Yes | Yes | Yes | Yes | Yes | Yes | ||||
13 | Yes | Yes | Yes | Yes | |||||||
11 | Yes | Yes | Yes | Yes |
Installing Microsoft ODBC Driver for SQL Server
The driver is installed when you run msodbcsql.msi
from one of the Downloads for Windows.
[!NOTE]
For those who have Driver 17.1.0.1 or below installed, it is recommended that it be uninstalled manually prior to installing the newer version of the Driver.
Side-by-side with Native Client
The driver can be installed side-by-side with [!INCLUDEssNoVersion] Native Client. Major versions of the driver (11, 13, 17, 18) can all be installed side-by-side with each other, as well.
When you invoke msodbcsql.msi
, only the client components are installed by default. The client components are files that support running an application that was developed using the driver. To install the SDK components, specify ADDLOCAL=ALL
on the command line. Here is an example.
msiexec /i msodbcsql.msi ADDLOCAL=ALL
End-user license
Specify IACCEPTMSODBCSQLLICENSETERMS=YES
to accept the terms of the end-user license if you use the /passive
, /qn
, /qb
, or /qr
option to install. This option must be specified in all uppercase letters. Here is an example.
msiexec /quiet /passive /qn /i msodbcsql.msi IACCEPTMSODBCSQLLICENSETERMS=YES ADDLOCAL=ALL
Silent uninstall
The following example shows how to perform a silent uninstall.
msiexec /quiet /passive /qn /uninstall msodbcsql.msi
Indicate dependency
When an application uses the driver, the application should indicate that it depends on the driver through the install option APPGUID
. this indication enables the driver installer to report dependent applications before uninstalling. To specify a dependency on the driver, set the APPGUID
command-line parameter to your product code when silently installing the driver. A product code must be created when using Microsoft Installer to bundle your application setup program. Here is an example.
msiexec /i msodbcsql.msi APPGUID={ <Your dependent application's APPGUID> }
Command-line tools: sqlcmd.exe and bcp.exe
The bcp.exe
and sqlcmd.exe
tools for use with the driver can be downloaded at Microsoft Command Line Utilities 11 for SQL Server, Microsoft Command Line Utilities 13 for SQL Server, or Microsoft Command Line Utilities 13.1 for SQL Server. The driver is a prerequisite to install sqlcmd.exe
and bcp.exe
.
bcp.exe
and sqlcmd.exe
are installed in the 110Tools
subfolder of %PROGRAMFILES%Microsoft SQL ServerClient SDKODBC
for version 11, and 130Tools
for 13 and 13.1.
An application that uses BCP functions must specify the driver from the same version which shipped with the header file and library used to compile the application.
For example, when you compile an ODBC application with msodbcsql11.lib
and msodbcsql.h
, use «DRIVER={ODBC Driver 11 for SQL Server}» in the connection string.
Components of the Microsoft ODBC Driver for [!INCLUDEssNoVersion] on Windows
The ODBC driver on Windows contains the following components:
Component | Description |
---|---|
msodbcsql18.dll or msodbcsql17.dll or msodbcsql13.dll or msodbcsql11.dll |
The dynamic-link library (DLL) file that contains all of the driver’s functionality. This file is installed in %SYSTEMROOT%System32. |
msodbcdiag18.dll or msodbcdiag17.dll or msodbcdiag13.dll or msodbcdiag11.dll |
The dynamic-link library (DLL) file that contains the driver’s diagnostics (tracing) interface. This file is installed in %SYSTEMROOT%System32. |
msodbcsqlr18.rll or msodbcsqlr17.rll or msodbcsqlr13.rll or msodbcsqlr11.rll |
The accompanying resource file for the driver library. This file is installed in %SYSTEMROOT%System321033. |
s13ch_msodbcsql.chm or s11ch_msodbcsql.chm |
The Data Source Wizard help file that documents how to create a data source for the driver. This file is installed in %SYSTEMROOT%System321033
NOTE: There is no chm file for ODBC Driver 17 and above. |
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 for ODBC Driver 18 is installed in %PROGRAMFILES%Microsoft SQL ServerClient SDKODBC180SDK. |
msodbcsql18.lib or msodbcsql17.lib or msodbcsql13.lib or msodbcsql11.lib |
The library file needed to call the bcp utility functions that are part of the driver.
Note: If you do reference this library file in your program, make sure that it is in your system path and in the system path of those that use the application. msodbcsql18.lib is installed in %PROGRAMFILES%Microsoft SQL ServerClient SDKODBC180SDK. |
See also
Microsoft ODBC Driver for SQL Server on Windows
After 12 years on SqlServerBuilds.blogspot.com, it has been moved here to www.SqlServerVersions.com. The old address will be redirected automatically.
After SQL Server 2012, the primary ODBC driver for SQL Server has been developed and released as the Microsoft ODBC Driver for SQL Server. The Microsoft ODBC Driver for SQL Server is the driver that is updated with the most recent server features going forward.
How do I know what version/build I have? Look in the C:WindowsSystem32
or C:WindowsSysWOW64
folder for the file:
msodbcsql18.dll, or
msodbcsql17.dll, or
msodbcsql13.dll, or
msodbcsql11.dll
In the file properties, the Details
tab and the Product version
field.
Microsoft ODBC Driver for SQL Server build numbers:
Build | File version | Description | Release date |
---|---|---|---|
18.1.2.1 | 2018.181.2.1 | Microsoft ODBC Driver 18.1.2 for SQL Server Windows Latest Download x64 Installer
Download x86 Installer |
2022-11-03 *new |
18.1.1.1 | 2018.181.1.1 | Microsoft ODBC Driver 18.1.1 for SQL Server Windows Download x64 Installer
Download x86 Installer |
2022-08-08 |
18.0.1.1 | 2018.180.1.1 | Microsoft ODBC Driver 18.0.1 for SQL Server Windows Download x64 Installer
Download x86 Installer |
2022-02-15 |
17.10.3.1 | 2017.1710.3.1 | Microsoft ODBC Driver 17.10.3 for SQL Server Windows Download x64 Installer
Download x86 Installer |
2023-01-26 *new |
17.10.2.1 | 2017.1710.2.1 | Microsoft ODBC Driver 17.10.2 for SQL Server Windows Download x64 Installer
Download x86 Installer |
2022-11-28 *new |
17.10.1.1 | 2017.1710.1.1 | Microsoft ODBC Driver 17.10.1 for SQL Server Windows Download x64 Installer
Download x86 Installer |
2022-06-30 |
17.9.1.1 | 2017.179.1.1 | Microsoft ODBC Driver 17.9.1 for SQL Server Windows Download x64 Installer
Download x86 Installer |
2022-02-17 |
17.8.1.1 | 2017.178.1.1 | Microsoft ODBC Driver 17.8.1 for SQL Server Windows Download x64 Installer
Download x86 Installer |
2021-07-30 |
17.7.2.1 | 2017.177.2.1 | Microsoft ODBC Driver 17.7.2 for SQL Server Windows Download x64 Installer
Download x86 Installer |
2021-03-10 |
17.7.1.1 | 2017.177.1.1 | Microsoft ODBC Driver 17.7.1 for SQL Server Windows Download x64 Installer
Download x86 Installer |
2021-01-29 |
17.6.1.1 | 2017.176.1.1 | Microsoft ODBC Driver 17.6.1 for SQL Server Windows Download x64 Installer
Download x86 Installer |
2020-07-31 |
17.5.2.1 | 2017.175.2.1 | Microsoft ODBC Driver 17.5.2 for SQL Server Windows Download x64 Installer
Download x86 Installer |
2020-03-06 |
17.5.1.1 | 2017.175.1.1 | Microsoft ODBC Driver 17.5.1 for SQL Server Windows Download x64 Installer
Download x86 Installer |
2020-01-31 |
17.4.2.1 | 2017.174.2.1 | Microsoft ODBC Driver 17.4.2 for SQL Server Windows Download x64 Installer
Download x86 Installer |
2019-10-04 |
17.4.1.1 | 2017.174.1.1 | Microsoft ODBC Driver 17.4.1 for SQL Server Windows Download x64 Installer
Download x86 Installer |
2019-07-24 |
17.3.1.1 | 2017.173.1.1 | Microsoft ODBC Driver 17.3.1 for SQL Server Windows Download x64 Installer
Download x86 Installer |
2019-02-14 |
17.3.0.1 | 2017.173.0.1 | Microsoft ODBC Driver 17.3.0 for SQL Server (Preview) Windows Preview Download x64 Installer
Download x86 Installer |
2018-09-21 |
17.2.0.1 | 2017.172.0.1 | Microsoft ODBC Driver 17.2.0 for SQL Server Windows Download x64 Installer
Download x86 Installer |
2018-06-23 |
17.1.0.1 | 2017.171.0.1 | Microsoft ODBC Driver 17.1.0 for SQL Server Windows Download x64 Installer
Download x86 Installer |
2018-03-27 |
17.0.1.1 | 2017.170.1.1 | Microsoft ODBC Driver 17.0.1 for SQL Server Windows Download x64 Installer
Download x86 Installer |
2018-01-19 |
13.0.4414.46 | 2015.131.4414.46 | Microsoft ODBC Driver 13.1 for SQL Server Windows Download x64 Installer
Download x86 Installer |
2018-03-13 |
13.0.811.168 | 2015.130.811.168 | Microsoft ODBC Driver 13 for SQL Server Windows Download x64 Installer
Download x86 Installer |
2016-07-20 |
12.0.5543.11 | 2014.120.5543.11 | Microsoft ODBC Driver 11 for SQL Server Windows Download x64 Installer
Download x86 Installer |
2017-03-02 |
You can comment here. If you know of a Microsoft ODBC Driver for SQL Server version that we don’t have listed here, please use the comments.
I work on this site continuously and keep the information up to date. If it helps you, you can support me:
Buy me a coffee
Support me in another way
© 2007–2023 SqlServerVersions.com · Contact · Disclaimer · Privacy policy
Для корректного подключения к базам данных Microsoft SQL Server установите
драйверы ODBC. В данной статье приведены инструкции по настройке данных
драйверов.
Предварительно установите программы gcc и make:
-
на Debian-подобных дистрибутивах:
sudo
apt-get install tar gcc make g++
-
на RedHat-подобных дистрибутивах:
sudo
yum install tar gcc make
Установка Microsoft ODBC Driver 17 for SQL Server
Для установки Microsoft ODBC Driver 17 for SQL Server обратитесь к документации
Microsoft. После установки драйвера создайте символьную
ссылку для платформы с помощью команд:
cd /opt/Foresight/fp9.x-biserver/bin
sudo ln -s
/opt/microsoft/msodbcsql/lib64/libmsodbcsql-17.0.so.2270.0 libmsodbcsql-17.0.so
Установка Microsoft ODBC Driver 11 for SQL Server
Если ранее был установлен драйвер Microsoft SQL Server ODBC Driver 1.0
for Linux, то удалите его и установите Microsoft ODBC Driver 11 for SQL
Server (драйвер доступен по адресу https://www.microsoft.com/en-us/download/details.aspx?id=36437).
Для данной версии драйвера рекомендуется использование unixODBC версии
не старше 2.3.0.
Процесс установки диспетчера драйверов описан в статье «Установка диспетчера драйверов».
Для подготовки и установки ODBC драйвера:
-
Убедитесь, что архив с ODBC драйвером распакован.
-
Измените файлы:
-
build_dm.sh:
-
замените строку (только для Astra Linux):
req_proc=»x86_64″;
на:
req_proc=»unknown»;
-
замените «-xvzf» на «-xvf».
-
install.sh:
-
замените строку (только для Astra Linux):
req_proc=»x86_64″;
на:
req_proc=»unknown»;
-
замените строку (только для Debian-подобных дистрибутивов):
req_libs=( glibc e2fsprogs
krb5-libs openssl )
на:
req_libs=(
libc6 e2fsprogs libkrb5-3 openssl )
-
измените содержимое функции check_required_libs. Данная
функция должна выглядеть следующим образом:
function check_required_libs
{
log
«Checking that required libraries are installed»
for
lib in ${req_libs[@]}
do
local
present=$(dpkg-query -l «$lib» | grep «$lib» 2>/dev/null)
echo
«$present» >> «$log_file»
if
[ «$present» == «» ]; then
echo
«The $lib library was not found installed in the dpkg database.»
echo
«See README for which libraries are required for the $driver_name.»
return
1;
fi
done
return
0;
}
-
Скачайте установочный файл ODBC unixODBC-2.3.0.tar.gz
и выполните команду:
bash
build_dm.sh —download-url=file://unixODBC-2.3.0.tar.gz
После чего будет выдано сообщение:
>>Run
the command ‘cd /tmp/unixODBC<временная
метка>/unixODBC-2.3.0; make install’ to install the driver manager.
-
Установите пакет unixODBC с помощью команд:
cd /tmp/unixODBC<временная метка>/unixODBC-2.3.0
sudo
make install
cd —
Если команды выполняются под именем пользователя
sudo, то для перехода в директорию смените пользователя на root с помощью
команды:
sudo
-i
Далее перейдите в папку и выполните команду:
cd /tmp/unixODBC<временная метка>/unixODBC-2.3.0
make
install
После этого произведите выход из-под пользователя
root сочетанием клавиш CTRL+D.
-
Проверьте возможность установки ODBC драйвера в системе с помощью
команды:
bash
install.sh verify
После чего будет выдано сообщение о результатах
проверки. При условии отсутствия проблем для установки сообщение будет
получено в следующем виде:
Starting install for
Microsoft ODBC Driver 11 for SQL Server
Checking for 64 bit Linux
compatible OS ………………………………. OK
Checking required libs
are installed …………………………………. OK
unixODBC utilities (odbc_config
and odbcinst) installed ………………… OK
unixODBC Driver Manager
version 2.3.0 installed ……………………….. OK
unixODBC Driver Manager
configuration correct ………………………… OK*
Microsoft
ODBC Driver 11 for SQL Server already installed ………… NOT FOUND
Если при проверке возникли ошибки, то сообщение
о них будет записано в лог-файл, например:
See /tmp/msodbcsql.30762.3652.5941/install.log
for more information about installation failures.
Для дальнейшей установки устраните все ошибки.
После их устранения выполните команду для установки драйвера:
bash
install.sh install —accept-license
-
Создайте символьную ссылку для платформы с помощью команд:
cd /opt/Foresight/fp9.x-biserver/bin
sudo ln -s
/opt/microsoft/msodbcsql/lib64/libmsodbcsql-11.0.so.2270.0 libmsodbcsql-11.0.so
-
Убедитесь, что отсутствуют проблемы с разделяемыми библиотеками,
с помощью команды:
ldd
/opt/microsoft/msodbcsql/lib64/libmsodbcsql-11.0.so.2270.0 | grep not
В случае присутствия всех необходимых библиотек
переходите к регистрации драйвера.
Если в результате выполнения команды получился
список, например:
libcrypto.so.10 =>
not found
libssl.so.10
=> not found
То выполните следующие действия:
cd /usr/lib/x86_64-linux-gnu
sudo apt-get install
libssl-dev
sudo ln -s libcrypto.so.1.0.0
libcrypto.so.10
sudo
ln -s libssl.so.1.0.0 libssl.so.10
Для Ubuntu символьные ссылки будут другие:
cd
/usr/lib/x86_64-linux-gnu
sudo apt-get install libssl-dev
sudo ln -s /lib/x86_64-linux-gnu/libcrypto.so.1.0.0 libcrypto.so.10
sudo ln -s /lib/x86_64-linux-gnu/libssl.so.1.0.0 libssl.so.10
После выполнения действий повторно проверьте
все зависимости драйвера и в случае отсутствия проблем переходите к регистрации.
Запись о драйвере будет добавлена в файл odbcinst.ini.
-
Зарегистрируйте драйвер вручную с помощью команды:
odbcinst
-i -d -f mssql.driver.template
Где файл mssql.driver.template содержит необходимые
для работы драйвера параметры. Например:
[ODBC Driver 11 for SQL
Server]
Description = Microsoft
ODBC Driver 11 for SQL Server
Driver =
/opt/microsoft/msodbcsql/lib64/libmsodbcsql-11.0.so.2270.0
Threading = 1
IconvEncoding = UTF16LE
DSN
= MSSQL_DSN
-
Проверьте правильность установки драйвера
с помощью команды:
odbcinst
-q -d -n «ODBC Driver 11 for SQL Server»
Результатом правильной установки будет служить
вывод всех параметров драйвера с их значениями.
-
Проверьте подключение к серверу. Для этого используйте подключение
с применением telnet:
telnet
192.168.1.1 1433
В случае ошибки подключения будет получено
сообщение:
telnet:
Unable to connect to remote host: Connection refused
Для устранения ошибок на данном этапе обратитесь
к системному администратору.
При успешном подключении будет получено сообщение
следующего вида:
Connected
to 192.168.1.1.
-
Проверьте подключение к серверу с
использованием параметров из источника данных. Для это выполните команду:
isql
-v <DATA_SOURCE_NAME> <USER>@<HOST> <PASSWORD>
В случае успешного подключения к серверу
будет получено сообщение:
+—————————————+
| Connected! |
| |
| sql-statement |
| help [tablename] |
| quit |
| |
+—————————————+
При этом будет возможность выполнить запросы
к базе данных.
В случае проблем будет выдано сообщение:
[ISQL]ERROR:
Could not SQLConnect
Для устранения ошибок на данном этапе обратитесь
к администратору СУБД.
После выполнения действий будет подготовлен и установлен драйвер Microsoft
ODBC Driver 11 for SQL Server.
См. также:
Дополнительные
настройки
SQL Server 2014
Standard security
Driver={ODBC Driver 11 for SQL Server};Server=myServerAddress;Database=myDataBase;UID=myUsername;PWD=myPassword;
Trusted Connection
Driver={ODBC Driver 11 for SQL Server};Server=myServerAddress;Database=myDataBase;Trusted_Connection=yes;
Connecting to an SQL Server instance
The syntax of specifying the server instance in the value of the server key is the same for all connection strings for SQL Server.
Driver={ODBC Driver 11 for SQL Server};Server=serverNameinstanceName;Database=myDataBase;Trusted_Connection=yes;
Using a non-standard port
If your SQL Server listens on a non-default port you can specify that using the servername,xxxx syntax (note the comma, it’s not a colon).
Driver={ODBC Driver 11 for SQL Server};Server=myServerName,myPortNumber;Database=myDataBase;UID=myUsername;PWD=myPassword;
Enable MARS
Driver={ODBC Driver 11 for SQL Server};Server=serverAddress;Database=databaseName;Trusted_Connection=yes;MARS_Connection=yes;
Encrypt data sent over network
Driver={ODBC Driver 11 for SQL Server};Server=serverAddress;Database=databaseName;Trusted_Connection=yes;Encrypt=yes;
Attach a database file on connect to a local SQL Server Express instance
Driver={ODBC Driver 11 for SQL Server};Server=.SQLExpress;AttachDBFileName=c:dir\mydb.mdf;Database=dbName;Trusted_Connection=yes;
Database mirroring
If you connect to a database that is being mirrored, your application can take advantage of the drivers ability to automatically redirect connections when a database mirroring failover occurs. You must specify the initial principal server and database in the connection string and the failover partner server.
Driver={ODBC Driver 11 for SQL Server};Server=myServerAddress;Failover_Partner=myMirrorServerAddress;Database=myDataBase;Trusted_Connection=yes;
SQL Server 2012
Standard security
Driver={ODBC Driver 11 for SQL Server};Server=myServerAddress;Database=myDataBase;UID=myUsername;PWD=myPassword;
Trusted Connection
Driver={ODBC Driver 11 for SQL Server};Server=myServerAddress;Database=myDataBase;Trusted_Connection=yes;
Connecting to an SQL Server instance
The syntax of specifying the server instance in the value of the server key is the same for all connection strings for SQL Server.
Driver={ODBC Driver 11 for SQL Server};Server=serverNameinstanceName;Database=myDataBase;Trusted_Connection=yes;
Using a non-standard port
If your SQL Server listens on a non-default port you can specify that using the servername,xxxx syntax (note the comma, it’s not a colon).
Driver={ODBC Driver 11 for SQL Server};Server=myServerName,myPortNumber;Database=myDataBase;UID=myUsername;PWD=myPassword;
Enable MARS
Driver={ODBC Driver 11 for SQL Server};Server=serverAddress;Database=databaseName;Trusted_Connection=yes;MARS_Connection=yes;
Encrypt data sent over network
Driver={ODBC Driver 11 for SQL Server};Server=serverAddress;Database=databaseName;Trusted_Connection=yes;Encrypt=yes;
Attach a database file on connect to a local SQL Server Express instance
Driver={ODBC Driver 11 for SQL Server};Server=.SQLExpress;AttachDBFileName=c:dir\mydb.mdf;Database=dbName;Trusted_Connection=yes;
Database mirroring
If you connect to a database that is being mirrored, your application can take advantage of the drivers ability to automatically redirect connections when a database mirroring failover occurs. You must specify the initial principal server and database in the connection string and the failover partner server.
Driver={ODBC Driver 11 for SQL Server};Server=myServerAddress;Failover_Partner=myMirrorServerAddress;Database=myDataBase;Trusted_Connection=yes;
SQL Server 2008
Standard security
Driver={ODBC Driver 11 for SQL Server};Server=myServerAddress;Database=myDataBase;UID=myUsername;PWD=myPassword;
Trusted Connection
Driver={ODBC Driver 11 for SQL Server};Server=myServerAddress;Database=myDataBase;Trusted_Connection=yes;
Connecting to an SQL Server instance
The syntax of specifying the server instance in the value of the server key is the same for all connection strings for SQL Server.
Driver={ODBC Driver 11 for SQL Server};Server=serverNameinstanceName;Database=myDataBase;Trusted_Connection=yes;
Using a non-standard port
If your SQL Server listens on a non-default port you can specify that using the servername,xxxx syntax (note the comma, it’s not a colon).
Driver={ODBC Driver 11 for SQL Server};Server=myServerName,myPortNumber;Database=myDataBase;UID=myUsername;PWD=myPassword;
Enable MARS
Driver={ODBC Driver 11 for SQL Server};Server=serverAddress;Database=databaseName;Trusted_Connection=yes;MARS_Connection=yes;
Encrypt data sent over network
Driver={ODBC Driver 11 for SQL Server};Server=serverAddress;Database=databaseName;Trusted_Connection=yes;Encrypt=yes;
Attach a database file on connect to a local SQL Server Express instance
Driver={ODBC Driver 11 for SQL Server};Server=.SQLExpress;AttachDBFileName=c:dir\mydb.mdf;Database=dbName;Trusted_Connection=yes;
Database mirroring
If you connect to a database that is being mirrored, your application can take advantage of the drivers ability to automatically redirect connections when a database mirroring failover occurs. You must specify the initial principal server and database in the connection string and the failover partner server.
Driver={ODBC Driver 11 for SQL Server};Server=myServerAddress;Failover_Partner=myMirrorServerAddress;Database=myDataBase;Trusted_Connection=yes;
SQL Server 2005
Standard security
Driver={ODBC Driver 11 for SQL Server};Server=myServerAddress;Database=myDataBase;UID=myUsername;PWD=myPassword;
Trusted Connection
Driver={ODBC Driver 11 for SQL Server};Server=myServerAddress;Database=myDataBase;Trusted_Connection=yes;
Connecting to an SQL Server instance
The syntax of specifying the server instance in the value of the server key is the same for all connection strings for SQL Server.
Driver={ODBC Driver 11 for SQL Server};Server=serverNameinstanceName;Database=myDataBase;Trusted_Connection=yes;
Using a non-standard port
If your SQL Server listens on a non-default port you can specify that using the servername,xxxx syntax (note the comma, it’s not a colon).
Driver={ODBC Driver 11 for SQL Server};Server=myServerName,myPortNumber;Database=myDataBase;UID=myUsername;PWD=myPassword;
Enable MARS
Driver={ODBC Driver 11 for SQL Server};Server=serverAddress;Database=databaseName;Trusted_Connection=yes;MARS_Connection=yes;
Encrypt data sent over network
Driver={ODBC Driver 11 for SQL Server};Server=serverAddress;Database=databaseName;Trusted_Connection=yes;Encrypt=yes;
Attach a database file on connect to a local SQL Server Express instance
Driver={ODBC Driver 11 for SQL Server};Server=.SQLExpress;AttachDBFileName=c:dir\mydb.mdf;Database=dbName;Trusted_Connection=yes;
Database mirroring
If you connect to a database that is being mirrored, your application can take advantage of the drivers ability to automatically redirect connections when a database mirroring failover occurs. You must specify the initial principal server and database in the connection string and the failover partner server.
Driver={ODBC Driver 11 for SQL Server};Server=myServerAddress;Failover_Partner=myMirrorServerAddress;Database=myDataBase;Trusted_Connection=yes;
- Windows
- Разработчикам
- Базы данных
- Microsoft ODBC Driver for SQL Server
Количество загрузок:1,316
Операционная система:Windows 7
Последняя версия:11.0.2270.0
Сообщить о неточности
Описание
Скачать Microsoft ODBC Driver for SQL Server 11.0.2270.0 бесплатно с сайта. Microsoft ODBC Driver for SQL Server принадлежит к категории Разработчикам, а точнее к подкатегории Базы данных.
Microsoft ODBC Driver for SQL Server совместима с версиями 32-бит Windows 7. Установочные файлы программы следующие: cliconfg.exe, sqlmangr.exe, scm.exe, profiler.exe или ODBCADM.EXE и т.д. Эта бесплатная программа была создана Microsoft. Самая популярная версия среди пользователей Microsoft ODBC Driver for SQL Server 11.0.
От разработчика:
The Microsoft ODBC Driver For SQL Server provides native connectivity from Windows to Microsoft SQL Server and Windows Azure SQL Database. Microsoft ODBC Driver 11 for SQL Server is a single dynamic-link library (DLL) containing run-time support for applications using native-code APIs to connect to Microsoft SQL Server 2005, 2008, 2008 R2, SQL Server 2012 and Windows Azure SQL Database.
Мы предлагаем оценить другие программы, такие как MaxDB, DTM ODBC Manager или FileAmigo, которые часто используются вместе с Microsoft ODBC Driver for SQL Server.
Обновлено:
15 мая, 2022
Последние обновления