SQL Server 2000 Cursor Management and ADO 
Author Message
 SQL Server 2000 Cursor Management and ADO

I was reading in a SQL Server 2000 book about Cursors in T-
SQL. It says that there are 4 types of cursors with the
Static being the most expensive in resources and the
firehose (forward-only) the most efficient for read-
only/forward-only access. However, it says that in T-SQL,
when a firehose cursor is created, but the table has
triggers, SQL Server 2K will convert automatically the
cursor to a static cursor.
My question is in regards to ADO. ADO uses API cursors
rather than T-SQL cursors, but I was wondering if the same
remains true. If I create a Server-Side/forward-only
cursor in ADO (similar to the firehose in T-SQL) and my
table has triggers, will SQL Server 2K create a static
cursor internally, thus eliminating the gains the ADO
developer (VB or C++) thinks is gaining?
Any feedback is welcomed.
Thanks.


Tue, 31 Aug 2004 22:53:02 GMT  
 
 [ 1 post ] 

 Relevant Pages 

1. VB6: Oracle 8/SQL Server 2000 compatibility problems using ADO 2.5 and SQL

2. VB6: Oracle 8/SQL Server 2000 compatibility problems using ADO 2.5 and SQL Syntax

3. VB6: Oracle 8/SQL Server 2000 compatibility problems using ADO 2.5 and SQL Syntax

4. VB6 application using SQL Server 2000 migrating db to SQL Server 2

5. SQL Server 2000, VB 6.0, ADO

6. VB6/SQL Server 2000 ADO Best Practices question

7. ADO error trapping in VB + SQL Server 2000

8. retrieve primary key after insert statement (using ADO / SQL Server 2000)

9. SQL Server 2000 and ADO

10. Excel 2002 hanging when using ADO (vba) + SQL Server 2000

11. ADO DLL VB6 - SQL Server 2000

12. multiple parameters with ADO and SQL Server 2000 Stored proc

 

 
Powered by phpBB® Forum Software