Microsoft Sql Server 2005 Odbc Drivers For Mac

Posted on by



Go Up to Database Connectivity (FireDAC)

Microsoft SQL Server version 20.00: For Microsoft SQL Server 2005 SP3 (9.0.4035) on Windows use: Microsoft SQL Native Client 20.00: For Microsoft SQL Server 2008 SP1 (.22) on Windows use: Microsoft SQL Native Client 2007.100.2531.00: For all versions of Microsoft SQL Server supported above on Mac OS X use. ODBC drivers for SQLServer 2005 There is a fileDSN set up to connect to SqlServer 2005 with the driver-6.01.7600.16385. We have a few machines which have the sqlserver driver. The driver includes an installer, connection setup assistant, on-line help, and connection diagnostic tools. With this Mac ODBC solution, you'll be importing data from your SQL Server in no time. Download ODBC Driver. The ODBC drivers for Linux and macOS support AlwaysOn Availability Groups. For more information about AlwaysOn Availability Groups, see: Availability Group Listeners, Client Connectivity, and Application Failover (SQL Server) Creation and Configuration of Availability Groups (SQL Server). This video tutorial covers how to configure ODBC to access a Microsoft SQL Server database. More guides and tutorials: http://www.itgeared.com/.

This topic describes how to connect to Microsoft SQL Server.

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.

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.

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:

Mac OS X Client Software

FireDAC requires:

  • the UnixODBC (libodbc.dylib) x86 ODBC driver manager library.
  • the FreeTDS (libtdsodbc.so) x86 ODBC driver.

FreeTDS can be transferred from CVS into a folder in your home directory (more 1) (more 2). To install FreeTDS on Mac OS X, 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.

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 you to specify DriverID, Server, Database, OSAuthent, User_Name, and Password.

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.

  • 127.0.0.1SQLEXPRESS
  • SrvHost, 4000
  • tcp:nasdfert6.database.windows.net
Port Only for Mac OS X. 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 set 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. It is not supported by SQL Azure. The enabled MARS may lead to fetch performance degradation. For more details, read the following:

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 -- case-insensitive metadata search is used.
  • False -- depends on the database collation. This is the default value.
True

Usage 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

Retrieved from 'http://docwiki.appmethod.com/appmethod/1.13/topics/e/index.php?title=Connect_to_Microsoft_SQL_Server_(FireDAC)&oldid=6480'

Where to download the ODBC Drivers and OLEDB Providers for the different versions of SQL Server Native Client?

There are different versions of the Native Client components for each SQL Server.

  • SQL Server 2005 - Native Client 9.0
  • SQL Server 2008 - Native Client 10.0
  • SQL Server 2012 - Native Client 11.0

The components have been distributed through SQL Server 'Feature Packs' and there are new versions of those 'Feature Packs' for each Service Pack release of SQL Server.

This page lists instructions and download links for each version of the Native Client OLE DB providers and ODBC drivers and for each Feature Pack distribution package. If you find something is missing, let us know here!

Download SQL Server 2005 Native Client ODBC & OLEDB

Microsoft Sql Server 2005 Odbc Drivers For Mac

Microsoft Sql Server Odbc Driver

Booth the ODBC driver and the OLEDB provider have been released within the 'Feature Pack for Microsoft SQL Server 2005'.
There are four versions of this Feature Pack. The latest is the 'December 2008' package.

The package contains:

  • SQL Native Client 9.0 OLE DB Provider - 'SQLNCLI'
  • SQL Native Client 9.0 ODBC Driver - '{SQL Native Client}'

Download Instructions

First navigate to one of the download links below, then:

  • Hit Download button.
  • Checkbox one of the installation packages (msi). Make sure you choose the right version:
    • sqlncli.msi for 32-bit
    • sqlncli_x64.msi for 64-bit
    • sqlncli_ia64.msi for Itanium
  • Click Next.
  • Download starts.

Feature Pack for SQL Server 2005 - download links

Download SQL Server 2008 Native Client ODBC & OLEDB

Booth the ODBC driver and the OLEDB provider have been released within Microsoft SQL Server 2008 'Feature Packs'.
There are different 'Feature Packs' for each SQL Server 2008 service pack version.

Microsoft Odbc Driver 17 For Sql Server

The package contains:

  • SQL Server Native Client 10.0 OLE DB Provider - 'SQLNCLI10'
  • SQL Server Native Client 10.0 ODBC Driver - '{SQL Server Native Client 10.0}'

Download Instructions

First navigate to one of the download links below, then:

  • Hit Download button.
  • Checkbox one of the 'sqlncli.msi' installation packages. Make sure you choose the right version:
    • x86 for 32-bit
    • x64 for 64-bit
    • IA64 for Itanium
  • Click Next.
  • Download starts.

Feature Pack for SQL Server 2008 - download links

  • SQL Server 2008 SP1 Feature Pack - NO LONGER AVAILABLE
  • SQL Server 2008 Feature Pack - NO LONGER AVAILABLE

Download SQL Server 2008 R2 Native Client ODBC & OLEDB

Booth the ODBC driver and the OLEDB provider have been released within Microsoft SQL Server 2008 R2 'Feature Packs'.
There are different 'Feature Packs' for each SQL Server 2008 R2 service pack version.

The package contains:

  • SQL Server Native Client 10.0 OLE DB Provider - 'SQLNCLI10'
  • SQL Server Native Client 10.0 ODBC Driver - '{SQL Server Native Client 10.0}'

Download Instructions

First navigate to one of the download links below, then:

  • Hit Download button.
  • Checkbox one of the 'sqlncli.msi' installation packages. Make sure you choose the right version:
    • sqlncli_x86.msi for 32-bit
    • sqlncli_amd64.msi for 64-bit
    • sqlncli_ia64.msi for Itanium
  • Click Next.
  • Download starts.

Feature Pack for SQL Server 2008 R2 - download links

Download SQL Server 2012 Native Client ODBC & OLEDB

Booth the ODBC driver and the OLEDB provider have been released within the 'Microsoft SQL Server 2012 Feature Pack'.
There are currently only one 'Feature Pack' for SQL Server 2012.

The package contains:

  • SQL Server Native Client 11.0 OLE DB Provider - 'SQLNCLI11'
  • SQL Server Native Client 11.0 ODBC Driver - '{SQL Server Native Client 11.0}'

Download Instructions

First navigate to one of the download links below, then:

  • Do NOT hit the Download button
  • Expand the 'Install Instructions' section
  • Scroll down to the 'MICROSOFT SQL SERVER CONNECTIVITY FEATURE PACK COMPONENTS' section (it's far down)
  • Under the 'Microsoft SQL Server 2012 Native Client' heading, click one of the 'sqlncli.msi' installation package links. Make sure you choose the right version:
    • X86 Package for 32-bit
    • X64 Package for 64-bit
    • seems there are no link for the Itanium CPU architecture
  • Download starts.

Feature Pack for SQL Server 2012 - download links

Summary

This page aims to provide all information needed to obtain the correct Native Client ODBC Driver or Native Client OLEDB Provider for connections to SQL Server. If any info on this page is not up to date, not correct, unclear or could be more precise, let us know buy sending us info through this form. Thanks!