Clarify file extension conventions for backups - #10380
Clarify file extension conventions for backups#10380Deepesh Dhake (deepeshd87) wants to merge 2 commits into
Conversation
Updated best practice recommendations for backup file extensions.
|
Deepesh Dhake (@deepeshd87) : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
prmerger-automator
Bot
added
backup-restore/subsvc
Change sent to author
sql/svc
labels
|
Learn Build status updates of commit 8dc0097: ✅ Validation status: passed
For more details, please refer to the build report. |
|
Deepesh Dhake (@deepeshd87) : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
There was a problem hiding this comment.
Pull request overview
Updates SQL Server backup documentation to clarify that .BAK/.TRN are naming conventions (not security features), while still explaining an operational reason to follow them.
Changes:
- Reworded guidance to remove the implication that file extensions provide security properties.
- Added operational rationale for consistent extensions (backup identification/management and antivirus exclusion configuration).
- Added a missing terminal period for consistency in the
.BAKbullet.
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
|
Masha Thomas (MSFT) (@MashaMSFT) Can you review the proposed changes? Important: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
prmerger-automator
Bot
added
the
aq-pr-triaged
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
|
Learn Build status updates of commit 5c313d8: ✅ Validation status: passed
For more details, please refer to the build report. |
The "Best practice recommendations" section listed .BAK/.TRN under "To ensure security," but these extensions are a naming conventions. SQL Server doesn't enforce or read them, and they provide no security property. This rewords the guidance to reflect that, while keeping a concrete operational reason to follow the convention (antivirus exclusion configuration, per Configure antivirus software to work with SQL Server). Also adds a missing terminal period to the .BAK list item for consistency.