Updates from editor

Author: v-phoebh

support/sql/database-engine/backup-restore/backup-restore-operations.md

@@ -1,7 +1,7 @@
 ---
 title: SQL Server backup and restore operation issues
 description: This article troubleshoots SQL Server backup and restore operation issues, such as the operation taking a long time, issues between different SQL Server versions.
-ms.date: 09/10/2021
+ms.date: 03/21/2025
 ms.custom: sap:Database Backup and Restore
 ms.reviewer: ramakoni
 editor: v-jesits
@@ -56,13 +56,13 @@ Backup and restore operations are I/O intensive. Backup/Restore throughput depen
 
 ## Issues that affect database restoration between different SQL Server versions
 
-**Symptoms:**
+**Symptoms**
 
 A SQL Server backup can't be restored to an earlier version of SQL Server than the version at which the backup was created. For example, you can't restore a backup that's taken on a SQL Server 2019 instance to a SQL Server 2017 instance. Otherwise, the following error message appears:
 
 > Error 3169: The database was backed up on a server running version %ls. That version is incompatible with this server, which is running version %ls. Either restore the database on a server that supports the backup, or use a backup that is compatible with this server.
 
-**Resolution:**
+**Resolution**
 
 Use the following method to copy a database that's hosted on a later version of SQL Server to an earlier version of SQL Server.
 
@@ -86,11 +86,11 @@ For more information about how to generate scripts for your database, see [Scrip
 
 ## Backup job issues in Always On environments
 
-**Symptoms:**
+**Symptoms**
 
 You encounter problems that affect backup jobs or maintenance plans in Always On environments.
 
-**Resolution:**
+**Resolution**
 
 - By default, the automatic backup preference is set to **Prefer Secondary**. This specifies that backups should occur on a secondary replica - except if the primary replica is the only replica online. You can't take differential backups of your database by using this setting. To change this setting, use SSMS on your current primary replica, and navigate to **Backup Preferences** page under **Properties** of your availability group.
 - If you're using a maintenance plan or scheduled jobs to generate backups of your databases, make sure to create the jobs for each availability database on every server instance that hosts an availability replica for the availability group.
@@ -102,7 +102,7 @@ For more information about backups in an Always On environment, see the followin
 
 ## Media-related errors when you restore a database from a backup
 
-**Symptoms:**
+**Symptoms**
 
 If you receive error messages that indicate a file issue, this is symptomatic of a corrupted backup file. The following are some examples of errors that you could get if a backup set is corrupted:
 
@@ -113,21 +113,21 @@ If you receive error messages that indicate a file issue, this is symptomatic of
  > 3243: The media family on device '%ls' was created using Microsoft Tape Format version %d.%d. SQL Server supports version %d.%d.
 
 
-**Cause:**
+**Cause**
 
 These issues can occur because of issues that affect the underlying hardware (hard disks, network storage, and so on) or that are related to a virus or malware. Review Windows System event logs and hardware logs for reported errors, and take appropriate action (for example, upgrade firmware or fix networking issues).
 
-**Resolution:**
+**Resolution**
 
 - You can use the [Restore Header](/sql/t-sql/statements/restore-statements-headeronly-transact-sql) statement to check your backup.
-- To reduce occurrence of these restore errors, enable the **Backup CHECKSUM** option when you run a backup to avoid backing up a corrupted database. For more information, see [Possible Media Errors During Backup and Restore (SQL Server)](/sql/relational-databases/backup-restore/possible-media-errors-during-backup-and-restore-sql-server).
+- To reduce the occurrence of these restore errors, enable the **Backup CHECKSUM** option when you run a backup to avoid backing up a corrupted database. For more information, see [Possible Media Errors During Backup and Restore (SQL Server)](/sql/relational-databases/backup-restore/possible-media-errors-during-backup-and-restore-sql-server).
 - You can also enable trace flag 3023 to enable a checksum when you run backups by using backup tools. For more information, see [How to enable the CHECKSUM option if backup utilities don't expose the option](https://support.microsoft.com/topic/how-to-enable-the-checksum-option-if-backup-utilities-do-not-expose-the-option-0d5efb4c-5dfc-0122-c7e3-312a5dd5af3b).
 - To fix these issues, you have to either locate another usable backup file or create a new backup set. Microsoft doesn't offer any solutions that can help retrieve data from a corrupted backup set.
-- If a backup file restores successfully on one server but not on another, try different ways to copy the file between the servers. For example, try [robocopy](/windows-server/administration/windows-commands/robocopy) instead of a regular copy operation. Investigate whether the file is being modified during the copy operation on network or on the destination storage device. 
+- If a backup file restores successfully on one server but not on another, try different ways to copy the file between the servers. For example, try [robocopy](/windows-server/administration/windows-commands/robocopy) instead of a regular copy operation. Investigate whether the file is being modified during the copy operation on the network or the destination storage device. 
 
 ## Backups fail because of permissions issues
 
-**Symptoms:**
+**Symptoms**
 
 When you try to run database backup operations, one of the following errors occurs.
 
@@ -147,13 +147,13 @@ When you try to run database backup operations, one of the following errors occu
     Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.
     ```
 
-**Cause:**
+**Cause**
 
 Either of these scenarios can occur if the SQL Server service account doesn't have Read and Write permissions to the folder that backups are being written to. Backup statements can be run either as part of a job step or manually from SQL Server Management Studio. In either case, they always run under the context of the SQL Server Service startup account. Therefore, if the service account doesn't have the necessary privileges, you receive the error messages that were noted earlier.
 
-**Resolution:**
+**Resolution**
 
-You can check the current permissions of SQL Service account on a folder by navigating to the **Security** tab in the properties of the corresponding folder, selecting the **Advanced** button, and then using the **Effective Access** tab. For more information, see [Backup Devices](/sql/relational-databases/backup-restore/backup-devices-sql-server).
+You can check the current permissions of the SQL Server Service account on a folder by navigating to the **Security** tab in the properties of the corresponding folder, selecting the **Advanced** button, and then using the **Effective Access** tab. For more information, see [Backup Devices](/sql/relational-databases/backup-restore/backup-devices-sql-server).
 
 
 ## Backup or restore operations that use third-party backup applications fail
@@ -182,14 +182,14 @@ SQL Server provides a Virtual Backup Device Interface (VDI) tool. This API enabl
 
 ## Backups might fail if change tracking is enabled
 
-**Symptoms:**
+**Symptoms**
 
-Backups might fail if change tracking is enabled on the databases and returns errors that resemble the following one:
+Backups might fail if change tracking is enabled on the databases and return errors that resemble the following one:
 
-> "Error: 3999, Severity: 17, State: 1.  
-> \<Time Stamp\> spid \<spid\> Failed to flush the commit table to disk in dbid 8 due to error 2601. Check the error log for more information."
+> Error: 3999, Severity: 17, State: 1.  
+> \<Time Stamp\> spid \<spid\> Failed to flush the commit table to disk in dbid 8 due to error 2601. Check the error log for more information.
 
-**Resolution:**
+**Resolution**
 
 To solve the issue, see the following articles:
 
@@ -198,21 +198,21 @@ To solve the issue, see the following articles:
 
 ## Issues restoring backups of encrypted databases
 
-**Symptoms:**
+**Symptoms**
 
 You encounter issues when restoring backups of encrypted databases.
 
-**Resolution:**
+**Resolution**
 
 To solve the issue, see [Move a TDE Protected Database to Another SQL Server](/sql/relational-databases/security/encryption/move-a-tde-protected-database-to-another-sql-server).
 
 ## Fail to restore a CRM backup from the Enterprise edition
 
-**Symptoms:**
+**Symptoms**
 
 You fail to restore a CRM backup from the Enterprise edition on a Standard edition.
 
-**Resolution:**
+**Resolution**
 
 To solve the issue, see [2567984 "Database cannot be started in this edition of SQL Server" error when restoring a Microsoft Dynamics CRM database](https://support.microsoft.com/help/2567984).
   

support/sql/integration-services/ssis-package-doesnt-run-when-called-job-step.md

@@ -1,7 +1,7 @@
 ---
 title: SSIS package does not run when called from a job step
 description: This article provides resolutions for the problem that occurs when you call an SSIS package from a SQL Server Agent job step.
-ms.date: 12/07/2020
+ms.date: 03/21/2025
 ms.custom: sap:Integration Services
 ms.reviewer: craigg
 ---
@@ -91,7 +91,7 @@ OnError,DOMAINNAME,DOMAINNAME\USERNAME,Execute SQL Task,{C6C7286D-57D4-4490-B12D
 
 By using the exec subsystem command approach, you add verbose console logging switches to the SSIS command line to call the Dtexec.exe SSIS command-line executable file. Additionally, you use the Advanced job feature of the output file. You can also use the **Include Step Output in the history** option to redirect the logging information to a file or to the SQL Server Agent Job History.
 
-Here is an example of a command line:
+Here's an example of a command line:
 
 ```console
  dtexec.exe /FILE "C:\_work\SSISPackages\ProtectionLevelTest\ProtectionLevelTest\AgentTesting.dtsx" /MAXCONCURRENT " -1 " /CHECKPOINTING OFF /REPORTING V /CONSOLELOG NCOSGXMT
@@ -114,6 +114,6 @@ Log: Name: OnError Computer: COMPUTERNAME Operator: DOMAINNAME\username Source N
 ## References
 
 - For more information about a similar problem, see [You receive an 'Error loading' error message when you try to run a SQL Server Integration Services package](../integration-services/error-loading-message-run-integration-services-package.md).
-- [Connectivity error 0x80004005 occurs when you run an SSIS package as a SQL Agent job](../database-engine/connect/sql-server-faces-connectivity-issue-ssispack-fail.md)
+- [Connectivity error 0x80004005 occurs when you run an SSIS package as a SQL Agent job](../database-engine/connect/sql-server-faces-connectivity-issue-ssispack-fail.md).
 - For more information about how to create package templates, see [Create a package in SQL Server Data Tools using the Package Template](/sql/integration-services/create-packages-in-sql-server-data-tools#create-a-package-in-sql-server-data-tools-using-the-package-template).
 - For more information about SSIS package security and the `ProtectionLevel` property, see [Protection Level Setting and the SSISDB Catalog](/sql/integration-services/security/access-control-for-sensitive-data-in-packages#protection-level-setting-and-the-ssisdb-catalog).

support/sql/releases/new-mu-servicing-model.md

@@ -1,7 +1,7 @@
 ---
 title: Updates to the Microsoft Update detection logic 
 description: This article describes the updates to the Microsoft Update detection logic for SQL Service servicing.
-ms.date: 01/11/2021
+ms.date: 03/21/2025
 ms.topic: conceptual
 ms.custom: sap:Installation, Patching, Upgrade, Uninstall
 ms.reviewer: jeffwil 

support/sql/ssms/error-click-databases-node.md

@@ -1,7 +1,7 @@
 ---
 title: Error when you click the Databases node
 description: This article describes an error message that typically occurs in SSMS when there is a problem retrieving information about one or more databases of a SQL Server instance.
-ms.date: 11/19/2020
+ms.date: 03/21/2025
 ms.custom: sap:SQL Server Management, Query and Data Tools
 ---
 # Error message when you click the Databases node in SQL Server Management Studio in SQL Server
@@ -21,32 +21,32 @@ You might receive an error message similar to the following one when using SQL S
 
 There can be multiple symptoms that can contribute to this problem. The following items may help you understand and troubleshoot the issue:
 
-- **Symptom 1:**
+- **Symptom 1**
 
   You might run into known issues in the following articles:
 
-  - [SQL Server 2016 Agent fails to start or “Failed to retrieve data” error when you try to read error log from SSMS 2016](https://support.microsoft.com/help/3185365)
+  - [SQL Server 2016 Agent fails to start or "Failed to retrieve data" error when you try to read error log from SSMS 2016](https://support.microsoft.com/help/3185365)
 
   - [KB4550657 - FIX: Error occurs when you interact with SQL Server Agent in SQL Server 2019](https://support.microsoft.com/help/4550657)
 
-  **Resolution:**
+  **Resolution**
 
-   To solve the known issues, see the resolutions documented in the corresponding articles above.
+   To solve the known issues, see the resolutions documented in the corresponding articles listed earlier.
 
-- **Symptom 2:**
+- **Symptom 2**
 
   You can run into this issue if using an older version of SSMS and when one of the following conditions is true:
 
-  - SQL Server Management Studio cannot correctly read one or more databases. Therefore, certain properties of a database cannot be retrieved.
+  - SQL Server Management Studio can't correctly read one or more databases. Therefore, certain properties of a database can't be retrieved.
 
   - One or more databases is in an offline mode and you're using an older version of SSMS to connect to that SQL instance hosting this offline database.
 
-  In these situations, the collection of objects doesn't appear in the **Object Explorer** pane or in the **Object Explorer Details** pane. Therefore, certain properties of the database aren't computed as a group in the collection of objects.
+  In these situations, the collection of objects doesn't appear in the **Object Explorer** pane or the **Object Explorer Details** pane. Therefore, certain properties of the database aren't computed as a group in the collection of objects.
 
   > [!NOTE]
   > This problem also occurs if you're not a member of the Sysadmins group.
 
-  **Resolution:**
+  **Resolution**
 
   To work around this problem, follow these steps:
 
@@ -66,5 +66,5 @@ There can be multiple symptoms that can contribute to this problem. The followin
 
   4. Right-click the **Databases** node, and then select **Refresh**.
 
-  Alternatively, you can download and install SSMS from [Download SQL Server Management Studio (SSMS)](/sql/ssms/download-sql-server-management-studio-ssms) and see if the issue goes away. If the issue still occurs with new version of SSMS, see [SQL Server help and feedback](/sql/sql-server/sql-server-get-help) for additional ways to get assistance with your issue.
+  Alternatively, you can download and install SSMS from [Download SQL Server Management Studio (SSMS)](/sql/ssms/download-sql-server-management-studio-ssms) and see if the issue goes away. If the issue still occurs with the new version of SSMS, see [SQL Server help and feedback](/sql/sql-server/sql-server-get-help) for additional ways to get assistance with your issue.