INF: ODBC Catalog Functions in Static CursorsID: Q149923
|
The 2.65.0201 or later versions of the Microsoft SQL Server ODBC Driver support calling the ODBC catalog API functions while using static server cursors. This does not mean that the catalog stored procedures themselves can be called from within a static server cursor.
The section "Additional ODBC SQL Server Driver Information" in the SQL
Server 6.5 "Programing ODBC for SQL Server" manual states that the ODBC
catalog API functions can be called while using a static server cursor.
Users who know that the Microsoft SQL Server Driver implements the ODBC
Catalog API functions as calls to SQL Server catalog stored procedures (for
example, SQLTables was implemented as a call to sp_tables) may assume this
means that static cursors can be opened on the catalog stored procedures.
However, this is not a correct assumption. SQL Server 6.5 still has the
restriction that server cursors can only be opened for a single select
statement, or an execution of a procedure which contains only a single
select statement. This prevents opening server cursors against the catalog
stored procedures, because the procedures contain more than a single select
statement. What the sentence in the manual is saying is that the ODBC
Catalog API functions have been changed so that they can be called when the
application has set its statement or connection options to use static
cursors.
In SQL Server 6.5, the implementation of the ODBC catalog functions was so
that the Microsoft SQL Server ODBC Driver driver does not open a cursor
directly on the underlying catalog stored procedure using a static cursor.
It instead:
Additional query words: cursor odbc
Keywords : kbprg kbusage SSrvProg SSrvStProc
Version : 6.5
Platform : WINDOWS
Issue type : kbhowto
Last Reviewed: March 25, 1999