Merge pull request #34107 from rwestMSFT/rw-0519-fix-links

v-shils · web-flow · commit 3b336525f8a1 · 2025-05-19T11:56:32.000-07:00
[SCOPED] Fix links
diff --git a/docs/includes/sql-server-servicing-updates-version-15.md b/docs/includes/sql-server-servicing-updates-version-15.md
@@ -7,4 +7,4 @@ ms.topic: include
 ---
 ## SQL Server 2019 servicing updates
 
-For current information about SQL Server servicing updates, see [https://support.microsoft.com/help/4518398](https://support.microsoft.com/help/4518398).
+For current information about SQL Server servicing updates, see [SQL Server 2019 build versions](/troubleshoot/sql/releases/sqlserver-2019/build-versions).
diff --git a/docs/linux/sql-server-linux-replication.md b/docs/linux/sql-server-linux-replication.md
@@ -16,7 +16,7 @@ monikerRange: ">=sql-server-2017 || >=sql-server-linux-2017"
 
 [!INCLUDE [SQL Server - Linux](../includes/applies-to-version/sql-linux.md)]
 
-[!INCLUDE [SQL Server 2017](../includes/sssql17-md.md)] ([CU18](https://support.microsoft.com/help/4527377)) and later support SQL Server Replication for instances of SQL Server on Linux.
+[!INCLUDE [SQL Server 2017](../includes/sssql17-md.md)] ([CU18](/troubleshoot/sql/releases/sqlserver-2017/cumulativeupdate18)) and later support SQL Server Replication for instances of SQL Server on Linux.
 
 Configure replication on Linux with SQL Server Management Studio (SSMS) [replication stored procedures](../relational-databases/system-stored-procedures/replication-stored-procedures-transact-sql.md).
 
diff --git a/docs/linux/sql-server-linux-whats-new.md b/docs/linux/sql-server-linux-whats-new.md
@@ -18,7 +18,7 @@ ms.custom:
 
 This article describes the major features and services available for [!INCLUDE [sssql17-md](../includes/sssql17-md.md)] running on Linux.
 
-In addition to these capabilities in this article, cumulative updates (CUs) are released at regular intervals. These cumulative updates provide many improvements and fixes. For detailed information about the latest CU release, see <https://aka.ms/sql2017cu>. For package downloads and known issues, see [Release notes for SQL Server 2017 on Linux](sql-server-linux-release-notes-2017.md).
+In addition to these capabilities in this article, cumulative updates (CUs) are released at regular intervals. These cumulative updates provide many improvements and fixes. For detailed information about the latest CU release, see [SQL Server 2017 build versions](/troubleshoot/sql/releases/sqlserver-2017/build-versions). For package downloads and known issues, see [Release notes for SQL Server 2017 on Linux](sql-server-linux-release-notes-2017.md).
 
 ## Ubuntu 18.04 support
 
diff --git a/docs/machine-learning/r/r-server-standalone.md b/docs/machine-learning/r/r-server-standalone.md
@@ -85,7 +85,7 @@ Standalone servers can use the [operationalization](/machine-learning-server/wha
 
 SQL Server releases cumulative updates on a regular basis. Applying the cumulative updates adds security and functional enhancements to an existing installation.
 
-Descriptions of new or changed functionality can be found in the [CAB Downloads](../install/sql-ml-cab-downloads.md) article and on the web pages for [SQL Server 2016 cumulative updates](https://support.microsoft.com/help/3177312/sql-server-2016-build-versions) and [SQL Server 2017 cumulative updates](/troubleshoot/sql/releases/sqlserver-2017/build-versions).
+Descriptions of new or changed functionality can be found in the [CAB Downloads](../install/sql-ml-cab-downloads.md) article and on the build version articles for [SQL Server 2016](/troubleshoot/sql/releases/sqlserver-2016/build-versions), [SQL Server 2017](/troubleshoot/sql/releases/sqlserver-2017/build-versions), and [SQL Server 2019](/troubleshoot/sql/releases/sqlserver-2019/build-versions).
 
 For more information on how to apply updates to an existing instance, see [Apply updates](../install/sql-machine-learning-standalone-windows-install.md#apply-cu) in the installation instructions.
 
diff --git a/docs/machine-learning/troubleshooting/common-issues-external-script-execution.md b/docs/machine-learning/troubleshooting/common-issues-external-script-execution.md
@@ -208,7 +208,7 @@ To avoid this problem, be sure to install any new features at the same patch lev
 
 > [!NOTE] 
 > On older systems, Launchpad can fail to start if there is an 8dot3 notation requirement. This requirement has been removed in later releases. SQL Server 2016 R Services customers should install one of the following:
-> * SQL Server 2016 SP1 and CU1: [Cumulative Update 1 for SQL Server](https://support.microsoft.com/help/3208177/cumulative-update-1-for-sql-server-2016-sp1).
+> * SQL Server 2016 SP1 and CU1: [Cumulative Update 1 for SQL Server 2016 SP1](/troubleshoot/sql/releases/sqlserver-2016/servicepack1-cumulativeupdate1).
 > * SQL Server 2016 RTM, Cumulative Update 3, and this [hotfix](https://support.microsoft.com/help/3210110/on-demand-hotfix-update-package-for-sql-server-2016-cu3), which is available on demand.
 
 For compatibility with R, SQL Server 2016 R Services (In-Database) required the drive where the feature is installed to support the creation of short file names by using *8dot3 notation*. An 8.3 file name is also called a *short file name*, and it's used for compatibility with earlier versions of Microsoft Windows or as an alternative to long file names.
diff --git a/docs/relational-databases/policy-based-management/check-disk-input-and-output-subsystem-for-io-delay-problems.md b/docs/relational-databases/policy-based-management/check-disk-input-and-output-subsystem-for-io-delay-problems.md
@@ -29,6 +29,5 @@ helpviewer_keywords:
   
 ## Related content
 
- [Microsoft Knowledge Base article 897284](https://go.microsoft.com/fwlink/?linkid=117743)  
-  
- [SQL Server I/O Basics, Chapter 2](/previous-versions/sql/sql-server-2005/administrator/cc917726(v=technet.10))
+- [Troubleshoot slow SQL Server performance caused by I/O issues](/troubleshoot/sql/database-engine/performance/troubleshoot-sql-io-performance)
+- [SQL Server I/O Basics, Chapter 2](/previous-versions/sql/sql-server-2005/administrator/cc917726(v=technet.10))
diff --git a/docs/relational-databases/security/encryption/create-identical-symmetric-keys-on-two-servers.md b/docs/relational-databases/security/encryption/create-identical-symmetric-keys-on-two-servers.md
@@ -88,7 +88,7 @@ monikerRange: "=azuresqldb-current||>=sql-server-2016||>=sql-server-linux-2017||
 SQL Server 2016 uses the SHA1 hashing algorithm for its encryption work. Starting in SQL Server 2017, SHA2 is used instead. This means extra steps might be necessary to have your SQL Server 2017 installation decrypt items that were encrypted by SQL Server 2016. Here are the extra steps:
 
 - Ensure your SQL Server 2017 is updated to at least Cumulative Update 2 (CU2).
-  - See [Cumulative Update 2 (CU2) for SQL Server 2017](https://support.microsoft.com/help/4052574) for important details.
+  - See [Cumulative Update 2 for SQL Server 2017](/troubleshoot/sql/releases/sqlserver-2017/cumulativeupdate2) for important details.
 - After you install CU2, turn on trace flag 4631 in SQL Server 2017: `DBCC TRACEON(4631, -1);`
   - Trace flag 4631 is new in SQL Server 2017. Trace flag 4631 needs to be `ON` globally before you create the master key, certificate, or symmetrical key in SQL Server 2017. This enables these created items to interoperate with SQL Server 2016 and earlier versions. This trace flag should only be turned on temporarily to do the re-encryption of data with SHA2-derived keys.
 
diff --git a/docs/relational-databases/security/encryption/sql-server-connector-registry-modification.md b/docs/relational-databases/security/encryption/sql-server-connector-registry-modification.md
@@ -59,7 +59,7 @@ To upgrade the SQL Server Connector (Version: 1.0.5.0 with a Date Published: Sep
 > - SQL Server Connector versions 1.0.0.440 and older have been replaced and are no longer supported in production environments. For more information on troubleshooting SQL Server Connector issues, see [SQL Server Connector Maintenance & Troubleshooting](../../../relational-databases/security/encryption/sql-server-connector-maintenance-troubleshooting.md).
 > - Starting with version 1.0.3.0, the SQL Server Connector reports relevant error messages to the Windows event logs for troubleshooting.
 > - Starting with [1.0.4.0: (version 13.0.811.168)](https://download.microsoft.com/download/8/0/9/809494f2-bac9-4388-ad07-7eaf9745d77b/SQL%20Server%20Connector%20for%20Microsoft%20Azure%20Key%20Vault%201.0.4.0.msi), there is support for private Azure clouds, including Azure operated by 21Vianet, Azure Germany, and Azure Government.
-> - There is a breaking change in version 1.0.5.0 in terms of the thumbprint algorithm. You may experience database restore failures after upgrading to 1.0.5.0. For more information, see [KB article 447099](https://support.microsoft.com/help/4470999/db-backup-problems-to-sql-server-connector-for-azure-1-0-5-0).
+> - There is a breaking change in version 1.0.5.0 in terms of the thumbprint algorithm. You may experience database restore failures after upgrading to 1.0.5.0. For more information, see [Error 33111 when restoring backups from older versions of SQL Server Connector for Microsoft Azure Key Vault](/troubleshoot/sql/database-engine/backup-restore/error-33111-restore-issues-sql-connector).
 > - **Starting with version [1.0.5.0 (with a file date of September 2020)](https://www.microsoft.com/en-us/download/details.aspx?id=45344), the SQL Server Connector supports filtering messages and network request retry logic.**
 > - *The old version of the SQL Server Connector is also version: [1.0.5.0 (version 15.0.300.96) – File date January 2018](https://download.microsoft.com/download/8/0/9/809494f2-bac9-4388-ad07-7eaf9745d77b/1033_15.0.2000.367/SQLServerConnectorforMicrosoftAzureKeyVault.msi)*. Upgrade to the newest SQL Server Connector if you experience any issues.
 
diff --git a/docs/sql-server/sql-server-2016-release-notes.md b/docs/sql-server/sql-server-2016-release-notes.md
@@ -148,7 +148,7 @@ For more information, see [KB5007039](https://support.microsoft.com/topic/kb5007
 
 - :::image type="icon" source="../includes/media/download.svg" border="false"::: **[Download SQL Server 2016 Service Pack 2 (SP2)](https://www.microsoft.com/download/details.aspx?id=56836)**
 
-- For a complete list of updates, see [SQL Server 2016 Service Pack 2 release information](https://support.microsoft.com/help/4052908/sql-server-2016-service-pack-2-release-information)
+- For a complete list of updates, see [SQL Server 2016 Service Pack 2 release information](/troubleshoot/sql/releases/sqlserver-2016/servicepack2).
 
 The [!INCLUDE [sssql16-md](../includes/sssql16-md.md)] SP2 installation might require restart after installation. As a best practice, you should perform a restart following the installation of [!INCLUDE [sssql16-md](../includes/sssql16-md.md)] SP2.
 
diff --git a/docs/sql-server/sql-server-2017-release-notes.md b/docs/sql-server/sql-server-2017-release-notes.md
@@ -18,7 +18,7 @@ This article describes limitations and issues with SQL Server 2017. For related
 
 - [What's new in SQL Server 2017](what-s-new-in-sql-server-2017.md)
 - [Release notes for SQL Server 2017 on Linux](../linux/sql-server-linux-release-notes-2017.md)
-- [SQL Server 2017 Cumulative updates](https://aka.ms/sql2017cu) for information about the latest cumulative update (CU) release
+- [SQL Server 2017 build versions](/troubleshoot/sql/releases/sqlserver-2017/build-versions) for information about the latest cumulative update (CU) release
 
 ## Try SQL Server
 
diff --git a/docs/sql-server/what-s-new-in-sql-server-2017.md b/docs/sql-server/what-s-new-in-sql-server-2017.md
@@ -17,7 +17,7 @@ SQL Server 2017 represents a major step towards making SQL Server a platform tha
 :::image type="icon" source="../includes/media/download.svg"::: **[Download SQL Server 2017 Release - October 2017](https://go.microsoft.com/fwlink/?LinkID=829477)**
 
 > [!NOTE]
-> In addition to the changes below, cumulative updates are released at regular intervals after the GA release. These cumulative updates provide many improvements and fixes. For information about the latest CU release, see [SQL Server 2017 Cumulative updates](https://aka.ms/sql2017cu).
+> In addition to the changes below, cumulative updates are released at regular intervals after the GA release. These cumulative updates provide many improvements and fixes. For information about the latest CU release, see [SQL Server 2017 build versions](/troubleshoot/sql/releases/sqlserver-2017/build-versions).
 
 ## SQL Server 2017 Database Engine
 
diff --git a/docs/t-sql/database-console-commands/dbcc-checktable-transact-sql.md b/docs/t-sql/database-console-commands/dbcc-checktable-transact-sql.md
@@ -132,7 +132,7 @@ Causes `DBCC CHECKTABLE` to check the table for column values that aren't valid
 
 Column-value integrity checks are enabled by default and don't require the `DATA_PURITY` option. For databases upgraded from earlier versions of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)], you can use `DBCC CHECKTABLE WITH DATA_PURITY` to find and correct errors on a specific table; however, column-value checks on the table aren't enabled by default until `DBCC CHECKDB WITH DATA_PURITY` has been run error free on the database. After this, `DBCC CHECKDB` and `DBCC CHECKTABLE` check column-value integrity by default.
 
-Validation errors reported by this option can't be fixed by using DBCC repair options. For information about manually correcting these errors, see Knowledge Base article 923247: [Troubleshooting DBCC error 2570 in SQL Server 2005 and later versions](https://support.microsoft.com/help/923247).  
+Validation errors reported by this option can't be fixed by using DBCC repair options. For information about manually correcting these errors, see [Troubleshoot database consistency errors reported by DBCC CHECKDB](/troubleshoot/sql/database-engine/database-file-operations/troubleshoot-dbcc-checkdb-errors).
 
 If `PHYSICAL_ONLY` is specified, column-integrity checks aren't performed.
 
diff --git a/docs/tools/distributed-replay/sql-server-distributed-replay.md b/docs/tools/distributed-replay/sql-server-distributed-replay.md
@@ -93,7 +93,7 @@ To successfully replay trace data, it must meet the requirements for version and
 Distributed Replay supports input trace data that is collected on the following versions of [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)]:
 
 - [!INCLUDE [sssql19-md](../../includes/sssql19-md.md)]
-- [!INCLUDE [sssql17-md](../../includes/sssql17-md.md)] (Cumulative Update 1 and later versions - see [SQL Server 2017 Cumulative updates](https://aka.ms/sql2017cu))
+- [!INCLUDE [sssql17-md](../../includes/sssql17-md.md)] (Cumulative Update 1 and later versions - see [SQL Server 2017 build versions](/troubleshoot/sql/releases/sqlserver-2017/build-versions))
 - [!INCLUDE [sssql16-md](../../includes/sssql16-md.md)]
 - [!INCLUDE [ssSQL14](../../includes/sssql14-md.md)]
 - [!INCLUDE [ssSQL11](../../includes/sssql11-md.md)]
