Skip to content

Enhance documentation on FAST_FORWARD cursor behavior - #10369

Open
HugoKornelis wants to merge 1 commit into
MicrosoftDocs:livefrom
HugoKornelis:patch-16
Open

Enhance documentation on FAST_FORWARD cursor behavior#10369
HugoKornelis wants to merge 1 commit into
MicrosoftDocs:livefrom
HugoKornelis:patch-16

Conversation

@HugoKornelis

Copy link
Copy Markdown
Contributor

Clarified behavior of FAST_FORWARD cursors and their runtime choices. Added a link for additional background on SQL Server fast-forward server cursors.

Clarified behavior of FAST_FORWARD cursors and their runtime choices. Added a link for additional background on SQL Server fast-forward server cursors.
@prmerger-automator

Copy link
Copy Markdown
Contributor

@HugoKornelis : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.

@prmerger-automator

Copy link
Copy Markdown
Contributor

@HugoKornelis : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.

@learn-build-service-prod

Copy link
Copy Markdown
Contributor

Learn Build status updates of commit a35f004:

✅ Validation status: passed

File Status Preview URL Details
docs/t-sql/language-elements/declare-cursor-transact-sql.md ✅Succeeded

For more details, please refer to the build report.

@v-regandowner
v-regandowner requested a review from Copilot August 3, 2026 16:14
@v-regandowner

Copy link
Copy Markdown
Contributor

@rwestMSFT

Can you review the proposed changes?

IMPORTANT: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@prmerger-automator prmerger-automator Bot added the aq-pr-triaged tracking label for the PR review team label Aug 3, 2026

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR clarifies how FAST_FORWARD cursors can be implemented by SQL Server and highlights that the implementation choice is made at execution time, which can affect visibility of concurrent changes. It also adds an external reference for additional background.

Changes:

  • Added guidance that FAST_FORWARD can be implemented as either STATIC or DYNAMIC, and that the choice can change between executions.
  • Added an external link to background information on fast-forward server cursors.

Comment on lines +145 to +147
A `FAST_FORWARD` cursor can either behave as a `STATIC` cursor or as a 'DYNAMIC' cursor. This choice is made at run time, depending on estimated costs, and the choice can change between executions. Since this choice affects whether concurrent modifications are visible to the cursor or not, such a run time change might impact your results. If your application requires that concurrent updates are visible, use a `DYNAMIC` or `KEYSET` cursor instead. If your application requires that concurrent updates are not visible, use a `STATIC` cursor instead.

For some more background, see https://techcommunity.microsoft.com/blog/sqlserver/understanding-sql-server-fast-forward-server-cursors/383556.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants