PRB: RDO Rowcount Returns Zero For Large SQL Server Recordsets (283845)
The information in this article applies to:
- Microsoft Visual Basic Enterprise Edition for Windows 5.0, when used with:
- Microsoft SQL Server 7.0 Service Pack 1
- Microsoft SQL Server 7.0 Service Pack 2
- Microsoft SQL Server 2000 (all editions)
- Microsoft Visual Basic Enterprise Edition for Windows 6.0, when used with:
- Microsoft SQL Server 7.0 Service Pack 1
- Microsoft SQL Server 7.0 Service Pack 2
- Microsoft SQL Server 2000 (all editions)
- Microsoft Visual Basic Enterprise Edition for Windows 6.0 SP3, when used with:
- Microsoft SQL Server 7.0 Service Pack 1
- Microsoft SQL Server 7.0 Service Pack 2
- Microsoft SQL Server 2000 (all editions)
- Microsoft Visual Basic Enterprise Edition for Windows 6.0 SP4, when used with:
- Microsoft SQL Server 7.0 Service Pack 1
- Microsoft SQL Server 7.0 Service Pack 2
- Microsoft SQL Server 2000 (all editions)
This article was previously published under Q283845 SYMPTOMS
When returning large rowsets through Remote Data Objects (RDO) from Microsoft SQL Server, rowsets that contain a large number of records may return a rowcount of 0.
CAUSE
This occurs if the cursor threshold configuration setting for the SQL Server server has been changed from the default value of -1 to 0 or some other positive value.
Setting the cursor threshold value to 0 forces SQL Server to execute all queries asynchronously. Setting the cursor threshold value to a positive number causes SQL Server to execute asynchronously all queries that return a larger number of rows than the chosen setting. In either case, it is impossible for RDO to determine an accurate rowcount from asynchronous queries.
RESOLUTION
Change the cursor threshold configuration setting to a lower value, or to -1.
STATUS
This behavior is by design.
REFERENCES
SQL Server Books Online, topic: "Cursor Threshold"
Modification Type: | Minor | Last Reviewed: | 7/15/2004 |
---|
Keywords: | kbprb kbRDO KB283845 |
---|
|