fix broken links

Author: HaiyingYu

support/sql/database-engine/performance/recommended-updates-configuration-workloads.md

@@ -70,7 +70,7 @@ Review the content in the **Knowledge Base article or Books Online Resource** co
 | [Compute capacity limits by edition](/sql/sql-server/compute-capacity-limits-by-edition-of-sql-server) The license core limitation for SQL Server 2012|Enterprise Edition that has Server and Client Access License (CAL) licensing is limited to 20 cores per SQL Server instance.<br/><br/>There are no limits under the Core-based Server Licensing model.<br/><br/>Consider upgrading your edition of SQL Server to the appropriate SKU to use all hardware resources.|
 | [Slow performance on Windows Server when using the Balanced power plan](../../../windows-server/performance/slow-performance-when-using-power-plan.md) |Review the article, and work together with your Windows administrator to implement one of the solutions that are listed in the Resolution section of the article.|
 | [optimize for ad hoc workloads Server Configuration Option](/sql/database-engine/configure-windows/optimize-for-ad-hoc-workloads-server-configuration-option) </br></br>[FORCED PARAMETERIZATION](/sql/relational-databases/query-processing-architecture-guide)| Entries in the plan cache are evicted because of growth in other caches or memory clerks. You might also encounter plan cache eviction when the cache reaches its maximum number of entries. In addition to trace flag 8032 discussed above, consider the [optimize for ad hoc workloads](/sql/database-engine/configure-windows/optimize-for-ad-hoc-workloads-server-configuration-option) server option and also the [FORCED PARAMETERIZATION](/sql/relational-databases/query-processing-architecture-guide) database option. |
-| [How to reduce paging of buffer pool memory in SQL Server](https://support.microsoft.com/help/918483)<br/><br/> [Memory configuration and sizing considerations in SQL Server 2012 and later versions](https://support.microsoft.com/help/2663912/) | Assign the [Enable the Lock Pages in Memory Option (Windows)](/sql/database-engine/configure-windows/enable-the-lock-pages-in-memory-option-windows) user right to the SQL service Startup account. See [How to enable the "locked pages" feature in SQL Server 2012](https://support.microsoft.com/help/2659143/). <br/><br/>Set maximum server memory to approximately 90 percent of total physical memory. Make sure that the [Server memory configuration options](/sql/database-engine/configure-windows/server-memory-server-configuration-options) setting accounts for memory from only the nodes that are configured to use affinity mask settings. |
+| [How to reduce paging of buffer pool memory in SQL Server](https://support.microsoft.com/help/918483)<br/><br/> [Memory configuration and sizing considerations in SQL Server 2012 and later versions](https://support.microsoft.com/help/2663912/) | Assign the [Lock Pages in Memory Option (Windows)](/sql/database-engine/configure-windows/enable-the-lock-pages-in-memory-option-windows) user right to the SQL service Startup account. <br/><br/>Set maximum server memory to approximately 90 percent of total physical memory. Make sure that the [Server memory configuration options](/sql/database-engine/configure-windows/server-memory-server-configuration-options) setting accounts for memory from only the nodes that are configured to use affinity mask settings. |
 | [SQL Server and Large Pages Explained...](/archive/blogs/psssql/sql-server-and-large-pages-explained) | Consider enabling [Trace Flag 834](/sql/t-sql/database-console-commands/dbcc-traceon-trace-flags-transact-sql#tf834) if you have a server that has much memory, particularly for an analytical or data warehousing workload. Keep in mind that [Interoperability of Columnstore indexes with large page memory model in SQL Server](https://support.microsoft.com/kb/3210239). |
 | [Query Performance issues associated with a large sized security cache](/archive/blogs/psssql/query-performance-issues-associated-with-a-large-sized-security-cache) <br/><br/>[Queries take a longer time to finish running when the size of the TokenAndPermUserStore cache grows in SQL Server](https://support.microsoft.com/topic/queries-take-a-longer-time-to-finish-running-when-the-size-of-the-tokenandpermuserstore-cache-grows-in-sql-server-2005-ad1622e7-3bb5-7902-19a0-5d0e6271033d) <br/><br/>[DBCC TRACEON - Trace Flags (Transact-SQL)](/sql/t-sql/database-console-commands/dbcc-traceon-trace-flags-transact-sql)| If the security cache grows to a large size and you encounter performance problems and spinlock contention, consider enabling trace flag [T4610](/sql/t-sql/database-console-commands/dbcc-traceon-trace-flags-transact-sql#tf4610) and [T4618](/sql/t-sql/database-console-commands/dbcc-traceon-trace-flags-transact-sql#tf4618) to reduce the maximum size of TokenAndPermuserStore. |
 | [ALTER WORKLOAD GROUP](/sql/t-sql/statements/alter-workload-group-transact-sql) [KB3107401 - New query memory grant options are available (min_grant_percent and max_grant_percent) in SQL Server 2012](https://support.microsoft.com/help/3107401)| If you have many queries that are exhausting large memory grants, reduce `request_max_memory_grant_percent` for the default workload group in the resource governor configuration from the default 25 percent to a lower value. New query memory grant options are available (`min_grant_percent` and `max_grant_percent`) in SQL Server. |
@@ -203,7 +203,7 @@ These recommendations don't require you to enable other trace flags as startup p
 | **Database Mail** FIX: Database Mail cannot connect to SQL Server when non-default TCP port is used| [KB4100873 - FIX: Database Mail cannot connect to SQL Server 2017 on Linux when non-default TCP port is used](https://support.microsoft.com/help/4100873) <br/> Cumulative Update 6 for SQL Server 2017|
 | **Container** FIX: Can't stop the SQL Server Linux Docker container by using the "docker stop" command| [KB4093805 - FIX: Can't stop the SQL Server Linux Docker container by using the "docker stop" command](https://support.microsoft.com/help/4093805) <br/> Cumulative Update 5 for SQL Server 2017|
 | **Container** FIX: Out of memory error when you run SQL Server in a Linux Docker container| [KB4347055 - FIX: Out of memory error when you run SQL Server 2017 in a Linux Docker container](https://support.microsoft.com/help/4347055) <br/> Cumulative Update 10 for SQL Server 2017|
-| **AG**: If you are using Pacemaker package 1.1.18-11.el7 or higher, adjust the start-failure-is-fatal property| [KB4229789 - Cumulative Update 7 for SQL Server 2017](https://support.microsoft.com/help/4229789) <br/> See the **Pacemaker Notice** section|
+| **AG**: If you are using Pacemaker package 1.1.18-11.el7 or higher, adjust the start-failure-is-fatal property| [KB4229789 - Cumulative Update 7 for SQL Server 2017](../../releases/sqlserver-2017/cumulativeupdate7.md) <br/> See the **Pacemaker Notice** section|
 | **AG** FIX: Pacemaker may kill the resource agent processes when operation times out| [KB4460203 - FIX: Pacemaker may kill the resource agent processes when operation times out in SQL Server 2017 Always On Availability Group](https://support.microsoft.com/help/4460203) <br/> Cumulative Update 11 for SQL Server 2017|
 | **AG** FIX: Two SQL Server instances are the primary replica of an availability group| [KB4316791 - FIX: Two SQL Server instances are the primary replica of an availability group in SQL Server](https://support.microsoft.com/help/4316791) <br/> Cumulative Update 8 for SQL Server 2017|
 | **AG** FIX: Unnecessary failover when you use Always On Availability Group| [KB4056922 - FIX: Unnecessary failover when you use Always On Availability Group in SQL Server 2017 on Linux](https://support.microsoft.com/help/4056922) <br/> Cumulative Update 3 for SQL Server 2017|