= uda.odbc.st.odbc-sqlserver-st %TOC% = ODBC Drivers for Microsoft SQL Server %TOC% ODBC Drivers for Microsoft SQL Server The Single-Tier ODBC Drivers for Microsoft SQL Server are a single component installed on a data-consuming machine - depending on the architecture in which the driver is deployed, either a client such as a desktop, a workstation or an application-server machine. No components need be installed on the database server. The [[OpenLink]] Single-Tier Drivers for Microsoft SQL Server are a Type-B class of driver developed using the Microsoft SQL Server TDS network (wire) protocol interface eliminating the need for the installation of any Microsoft SQL Server-specific client networking software. [[/images/odbcsqlserverst.gif|]] /Microsoft SQL Server Single-Tier Architecture Diagram Image scaled down; Click to enlarge./ | Platform Support | Support for client, server, and application server operating systems | | 32- and 64-bit components | Enables the development and utilization of 32- or 64-Bit DBMS independent applications. | Broad Operating System Support | Enables the development of ODBC compliant applications and the utilization of ODBC Drivers on non Windows platforms such as; Linux (x86, PPC, Itanium, Opteron), Mac OS X, Mac OS Classic, [[FreeBSD]] , Solaris, AIX, HP-UX, HP True64 UNIX, IRIX, Altix, SCO [[UnixWare]] , and others. | | Database Engine Support | Backend database engine support | | Broad backend Database Support | Enables DBMS independent application utilization and deployment across a vast array of industry leading DBMS engines that includes; Oracle (7.x - 10.x), SQL Server (6.x - 2005), DB2 (6.x - 8.x), Sybase (10.x - 12.x), Progress (7.x - 10.x), Ingres (6.4 - II family), Informix (5.x - 9.x & IDS 2000), [[MySQL]] , and [[PostgreSQL]] . | Performance | | Blistering Performance | Delivery of data access performance levels across ODBC, JDBC, ADO.NET and OLE DB that don't compromise viability of DBMS independent application development and deployment. | Network Aware Record Retrieval | Enabling the retrieval and insertion of multiple DBMS records in batches over the network with a minimal number of network hops. | | Usability | | Wire Protocol Based Driver | The use of the TDS wire-protocol facilitates direct connectivity from Driver to Database Server. This alleviates the need to install any additional client side networking software as part of the driver installation and configuration process | Administration | Configuration and Management | | Single Component Installation Process | In situations where DBMS vendor networking is already in place, Single-Tier Drivers provide ease of installation and configuration since you are only required to install a single client component that inherently depends on existing DBMS specific networking for remote data access. | Standards Compliance | | International character support | Enables the development and deployment of international applications that are independent of underlying database engine. | Standards Compliance | | ODBC 3.5 Compliance | Enables broad compatibility between an extensive collection of older and newer ODBC Applications across an array of platforms. | Performance | | Multithreaded | Enables exploitation of scalability benefits arising from the use of multiple CPUs or Clusters while developing or using DBMS independent applications. | Standards Compliance | | Supports Advanced Data Access API functionality | Enables the development and utilization of DBMS application with DBMS independent granularity that extends to challenging areas such as scalar function calls, dates and timestamps manipulation, outer join handling, and SQL stored procedure invocation etc. | Complete ODBC Scrollable Cursor Model Support | Provides ODBC compliant applications with a flexible model for handling sensitivity to data changes using the following scrollable cursor models: Forward-Only, Static, [[KeySet]] , Dynamic, and Mixed. | ----