organization update

Author: sevend2

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

@@ -37,9 +37,9 @@ Backup and restore operations are I/O intensive. Backup/Restore throughput depen
 
 1. Check whether you're experiencing any of the known issues that are listed in the following table. Consider whether you should implement the changes or apply the fixes and best practices that are discussed in the corresponding articles.
 
-    |Knowledge Base or Books Online link|Explanation and recommended actions|
+    |Knowledge Base link|Explanation and recommended actions|
     |---|---|
-    | [Optimizing Backup and Restore Performance in SQL Server](https://technet.microsoft.com/library/ms190954%28v=sql.105%29.aspx)|The Books Online topic covers various best practices that you can use to improve the performance of Backup/Restore operations. For example, you can assign the `SE_MANAGE_VOLUME_NAME` special privilege to the Windows account that's running SQL Server to enable instant initialization of data files. This can produce significant performance gains.|
+    | [Optimizing Backup and Restore Performance in SQL Server](https://technet.microsoft.com/library/ms190954%28v=sql.105%29.aspx)|This article covers various best practices that you can use to improve the performance of Backup/Restore operations. For example, you can assign the `SE_MANAGE_VOLUME_NAME` special privilege to the Windows account that's running SQL Server to enable instant initialization of data files. This can produce significant performance gains.|
     | [2920151 Recommended hotfixes and updates for Windows Server 2012 R2-based failover clusters](https://support.microsoft.com/help/2920151) <br/><br/> [2822241 Windows 8 and Windows Server 2012 update rollup: April 2013](https://support.microsoft.com/help/2822241)|Current system rollups can include fixes for known issues at the system level that can degrade the performance of programs such as SQL Server. Installing these updates can help prevent such issues.|
     | [2878182 FIX: User mode processes in an application are unresponsive on servers that are running Windows Server 2012](https://support.microsoft.com/help/2878182) <br/><br/>|Backup operations are I/O intensive and can be affected by this bug. Apply this fix to help prevent these issues.|
     | [Configure antivirus software to work with SQL Server](../security/antivirus-and-sql-server.md)|Antivirus software may hold locks on .bak files. This can affect the performance of backup and restore operations. Follow the guidance in this article to exclude backup files from virus scans.|
@@ -161,19 +161,30 @@ SQL Server provides a Virtual Backup Device Interface (VDI) tool. This API enabl
   |Backups of case-sensitive databases failing| [2987610 FIX: Error when you back up a database that has case-sensitive collation by using VSS in SQL Server 2012 SP2](https://support.microsoft.com/help/2987610) |
   |Third-party backups that are made by using VSS writer may fail and return 8229 errors.| [2987610 FIX: Error when you back up a database that has case-sensitive collation by using VSS in SQL Server 2012 SP2](https://support.microsoft.com/help/2987610) |
   | Understanding how VDI backup works |[How It Works: SQL Server - VDI (VSS) Backup Resources](https://techcommunity.microsoft.com/t5/sql-server-support/how-it-works-sql-server-vdi-vss-backup-resources/ba-p/315695) |
-  |Azure Site recovery agent reports failure | [ASR Agent or other non-component VSS backup fails for a server hosting SQL Server 2008 R2](https://support.microsoft.com/help/4504103) |
 
 ### More resources
 
 [How It Works: How many databases can be backed up simultaneously?](https://techcommunity.microsoft.com/t5/sql-server-support/how-it-works-how-many-databases-can-be-backed-up-simultaneously/ba-p/315874)
 
-## Miscellaneous issues
+## Backups might fail if change tracking is enabled
 
-|Symptom/scenario|Remedial actions or additional information|
-|---|---|
-|Backups might fail if change tracking is enabled on the databases and returns errors that resemble the following:<br/><br/>"Error: 3999, Severity: 17, State: 1. <br/><br/>\<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."<br/><br/><br/>|See the following Microsoft Knowledge Base articles:<ul><li> [2682488 FIX: Backup operation fails in a SQL Server 2008, in a SQL Server 2008 R2 or in a SQL Server 2012 database after you enable change tracking](https://support.microsoft.com/help/2682488)</li><li> [2603910 FIX: Backup fails in SQL Server 2008, in SQL Server 2008 R2 or in SQL Server 2012 if you enable change tracking on the database](https://support.microsoft.com/help/2603910) </li><li> [2522893 FIX: A backup operation on a SQL Server 2008 or SQL Server 2008 R2 database fails if you enable change tracking on this database](https://support.microsoft.com/help/2522893)</li><ul> |
-|Issues restoring backups of encrypted databases| [Move a TDE Protected Database to Another SQL Server](/sql/relational-databases/security/encryption/move-a-tde-protected-database-to-another-sql-server) |
-|Trying to restore a CRM backup from the Enterprise edition fails on a Standard edition| [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) |
+Backups might fail if change tracking is enabled on the databases and returns 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."
+
+To solve the issue, see the following articles:
+
+- [2682488 FIX: Backup operation fails in a SQL Server 2008, in a SQL Server 2008 R2 or in a SQL Server 2012 database after you enable change tracking](https://support.microsoft.com/help/2682488)
+- [2603910 FIX: Backup fails in SQL Server 2008, in SQL Server 2008 R2 or in SQL Server 2012 if you enable change tracking on the database](https://support.microsoft.com/help/2603910)
+
+## Issues restoring backups of encrypted databases
+
+If you encounter issues when restoring backups of encrypted databases, 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
+
+If you fail to restore a CRM backup from the Enterprise edition on a Standard edition, 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).
   
 ## FAQ about SQL Server backup and restore operations
 
@@ -213,9 +224,9 @@ SQL Server provides a Virtual Backup Device Interface (VDI) tool. This API enabl
 
 ## Reference topics for SQL Server backup and restore operations
 
-- For more information about backup and restore operations, see the following topics in Books Online:
+- For more information about backup and restore operations, see the following article:
 
-   ["Back Up and Restore of SQL Server Databases"](/sql/relational-databases/backup-restore/back-up-and-restore-of-sql-server-databases): This topic covers the concepts of the backup and restore operations for SQL Server databases, provides links to additional topics, and provides detailed procedures to run various backups or restore tasks (such as verifying backups, and backing up by using T-SQL or SSMS). This is the parent topic about this subject in SQL Server documentation.
+   ["Back Up and Restore of SQL Server Databases"](/sql/relational-databases/backup-restore/back-up-and-restore-of-sql-server-databases): This article covers the concepts of the backup and restore operations for SQL Server databases, provides links to additional topics, and provides detailed procedures to run various backups or restore tasks (such as verifying backups, and backing up by using T-SQL or SSMS). This is the parent topic about this subject in SQL Server documentation.
 - The following table lists additional topics that you might want to review for specific tasks that are related to backup and restore operations.
 
     |Reference|Description|

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

@@ -113,15 +113,5 @@ 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 2005 Integration Services package in SQL Server 2005](https://support.microsoft.com/help/904800)
+For more information about how to create package templates, see [How to create a package template in SQL Server Business Intelligence Development Studio](https://support.microsoft.com/help/908018)
 
-- For more information about how to use the Dtutil.exe utility in batch operations, see [How to use the dtutil utility (Dtutil.exe) to set the protection level of a batch of SQL Server Integration Services (SSIS) packages in SQL Server 2005](https://support.microsoft.com/help/906562)
-
-- For more information about how to create package templates, see [How to create a package template in SQL Server Business Intelligence Development Studio](https://support.microsoft.com/help/908018)
-
-- For more information about SSIS package security and the `ProtectionLevel` property, see the **Security Considerations for Integration Services** topic in SQL Server 2005 Books Online.
-
-Unfortunately, users are not aware that default agent job step settings put them in this state. For more information about SQL Server Agent proxies and SSIS, see the following topics in SQL Server 2005 Books Online:
-
-- Scheduling package execution in SQL Server Agent
-- Creating SQL Server Agent proxies

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

@@ -11,11 +11,15 @@ ms.reviewer: jeffwil
 
 _Applies to:_   SQL Server 2019, SQL Server 2017, SQL Server 2016
 
+## Historical servicing baselines
+
 Historically, servicing baselines (RTM or Service Pack) have included the following servicing branches:
 
 - A General Distribution Release (GDR) branch that contains only security and other critical fixes.
 - A cumulative update (CU) branch that contains security and other critical fixes plus all other fixes for the baseline.
 
+## Microsoft update detection logic
+
 The Microsoft Update (MU) detection logic was constructed so that instances at the servicing baseline or along the GDR branch would be offered updates from the GDR branch.
 
 Previously, users had to proactively install at least one CU to align the instance to the CU branch for servicing through MU. However, after that was done, you could not return to the GDR branch for that instance until either of the following changes were made:
@@ -25,13 +29,23 @@ Previously, users had to proactively install at least one CU to align the instan
 
 This logic was established to minimize the changes to the instance if a security update or other critical update was required. Instances on the CU branch have to take all updates that are released for the baseline when a required security or other critical release appears. This includes all nonsecurity changes up to the required security update.
 
-However, this logic created problems for users who tried to manage routine servicing of large sets of instances by using WSUS. This is because the MU logic couldn't be used without first manually updating every client so that it could participate. To work around this issue and still avoid flipping instances to the CU train without explicit user consent, the following changes were made to the MU detection logic for both routine CU servicing and security releases for the more recent servicing releases of baselines in support:
+### Problems with MU logic
+
+However, this logic created problems for users who tried to manage routine servicing of large sets of instances by using WSUS. This is because the MU logic couldn't be used without first manually updating every client so that it could participate. 
+
+### Changes to MU detection logic
+
+To work around this issue and still avoid flipping instances to the CU train without explicit user consent, the following changes were made to the MU detection logic for both routine CU servicing and security releases for the more recent servicing releases of baselines in support:
 
 - Cumulative Updates: The MU detection logic now allows clean instances that are at the baseline (RTM or SP,  with no servicing updates) or that are already updated along the CU branch to receive the update. A CU update does not have to be installed for an instance to be offered the update. However, if the instance has a GDR update, the instance must still be manually updated outside MU to become manageable through MU (WSUS) automation.
 - Security Releases (GDRs): The logic for security releases is now split into the following channels:
+
   - An *Automatic Updates* channel (Microsoft Update) keeps the older historic behavior that requires a CU to be installed on the instance in order for the CU branch version of the security release to be offered. It does this to protect instances from receiving all updates instead of only critical and security-related updates without evidence of the user explicitly opting in to the more extensive mode of servicing.
+
   - A *WSUS / Catalog* channel that uses the new detection logic that allows the CU branch version of the security release to be applied against a clean baseline instance. This is the channel of the release that will be presented to users who go to the Microsoft Update Catalog website.
 
+## Applicable releases
+
 This new updated detection logic applies to the following CU and GDR releases:
 
 - SQL Server 2016 Service Pack 2: CU14 and later CUs

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

@@ -17,9 +17,9 @@ You may receive an error message similar to the following when using SQL Server
 
 > Failed to retrieve data for this request (Microsoft.SqlServer.Management.sdk.sfc)
 
-## Troubleshooting
+## Cause and resolution
 
-There can be multiple causes that can contribute to this problem. The following items may help you understand and troubleshoot the issue:
+There can be multiple causes that can contribute to this problem. The following items may help you understand and troubleshoot the issue:
 
 - Check if you are running into any known issues listed below and use the resolutions documented in the corresponding articles: