Skip to content

Fix MS_EXPRESS typo for MS_XPRESS in BACKUP - #10476

Open
Rudi Bruchez (rudi-bruchez) wants to merge 1 commit into
MicrosoftDocs:livefrom
rudi-bruchez:fix/backup-ms-xpress-typo
Open

Rudi Bruchez (rudi-bruchez) wants to merge 1 commit into
MicrosoftDocs:livefrom
rudi-bruchez:fix/backup-ms-xpress-typo

Conversation

@rudi-bruchez

Copy link
Copy Markdown
Contributor

What's wrong

Under LEVEL and ALGORITHM, the page names the algorithm MS_EXPRESS twice. The algorithm is MS_XPRESS, as the same paragraph says a few words later ("The default is MS_XPRESS"), and ALGORITHM = MS_EXPRESS isn't a valid value.

Evidence

SQL Server 2025 CU7 (17.0.4065.4), Linux. BACKUP ... WITH COMPRESSION (ALGORITHM = MS_XPRESS, LEVEL = MEDIUM) succeeds, and msdb.dbo.backupset.compression_algorithm reports MS_XPRESS. The level does affect MS_XPRESS: 597.5 MB at LOW, 575.8 MB at MEDIUM, 574.0 MB at HIGH on the same 1,422 MB database.

Change

Replaces the two occurrences of MS_EXPRESS with MS_XPRESS.

@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 0c41420:

✅ Validation status: passed

File Status Preview URL Details
docs/t-sql/statements/backup-transact-sql.md ✅Succeeded

For more details, please refer to the build report.

@Court72

Copy link
Copy Markdown
Contributor

Umachandar Jayachandran (@uc-msft)

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 Oct 30, 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