Microsoft Sql Server 2005 Odbc Drivers For Mac

  

  1. The ODBC Driver for SQL Server uses the ODBC interface to access data in database management systems. It allows an ODBC-compliant application to gain access to one or more data sources. ODBC drivers work under the control of an ODBC driver manager, which is a library that manages communication between the ODBC-aware application and ODBC drivers.
  2. Devart ODBC Driver for SQL Server provides high-performance and feature-rich connectivity solution for ODBC-based applications to access SQL Server databases from Windows, Linux and Mac OS X, both.
  3. Mar 06, 2020 Download Microsoft® ODBC Driver 17 for SQL Server® - Windows, Linux, & macOS from Official Microsoft Download Center.
  4. Mar 26, 2018 The Microsoft ODBC Driver for SQL Server provides native connectivity from Windows, Linux, & macOS to Microsoft SQL Server and Microsoft Azure SQL Database. Details Note: There are multiple files available for this download.

Our software uses the highest driver installed, For example, If both SQL server 2005 and 2008 are installed it will use SQL Server 2008 Driver. To Check Version of SQL Server ODBC Driver do the following.

Go Up to Database Connectivity (FireDAC)

This topic describes how to connect to Microsoft SQL Server.

  • 2Client Software
  • 5Use Cases
  • 6See Also

Microsoft Sql Server 2005 Odbc Drivers For Mac Free

Supported Versions

The FireDAC native driver supports Microsoft SQL Server Standard and Express editions version 2000 and later, and Microsoft SQL Azure. For a description of how to connect to Microsoft SQL Server Compact Edition, see Connect to Microsoft SQL Server Compact Edition.

Client Software

Windows Client Software

FireDAC requires one of the Microsoft SQL Server x86 or x64 ODBC drivers to be installed on the workstation:

  • SQL Server ODBC driver as the connectivity for SQL Server 2000. Most likely, the ODBC driver is already installed on your workstation. If not, see details.
  • SQL Native Client as the connectivity for SQL Server 2000 and 2005. We strongly recommend that you have SQL Native Client installed, if your application has to work with SQL Server 2005. See Microsoft SQL Server Native Client.
  • SQL Server Native Client NN.N as the connectivity for SQL Server 2000, 2005, 2008, 2012, and SQL Azure. We strongly recommend that you have SQL Server Native Client NN.N installed, if your application has to work with SQL Server 2008, 2012, or SQL Azure. See Microsoft SQL Server 2008 Native Client.
  • SQL Server Native Client 11.0 as the connectivity for LocalDB.
  • ODBC Driver 13 as the connectivity for SQL Server 2008, 2008 R2, 2012, 2014, and 2016, and SQL Azure.

Note: SQL Server Native Client 10.0 (SQL Server 2008) may fail to call a stored procedure, when it is connected to SQL Server 2000. The symptom of this issue is the error message 'Incorrect Syntax near to {'. In this case, use the ODBC driver from the SQL Server 2000 or 2005 distribution.

If the SQL Server ODBC driver has not been installed properly, an exception is raised when you try to connect:

macOS Client Software

FireDAC requires:

  • The UnixODBC (libodbc.dylib) x86 ODBC driver manager library.
  • The FreeTDS (libtdsodbc.dylib) x86 ODBC driver.
Microsoft Sql Server 2005 Odbc Drivers For Mac

FreeTDS can be transferred from CVS into a folder in your home directory (more 1) (more 2). To install FreeTDS on macOS, use the commands:

Note that you may also need to install the gawk utility. At this point, you can configure a ODBC DSN or test the FireDAC connection.

Note that the FreeTDS ODBC driver is not that efficient and stable as the original Microsoft ODBC driver.

Linux Client Software

FireDAC requires the unixODBC 64-bit ODBC driver manager library and the Microsoft ODBC Driver 11 for SQL Server on Linux.

To install the Microsoft ODBC Driver 11 for SQL Server on Linux:

  1. On Ubuntu Server 16.04 LTS, run the following commands:
  2. On Red Hat Enterprise Linux 7, download the corresponding installer and follow the official installation instructions.

Driver Linkage

To link the driver:

  • drop a TFDPhysMSSQLDriverLink component from the 'FireDAC Links' palette page.
  • or include the FireDAC.Phys.MSSQL unit in the uses clause.

Connection Definition Parameters

To connect to the Microsoft SQL Server DBMS, most applications require that you specify the DriverID, Server, Database, OSAuthent, User_Name, and Password parameters (see Defining Connection (FireDAC) for details).

DriverID=MSSQL

ParameterDescriptionExample value
Server Name of a server running SQL Server on the network. The value must be either the name of a server on the network or the name of a SQL Server Client Network Utility advanced server entry.

When you connect to the SQL Azure, you have to prepend the server name with the 'tcp:' prefix.

Note: The alternative TPC/IP port may be specified after a server name, separated by the comma.

Note: To connect to a named instance on Linux, the TPC/IP port must be specified after a server name, separated by the comma. Do not specify the instance name.

  • 127.0.0.1SQLEXPRESS
  • SrvHost, 4000
  • tcp:nasdfert6.database.windows.net
Port Only for macOS. Specifies the port where the SQL Server is listening.

For the Windows platform the port may be specified after a comma in the Server parameter value. For example, Server=host, port. The default port is 1433.

Database Name of the default database for the connection. If the Database is not specified, the default database defined for the login is used.Northwind
OSAuthent

Controls the authentication mode:

  • Yes -- use Windows authentication.
  • No -- use DBMS authentication. This is the default value.
No
User_Name The SQL Server login name, if OSAuthent=No.

When you connect to the SQL Azure, you have to append the '@<server>' suffix to your user name.

  • sa
  • addemo@nasdfert6
Password The SQL Server login password, if OSAuthent=No.

Note that the passwords with both '{' and '}' are not supported.

Network Name of a network library dynamic-link library. The name does not need to include the path and must not include the .dll file name extension.dbnmpntw
Address Network address of the server running an instance of SQL Server. Address is usually the network name of the server, but can be other names, such as a pipe, or a TCP/IP port and socket address.
MARS

Controls the MARS (multiple active result sets) support in a connection:

  • Yes -- MARS is enabled for a connection. This is the default value.
  • No -- MARS is disabled.

MARS is a feature supported by SQL 2005 and later, or by SQL Azure. Note that enabling the MARS feature might result in performance degradation.

For information about MARS, see: Using Multiple Active Result Sets (MARS)

No
Workstation Workstation ID. Typically, this is the network name of the computer on which the application resides (optional). If specified, this value is stored in the master.dbo.sysprocesses column hostname and is returned by sp_who and the Transact-SQL HOST_NAME function.Bookkeeper1
Language SQL Server language name (optional). When connecting to a SQL Server with multiple languages, Language specifies which set of messages are used for the connection.
Encrypt

Controls the network traffic encryption:

  • Yes -- network traffic is encrypted.
  • No -- no encryption is used. This is the default value.
Yes
LoginTimeout Controls the amount of time, in seconds, before an application times out while attempting to establish a connection. 0 specifies an infinite wait (default value).30
VariantFormat

Controls the SQL_VARIANT data type representation:

  • String -- values are represented as dtWideString. A string value is returned as a hex string, numbers as strings, and so on. This is the default value.
  • Binary -- values are represented as dtByteString with raw data presentation. A string value is returned as a string with original encoding, numbers in binary format, and so on.
Binary
ExtendedMetadata

Controls the extended description of the query result sets:

  • True -- FireDAC is getting a field origin table and column additional to the other column attributes. Setting this option to True may slow down a dataset opening.
  • False -- FireDAC uses the restricted information about the query columns. This is the default value.
True
ApplicationName Name of the application. If specified, this value is stored in the master.dbo.sysprocesses column program_name and is returned by sp_who and the Transact-SQL APP_NAME function.AllBooks
ODBCAdvanced Allows you to specify any other additional ODBC connection parameter value.MARS_Connection=no;Regional=yes
MetaDefCatalog Default database name. The Design time code excludes the catalog name from the object name if it is equal to MetaDefCatalog.Northwind
MetaDefSchema Default schema name. The Design time code excludes the schema name from the object name if it is equal to MetaDefSchema.dbo
MetaCaseIns

Controls the metadata case sensitivity:

  • True -- a case-insensitive metadata search is used.
  • False -- depends on the database collation. This is the default value.
True
MetaCaseInsCat

Controls the SQL Server catalog names case sensitivity. This parameter can take one of the following values:

  • Choose -- lets FireDAC automatically detect the catalog names case sensitivity. This is the default value.
  • False -- the catalog names are case-sensitive.
  • True -- the catalog names are case-insensitive.
True

Use Cases

Using a Secure Connection

To use TLS/SSL encryption, pass the key-value pair TrustServerCertificate=yes on the value of the ODBCAdvanced parameter:

Other Use Cases

  • Connect to the local SQL Server instance using SQL Server authentication:
  • Connect to SQL Express 2005 using Windows authentication:
  • Connect to SQL Azure. Note the '@<server>' suffix in User_Name and the 'tcp:' prefix in the Server parameters:
  • Connect to LocalDB:
  • Connect to LocalDB and attach a database file:

See Also

Samples

  • FireDAC MS SQL sample
Retrieved from 'http://docwiki.embarcadero.com/RADStudio/Sydney/e/index.php?title=Connect_to_Microsoft_SQL_Server_(FireDAC)&oldid=270548'
-->

This topic lists the requirements to use the Microsoft ODBC Driver for SQL Server on Linux and macOS.

SQL version compatibility

Microsoft Sql Server Odbc 17

The Linux and macOS drivers SQL version compatibility is the same as the Windows drivers SQL version compatibility.

Operating system support

Versions 17, 13.1, and 13 of the Linux and macOS drivers are supported on the x64 architecture of the following operating systems:

Driver version →
↓ Operating System		17.617.517.417.317.217.117.013.113
Apple OS X 10.11 (El Capitan)YesYesYesYesYesYesYes
Apple macOS 10.12 (Sierra)YesYesYesYesYesYesYes
Apple macOS 10.13 (High Sierra)YesYesYesYesYesYesYesYesYes
Apple macOS 10.14 (Mojave)YesYesYesYes
Apple macOS 10.15 (Catalina)YesYes
Alpine Linux 3.11YesYes
Debian Linux 8YesYesYesYesYesYesYesYesYes
Debian Linux 9YesYesYesYesYesYesYesYesYes
Debian Linux 10YesYesYes
Oracle Linux 8YesYes
RedHat Enterprise Linux 6YesYesYesYesYesYesYesYesYes
RedHat Enterprise Linux 7YesYesYesYesYesYesYesYesYes
RedHat Enterprise Linux 8YesYesYes
SUSE Linux Enterprise Server 111YesYesYesYesYesYesYesYesYes
SUSE Linux Enterprise Server 12YesYesYesYesYesYesYesYesYes
SUSE Linux Enterprise Server 15YesYesYesYes
Ubuntu Linux 14.04YesYesYesYesYesYesYes
Ubuntu Linux 16.04YesYesYesYesYesYesYesYesYes
Ubuntu Linux 18.04YesYesYesYesYes
Ubuntu Linux 20.04Yes

1 ODBC Driver 17 supports SUSE Linux Enterprise Server 11 SP4 only

The installation packages for the Microsoft ODBC Driver 13, 13.1, and 17 for SQL Server on Linux and macOS resolve the driver's dependencies automatically when installed using the package management system of your distribution, as described in Install the ODBC Driver (Linux) and Install the ODBC Driver (macOS).

Microsoft Sql Server 2005 Odbc Drivers For Mac

Microsoft Sql Server 2005 Odbc Drivers For Mac Windows 7

Microsoft ODBC Driver 11 for SQL Server

  • 64-bit UnixODBC 2.3.0 Driver Manager, built for 64-bit SQLLEN/SQLULEN. Later versions of the 64-bit UnixODBC Driver Manager are not supported with the ODBC driver on Linux. See Installing the Driver Manager for more information.

  • ODBC driver for Red Hat Enterprise Linux 5 (64-bit) requires the following packages, and can be downloaded here: Microsoft ODBC Driver 11 for SQL Server - Red Hat Linux

    • glibc
    • libgcc
    • libstdc++
    • e2fsprogs-libs
    • krb5-libs
    • openssl

  • ODBC driver for Red Hat Enterprise Linux 6 (64-bit) requires the following packages, and can be downloaded here: Microsoft ODBC Driver 11 for SQL Server - Red Hat Linux

    • glibc
    • libgcc
    • libstdc++
    • libuuid
    • krb5-libs
    • openssl

  • ODBC driver for SUSE Linux Enterprise 11 Service Pack 2 (64-bit) requires the following packages, and can be downloaded here: Microsoft ODBC Driver 11 Preview for SQL Server - SUSE Linux

    • glibc
    • libstdc++46
    • libgcc46
    • libuuid1
    • krb5
    • libopenssl0_9_8

See Also

Installing the Driver Manager
Known Issues in this Version of the Driver
Release Notes