Cursor Programming Details
Choosing the correct cursor options is an important part of developing a Microsoft SQL Server application.
Using block cursors can reduce the number of network roundtrips between the client and SQL Server, thereby improving performance. SQL Server may implicitly convert a cursor type if you execute a Transact-SQL statement not supported by the cursor type you requested. SQL Server populates the keyset of a large keyset-driven cursor asynchronously, which shortens the time between when the cursor is opened and when you can fetch the first rows.
In This Section
Topic |
Description |
|---|---|
Provides guidance on selecting an appropriate cursor type. |
|
Describes how to use block cursors to efficiently retrieve multiple rows in each fetch operations. |
|
Explains implicit cursor conversions and the factors that trigger SQL Server to implicitly convert a cursor from one type to another. |
|
Explains the benefits of populating large keyset-driven or static cursors asynchronously. |
|
Describes the scope of global and local cursors names. |
|
Describes ways to return metadata describing a server cursor. |
|
Explains the cursors types supported in distributed queries. |