OpenLink's SQL Server ODBC drivers are available in a choice of three formats to suit your network infrastructure.
A single-tier driver: easy installation on Mac OS X Universal and Microsoft Windows platforms.
A single-tier driver: simple and quick to deploy; installs on the client computer only; uses a database-specific communications layer
A multi-tier driver with configurable performance, scalability and security for Enterprise users; typically components are installed on both the client and database-server hosts.
|More Information and Download||More Information and Download||More Information and Download|
|Microsoft Windows and Mac OS X Availability|
|Linux, Solaris and other Unix OS Availability|
|Single component client-only installation|
|Multiple components installed on clients and server computers|
|Requires database-specific comms layer on client|
|ODBC Core, Level 1 and Level 2 Compliance|
|Support for Built-in Client-side Tracing|
|Configurable for Scalability|
|Ability to restrict connections based on application, IP address, username, requested database|
|Ability to override connection parameters on the server|
|Operating-system user authentication|
|Auto-Discovery of SQL Server instances|
|Database mirroring compatibility|
|Multiple Active Result Sets (MARS)|
|Named Instance Support|
|Snapshot transaction isolation levels|
|SQL Server Express Support|
|XA-Based Two-Phase Commit|
Our ODBC driver for SQL Server allows you to connect desktop applications such as Microsoft Access and Excel/Query, OpenOffice, reporting tools such as Crystal Reports/Business Objects, and more, to your backend database.
Additionally, our ODBC driver facilitates database connectivity for developers programming in scripting languages such as Perl (using DBI and DBD::ODBC), Python (using mxODBC or PyODBC), Ruby, SoftIntegration's Ch language, C and using the Microsoft Visual Studio 2005 IDE.
This document is empty and basically useless. It is generated by a web service that can make some statements in HTML Microdata format. This time the service made zero such statements, sorry.