reviewer suggestions corrected

Author: markingmyname

docs/database-engine/configure-windows/create-or-delete-a-server-alias-for-use-by-a-client.md

@@ -1,9 +1,8 @@
 ---
-title: "Create or Delete a Server Alias for Use by a Client | Microsoft Docs"
+title: Create or Delete a Server Alias for Use by a Client
 description: Find out how to create and delete an alias, an alternate name you can use when you connect to an instance of SQL Server. Learn about the benefits of aliases.
 ms.prod: sql
 ms.prod_service: high-availability
-ms.reviewer: ""
 ms.technology: configuration
 ms.topic: conceptual
 f1_keywords: 
@@ -13,37 +12,40 @@ helpviewer_keywords:
   - "aliases [SQL Server], creating"
 author: markingmyname
 ms.author: maghan
+ms.reviewer: ""
 ms.custom: ""
-ms.date: "03/14/2017"
+ms.date: "07/14/2021"
 ---
 
 # Create or Delete a Server Alias for Use by a Client
 
 [!INCLUDE [SQL Server](../../includes/applies-to-version/sqlserver.md)]
 
-This topic describes how to create or delete a server alias in [!INCLUDE[ssnoversion](../../includes/ssnoversion-md.md)] by using SQL Server Configuration Manager. An alias is an alternate name that can be used to make a connection. The alias encapsulates the required elements of a connection string, and exposes them with a name chosen by the user. Aliases can be used with any client application. By creating server aliases, your client computer can connect to multiple servers using different network protocols, without having to specify the protocol and connection details for each one. In addition, you can also have different network protocols enabled all the time, even if you only need to use them occasionally. If you have configured the server to listen on a non-default port number or named pipe, and you have disabled the SQL Server Browser service, create an alias that specifies the new port number or named pipe.  
-  
-## <a name="SSMSProcedure"></a> Using SQL Server Configuration Manager  
-  
-#### To create an alias  
-  
-1.  In [SQL Server Configuration Manager](../../relational-databases/sql-server-configuration-manager.md), expand **SQL Server Native Client Configuration**, right-click **Aliases**, and then click **New Alias**.  
-  
-2.  In the **Alias Name** box, type the name of the alias. Client applications use this name when they connect.  
-  
-3.  In the **Server** box, type the name or IP address of a server. For a named instance append the instance name.  
-  
-4.  In the **Protocol** box, select the protocol used for this alias. Selecting a protocol, changes the title of the optional properties box to Port No, Pipe Name, or Connection String.  
-  
-The connection strings described in [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Configuration Manager Help can be useful for programmers who create their own connection strings. To access this information, in the **New Alias** dialog box, press F1, or click **Help**.  
-  
-> [!NOTE]  
-> If a configured alias is connecting to the wrong server or instance, disable and then reenable the associated network protocol. Doing this clears any cached connection information and allows the client to connect correctly.  
-  
-#### To delete an alias  
-  
-1.  In [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Configuration Manager, expand **SQL Server Native Client Configuration**, and then click **Aliases**.  
-  
-2.  In the details pane, right-click the alias that you want to delete, and then click **Delete**.  
-  
-  
+This topic describes how to create or delete a server alias in SQL Server by using SQL Server Configuration Manager. An alias is an alternate name that can be used to make a connection. The alias encapsulates the required elements of a connection string, and exposes them with a name chosen by the user. Aliases can be used with any client application. By creating server aliases, your client computer can connect to multiple servers using different network protocols, without having to specify the protocol and connection details for each one. In addition, you can also have different network protocols enabled all the time, even if you only need to use them occasionally. If you have configured the server to listen on a non-default port number or named pipe, and you have disabled the SQL Server Browser service, create an alias that specifies the new port number or named pipe.
+
+## <a name="SSMSProcedure"></a> Using SQL Server Configuration Manager
+
+### To create an alias
+
+1. In [SQL Server Configuration Manager](../../relational-databases/sql-server-configuration-manager.md), expand **SQL Server Native Client Configuration**, right-click **Aliases**, and then select **New Alias**.
+
+2. In the **Alias Name** box, type the name of the alias. Client applications use this name when they connect.
+
+3. In the **Server** box, type the name or IP address of a server. For a named instance append the instance name.
+
+4. In the **Protocol** box, select the protocol used for this alias. Selecting a protocol, changes the title of the optional properties box to Port No, Pipe Name, or Connection String.  
+
+The connection strings described in SQL Server Configuration Manager Help can be useful for programmers who create their own connection strings. To access this information, in the **New Alias** dialog box, press F1, or select **Help**.
+
+> [!NOTE]
+> If a configured alias is connecting to the wrong server or instance, disable and then reenable the associated network protocol. Doing this clears any cached connection information and allows the client to connect correctly.
+
+### To delete an alias
+
+1. In SQL Server Configuration Manager, expand **SQL Server Native Client Configuration**, and then select **Aliases**.  
+
+2. In the details pane, right-click the alias that you want to delete, and then select **Delete**.
+
+## Next Steps
+
+- [SQL Server Config Manager](../../relational-databases/sql-server-configuration-manager.md)

docs/database-engine/configure-windows/optimize-for-ad-hoc-workloads-server-configuration-option.md

@@ -20,22 +20,22 @@ ms.date: "11/17/2017"
 
 The **optimize for ad hoc workloads** option is used to improve the efficiency of the plan cache for workloads that contain many single use ad hoc batches. When this option is set to 1, the 
 
-[!INCLUDE[ssDE](../../includes/ssde-md.md)] stores a small compiled plan stub in the plan cache when a batch is compiled for the first time, instead of the full compiled plan. This helps to relieve memory pressure by not allowing the plan cache to become filled with compiled plans that are not reused. 
+[!INCLUDE[ssDE](../../includes/ssde-md.md)] stores a small compiled plan stub in the plan cache when a batch is compiled for the first time, instead of the full compiled plan. This helps to relieve memory pressure by not allowing the plan cache to become filled with compiled plans that aren't reused. 
 
 The compiled plan stub allows the [!INCLUDE[ssDE](../../includes/ssde-md.md)] to recognize that this ad hoc batch has been compiled before but has only stored a compiled plan stub, so when this batch is invoked (compiled or executed) again, the [!INCLUDE[ssDE](../../includes/ssde-md.md)] compiles the batch, removes the compiled plan stub from the plan cache, and adds the full compiled plan to the plan cache. 
 
-The compiled plan stub is one of the cacheobjtypes displayed by the sys.dm_exec_cached_plans catalog view. It has a unique sql handle and plan handle. The compiled plan stub does not have an execution plan associated with it and querying for the plan handle will not return an XML Showplan.  
+The compiled plan stub is one of the cacheobjtypes displayed by the sys.dm_exec_cached_plans catalog view. It has a unique sql handle and plan handle. The compiled plan stub doesn't have an execution plan associated with it and querying for the plan handle doesn't return an XML Showplan.
 
-[Trace flag 8032](../../t-sql/database-console-commands/dbcc-traceon-trace-flags-transact-sql.md) reverts the cache limit parameters to the [!INCLUDE[ssVersion2005](../../includes/ssversion2005-md.md)] RTM setting which in general allows caches to be larger. Use this setting when frequently reused cache entries do not fit into the cache and when the optimize for ad hoc workloads Server Configuration Option has failed to resolve the problem with plan cache.  
- 
-> [!WARNING]  
+[Trace flag 8032](../../t-sql/database-console-commands/dbcc-traceon-trace-flags-transact-sql.md) reverts the cache limit parameters to the [!INCLUDE[ssVersion2005](../../includes/ssversion2005-md.md)] RTM setting, which in general allows caches to be larger. Use this setting when frequently reused cache entries do not fit into the cache and when the `optimize for ad hoc workloads Server Configuration Option` has failed to resolve the problem with plan cache.  
+
+> [!WARNING]
 > Trace flag 8032 can cause poor performance if large caches make less memory available for other memory consumers, such as the buffer pool.  
 
 ## Recommendations
 
-Avoid having a large number of single-use plans in the plan cache. A common cause of this problem is when the data types of query parameters is not consistently defined. This particularly applies to the length of strings but can apply to any data type that has a maxlength, a precision, or a scale. For example, if a parameter named @Greeting is passed as an nvarchar(10) on one call and an nvarchar(20) on the next call, separate plans are created for each parameter size. If a query has several parameters and they are not consistently defined when called, a large number of query plans could exist for each query. Plans could exist for each combination of query parameter data types and lengths that have been used.
+Avoid having a large number of single-use plans in the plan cache. A common cause of this problem is when the data types of query parameters aren't consistently defined. This particularly applies to the length of strings but can apply to any data type that has a maxlength, a precision, or a scale. For example, if a parameter named @Greeting is passed as a nvarchar(10) on one call and a nvarchar(20) on the next call, separate plans are created for each parameter size. If a query has several parameters and they aren't consistently defined when called, a large number of query plans could exist for each query. Plans could exist for each combination of query parameter data types and lengths that have been used.
 
-If the number of single-use plans take a significant portion of [!INCLUDE[ssDEnoversion](../../includes/ssdenoversion-md.md)] memory in an OLTP server, and these plans are Ad-hoc plans, use this server option to decrease memory usage with these objects.
+If the number of single-use plans take a significant portion of [!INCLUDE[ssDEnoversion](../../includes/ssdenoversion-md.md)] memory in an OLTP server, and these plans are Ad hoc plans, use this server option to decrease memory usage with these objects.
 To find the number of single-use cached plans, run the following query:
 
 ```sql