• Products >
• Support >
• Solutions
• Company
• Blog

• < Back
• ODBC drivers >
• JDBC drivers >
• Bridges, gateways >
• Other >
• All products

• < Back
• JDBC-ODBC Bridge
• JDBC-Access Gateway

• < Back
• ODBC-ODBC Bridge
• ODBC-JDBC Gateway
• dbExpress-ODBC Gateway
• XML-ODBC Server

• < Back
• ODBC-ODBC Join Engine
• SDK
• Consultancy
• Roadmap

A workaround for the "Cursor support is not an implemented feature for SQL Server Parallel DataWarehousing TDS" error

In version 1.7.16, the Easysoft SQL Server ODBC driver changed from using a client cursor to a server cursor when an application's behaviour suggested that it only needed a subset of the data in a query result. This cursor behaviour further aligns our SQL Server ODBC driver with Microsoft's Native Client.

An override for this behaviour was added in version 1.8.10 because if the application actually does want the entire result set, using a server cursor has performance implications, as server cursors are slower.

Another side-effect of this change is this error in SQL Azure:

"Cursor support is not an implemented feature for SQL Server Parallel Data
Warehousing TDS" error

To revert to the previous behaviour for cursors and prevent this error from being generated, add this OVERRIDE line to your the ODBC data source:

[SQLSERVER_SAMPLE]
.
.
.
OVERRIDE=65536

ODBC data sources are normally stored in /etc/odbc.ini.