From 8dc00972918cb25d5a6bd6c5839675c28b2a1b3a Mon Sep 17 00:00:00 2001 From: Deepesh Dhake Date: Sun, 23 Aug 2026 22:53:05 -0500 Subject: [PATCH 1/2] Clarify file extension conventions for backups Updated best practice recommendations for backup file extensions. --- .../back-up-and-restore-of-sql-server-databases.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/relational-databases/backup-restore/back-up-and-restore-of-sql-server-databases.md b/docs/relational-databases/backup-restore/back-up-and-restore-of-sql-server-databases.md index 27a321b5fbb..a80d67c1173 100644 --- a/docs/relational-databases/backup-restore/back-up-and-restore-of-sql-server-databases.md +++ b/docs/relational-databases/backup-restore/back-up-and-restore-of-sql-server-databases.md @@ -105,9 +105,9 @@ Designing an effective backup and restore strategy requires careful planning, im The accounts that perform backup or restore operations shouldn't be granted more privileges than necessary. Review [backup](../../t-sql/statements/backup-transact-sql.md#permissions) and [restore](../../t-sql/statements/restore-statements-transact-sql.md#permissions) for specific permission details. It's recommended that backups are [encrypted](../security/encryption/transparent-data-encryption.md) and, if possible, [compressed](backup-compression-sql-server.md). -To ensure security, backup files should have extensions that follow proper conventions: +Use consistent file extensions to make backups easier to identify and manage. SQL Server doesn't require or enforce these extensions, but following a convention helps with operational tasks such as configuring antivirus exclusions for backup files: -- Database backup files should have the `.BAK` extension +- Database backup files should have the `.BAK` extension. - Log backup files should have the `.TRN` extension. ### Use Separate Storage From 5c313d89d85c7df74907026dc1a291390fdc8ed9 Mon Sep 17 00:00:00 2001 From: Deepesh Dhake Date: Mon, 24 Aug 2026 10:11:25 -0500 Subject: [PATCH 2/2] Potential fix for pull request finding Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com> --- .../back-up-and-restore-of-sql-server-databases.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/relational-databases/backup-restore/back-up-and-restore-of-sql-server-databases.md b/docs/relational-databases/backup-restore/back-up-and-restore-of-sql-server-databases.md index a80d67c1173..63233cc1fe7 100644 --- a/docs/relational-databases/backup-restore/back-up-and-restore-of-sql-server-databases.md +++ b/docs/relational-databases/backup-restore/back-up-and-restore-of-sql-server-databases.md @@ -105,7 +105,7 @@ Designing an effective backup and restore strategy requires careful planning, im The accounts that perform backup or restore operations shouldn't be granted more privileges than necessary. Review [backup](../../t-sql/statements/backup-transact-sql.md#permissions) and [restore](../../t-sql/statements/restore-statements-transact-sql.md#permissions) for specific permission details. It's recommended that backups are [encrypted](../security/encryption/transparent-data-encryption.md) and, if possible, [compressed](backup-compression-sql-server.md). -Use consistent file extensions to make backups easier to identify and manage. SQL Server doesn't require or enforce these extensions, but following a convention helps with operational tasks such as configuring antivirus exclusions for backup files: +Use consistent file extensions to make backups easier to identify and manage. SQL Server doesn't require or enforce these extensions, but following a convention helps with operational tasks such as configuring antivirus exclusions for backup files. For more information, see [Configure antivirus software to work with SQL Server](/troubleshoot/sql/database-engine/security/antivirus-and-sql-server). - Database backup files should have the `.BAK` extension. - Log backup files should have the `.TRN` extension.