OpenLink Universal Data Access (UDA) Wiki
Documentation and guidance on installing, configuring and trouble-shooting UDA
Advanced Search
Help?
Location: / Dashboard / UdaWikiWeb / UdaWikiWebIndex / NewUDAFeatures / NewUDAFeaturesMT

New Features in OpenLink UDA v6.0

The following new features are in Universal Data Access Suite version 6.0:

Oracle:

Ingres / OpenIngres:

  • Ingres Native ADO.Net Provider

Generic, cross-database features:

  • Distributed Transaction Support
  • PAM, LDAP & Active Directory support
  • Support for XML Types

New Features in OpenLink UDA v5.2

The following new features are in Universal Data Access Suite version 5.2:

  • 64-bit ODBC Drivers for Windows, Linux, FreeBSD, Solaris, AIX, HP-UX, Tru64 Linux, IRIX across Itanium, Opteron, PA-RISC, IBM Risc, and PowerPC processors
  • Addition of SSL support to the existing data encryption functionality in our Multi-Tier Drivers
  • New ADO.NET managed providers for all supported databases
  • New ODBC.NET provider that facilitates compatability between ADO.NET clients and third-party ODBC Drivers
  • Enhanced ODBC-JDBC Bridge Driver that provides JDBC connectivity to any ODBC or ADO.NET client application
  • JDBC-to-ODBC Bridge Driver that provides ODBC connectivity to Java Application
  • A compatibility layer for Microsoft InfoPath that provides connectivity to non SQL Server and ACCESS databases via ODBC
  • JDBC 3.0-compliant Drivers for version 1.5 of the Java Virtual Machine and SDK

New Features

  • Unicode Driver support

Database agents support the latest releases of all supported database engines this includes:

1. Oracle 8i & 9i
2. Microsoft SQL Server 2000
3. DB/2 v7
4. ODBC Agent
5. JDBC Agent
6. Informix 9
7. Sybase Adaptive Server 12.5
8. Progress 9 (SQL-92)

Note that there are two Multi-tier generic ODBC clients:

1. With Unicode support olod5032u.dll (OpenLink Generic ODBC Driver (Unicode))
2. Without Unicode support olod5032.dll (OpenLink Generic ODBC Driver)

Both of these ODBC clients can be used with a Unicode enabled agent.

  • Zero Configuration

The OpenLink Request Broker can now be configured to Broadcast ZeroConfig services of available Database agents on the network, which then can be discovered by the the OpenLink Multi-Tier ODBC client. Enabling ODBC Datasources to be configured and/or connections made with no knowledge of network topology.

  • Significant SQL Server and SYBASE Driver Enhancements

Our Drivers are now built to communicate directly with Microsoft SQL Server and SYBASE ASE using the TDS protocol (the native wire protocol for both database servers). This also implies that no additional software is required post installation in order for our ODBC Drivers to communicate with these Drivers (this applies to the Single Tier format Drivers only). The use of TDS has also enabled us to double the performance of both our Single Tier and Multi-Tier Drivers for these databases.

  • Array Optimisations on Select Queries

All drivers now support the SQLSetStmtAttr(SQL_ARRAY_SIZE) call for batch select statements, providing improved performance when re-execute select statements with bound paramters.

  • Deferred Fetching

The Release 4 OpenLink driver family brings marked communications layer improvements. Central to these are improved implementation of the SQLGetData and SQLPutData ODBC function calls.
Wholesale vs. Piecemeal Data Transfer

In previous releases of the drivers, parameter data at query execution was assembled in the OpenLink driver's client component and transferred to its server component in a single network hop. (The client and server components apply to both the Single- and Multi-Tier drivers; they refer to different layers within the driver entity.) Similarly, when fetching from a "long", or large binary data column, data was transferred from the driver's server component to the client component in a single network transfer. The only way data could manipulated in a piecemeal fashion, was within the ODBC application from the driver's client component (client side only).

The Release 4 driver family now allow transferring parameter data in parts over the network between the client and server driver components. Once transferred, the fragmented column data are re-pieced together in their entirety within the client and server portions of the driver.
Deferred Fetching

When fetching, data from columns with "long" data are only transferred between the server and client components if one of the following applies to that column:

o It has been "bound" by the application via the SQLBindCol API call
o It has been retrieved via the SQLGetData API call

This mechanism is referred to as deferred fetching. In this method, as "long" column data is not reassembled within the OpenLink ODBC client itself (rather, within the application), driver memory overhead incurred is dramatically reduced. Deferred fetching applies to the following "long" database column types:

ODBC agent:

SQL_LONGVARCHAR

SQL_LONGVARBINARY

DB/2 agent:

SQL_BLOB

SQL_CLOB

SQL_DBCLOB

If the long data compatibility option has been specified in the DB2 database

SQL_LONGVARCHAR

SQL_LONGVARBINARY

SQL_LONGVARGRAPHIC

Oracle agent:

SQLT_BLOB

SQLT_CLOB

Sybase agent:

CS_IMAGE_TYPE

CS_TEXT_TYPE

However, if a table contains a column defined as one of these "long" types, but the actual data stored in the column only fills a small proportion of the available space, deferred fetching is of no benefit. In these cases, performance may be improved by switching off the deferred fetching mechanism using the control in the OpenLink Generic Client data source setup dialog.

Powered By Virtuoso