Skip to content

State the pre-2016 default of TARGET_RECOVERY_TIME correctly - #10505

Open
Rudi Bruchez (rudi-bruchez) wants to merge 1 commit into
MicrosoftDocs:livefrom
rudi-bruchez:fix/target-recovery-time-older-default
Open

Rudi Bruchez (rudi-bruchez) wants to merge 1 commit into
MicrosoftDocs:livefrom
rudi-bruchez:fix/target-recovery-time-older-default

Conversation

@rudi-bruchez

Copy link
Copy Markdown
Contributor

What's wrong

The description of target_recovery_time reads: "When greater than 0 (the default for older versions), specifies the upper-bound on the recovery time". The parenthesis attaches "the default for older versions" to "greater than 0", which reads as if older versions defaulted to a positive value. Before SQL Server 2016 the default was 0, meaning automatic checkpoints, as two other pages state:

  • Database checkpoints, table of checkpoint types: "The default is 0 for older versions, which indicates that the database will use automatic checkpoints".
  • ALTER DATABASE SET options, TARGET_RECOVERY_TIME: "For older versions the default is 0, which indicates that the database uses automatic checkpoints".

Evidence

Documentation only: the two pages above agree with each other and contradict this sentence.

Change

Moves the pre-2016 default into its own sentence, worded as in the two pages above, and leaves the definition of a value greater than 0 unchanged.

@prmerger-automator

Copy link
Copy Markdown
Contributor

Rudi Bruchez (@rudi-bruchez) : 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 5642d72:

✅ Validation status: passed

File Status Preview URL Details
docs/relational-databases/logs/change-the-target-recovery-time-of-a-database-sql-server.md ✅Succeeded

For more details, please refer to the build report.

@ShannonLeavitt

Copy link
Copy Markdown
Contributor

adbadram

Could 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 Nov 18, 2026
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.

3 participants