Full implementation of the new includes\paragraph-content\ .md file, in a total of 5 regular .md files.

MightyPen · MightyPen · commit dc8e02455d3f · 2018-04-04T19:13:20.000-07:00
diff --git a/docs/connect/jdbc/jdbc-driver-support-for-high-availability-disaster-recovery.md b/docs/connect/jdbc/jdbc-driver-support-for-high-availability-disaster-recovery.md
@@ -1,7 +1,7 @@
 ---
 title: "JDBC Driver Support for High Availability, Disaster Recovery | Microsoft Docs"
 ms.custom: ""
-ms.date: "01/19/2017"
+ms.date: "04/04/2018"
 ms.prod: "sql-non-specified"
 ms.prod_service: "drivers"
 ms.service: ""
@@ -89,29 +89,11 @@ If you are using Microsoft JDBC Driver 4.2 (or lower) for SQL Server and if **mu
  If you upgrade a [!INCLUDE[jdbcNoVersion](../../includes/jdbcnoversion_md.md)] application that currently uses database mirroring to a multi-subnet scenario, you should remove the **failoverPartner** connection property and replace it with **multiSubnetFailover** set to **true** and replace the server name in the connection string with a availability group listener. If a connection string uses **failoverPartner** and **multiSubnetFailover=true**, the driver will generate an error. However, if a connection string uses **failoverPartner** and **multiSubnetFailover=false** (or **ApplicationIntent=ReadWrite**), the application will use database mirroring.  
   
  The driver will return an error if database mirroring is used on the primary database in the AG, and if **multiSubnetFailover=true** is used in the connection string that connects to a primary database instead of to an availability group listener.  
-  
-## Specifying Application Intent  
- When **applicationIntent=ReadOnly**, the client requests a read-only workload when connecting to an AlwaysOn enabled database. The server will enforce the intent at connection time and during a USE database statement but only to an AlwaysOn enabled database.  
-  
- The **applicationIntent** keyword does not work with legacy, read-only databases.  
-  
- A database can allow or disallow read workloads on the targeted AlwaysOn database. (This is done with the **ALLOW_CONNECTIONS** clause of the **PRIMARY_ROLE** and **SECONDARY_ROLE**[!INCLUDE[tsql](../../includes/tsql_md.md)] statements.)  
-  
- The **applicationIntent** keyword is used to enable read-only routing.  
-  
-## Read-Only Routing  
- Read-only routing is a feature that can ensure the availability of a read-only replica of a database. To enable read-only routing:  
-  
-1.  You must connect to an AlwaysOn Availability Group availability group listener.  
-  
-2.  The **applicationIntent** connection string keyword must be set to **ReadOnly**.  
-  
-3.  The Availability Group must be configured by the database administrator to enable read-only routing.  
-  
- It is possible that multiple connections using read-only routing will not all connect to the same read-only replica. Changes in database synchronization or changes in the server's routing configuration can result in client connections to different read-only replicas. To ensure that all read-only requests connect to the same read-only replica, do not pass an availability group listener or virtual IP address to the **serverName** connection string keyword. Instead, specify the name of the read-only instance.  
-  
- Read-only routing may take longer than connecting to the primary because read-only routing first connects to the primary and then looks for the best available readable secondary. Because of this, you should increase your login timeout.  
-  
+
+
+[!INCLUDE[specify-application-intent_read-only-routing](~/includes/paragraph-content/specify-application-intent-read-only-routing.md)]
+
+
 ## New Methods Supporting multiSubnetFailover and applicationIntent  
  The following methods give you programmatic access to the **multiSubnetFailover**, **applicationIntent** and **transparentNetworkIPResolution** connection string keywords:  
   
diff --git a/docs/connect/odbc/linux-mac/odbc-driver-on-linux-support-for-high-availability-disaster-recovery.md b/docs/connect/odbc/linux-mac/odbc-driver-on-linux-support-for-high-availability-disaster-recovery.md
@@ -1,7 +1,7 @@
 ---
 title: "ODBC Driver on Linux and macOS - High Availability and Disaster Recovery | Microsoft Docs"
 ms.custom: ""
-ms.date: "01/19/2017"
+ms.date: "04/04/2018"
 ms.prod: "sql-non-specified"
 ms.prod_service: "drivers"
 ms.service: ""
@@ -70,29 +70,11 @@ If read-only routing is not in effect, connecting to a secondary replica locatio
 2.  If an application uses **ApplicationIntent=ReadWrite** and the secondary replica location is configured for read-only access.  
   
 A connection fails if a primary replica is configured to reject read-only workloads and the connection string contains **ApplicationIntent=ReadOnly**.  
-  
-## Specifying Application Intent  
-When **ApplicationIntent=ReadOnly**, the client requests a read workload when connecting to an AlwaysOn enabled database. The server enforces the intent at connection time and during a USE database statement but only to an AlwaysOn enabled database.
 
-The **ApplicationIntent** keyword does not work with legacy, read-only databases.  
 
-A database can allow or disallow read workloads on the targeted AlwaysOn database. (Use the **ALLOW_CONNECTIONS** clause of the **PRIMARY_ROLE** and **SECONDARY_ROLE**[!INCLUDE[tsql](../../../includes/tsql_md.md)] statements.)  
-  
-The **ApplicationIntent** keyword is used to enable read-only routing.  
-  
-## Read-Only Routing  
-Read-only routing is a feature that can ensure the availability of a read-only replica of a database. To enable read-only routing:  
-  
-1.  Connect to an Always On Availability Group availability group listener.  
-  
-2.  The **ApplicationIntent** connection string keyword must be set to **ReadOnly**.  
-  
-3.  The database administrator must configure the Availability Group to enable read-only routing.  
-  
-It is possible for multiple connections that use read-only routing to connect to different read-only replicas. Changes in database synchronization or changes in the server's routing configuration can result in client connections to different read-only replicas. To ensure that all read-only requests connect to the same read-only replica, do not pass an availability group listener to the **Server** connection keyword. Instead, specify the name of the read-only instance.  
-  
-Expect longer connection times with read-only routing than connecting to the primary. Therefore, increase your login timeout. Read-only routing first connects to the primary and then looks for the best available readable secondary.  
-  
+[!INCLUDE[specify-application-intent_read-only-routing](~/includes/paragraph-content/specify-application-intent-read-only-routing.md)]
+
+
 ## ODBC Syntax
 
 Two ODBC connection string keywords support [!INCLUDE[ssHADR](../../../includes/sshadr_md.md)]:  
diff --git a/docs/connect/oledb/features/oledb-driver-for-sql-server-support-for-high-availability-disaster-recovery.md b/docs/connect/oledb/features/oledb-driver-for-sql-server-support-for-high-availability-disaster-recovery.md
@@ -2,7 +2,7 @@
 title: "OLE DB Driver for SQL Server Support for High Availability, Disaster Recovery | Microsoft Docs"
 description: "OLE DB Driver for SQL Server support for high availability, disaster recovery"
 ms.custom: ""
-ms.date: "03/26/2018"
+ms.date: "04/04/2018"
 ms.prod: "sql-non-specified"
 ms.prod_service: "database-engine, sql-database, sql-data-warehouse, pdw"
 ms.service: ""
@@ -67,29 +67,11 @@ A connection error will occur if the **MultiSubnetFailover** and **Failover_Part
 If you upgrade an OLE DB Driver for SQL Server application that currently uses database mirroring to a multi-subnet scenario, you should remove the **Failover_Partner** connection property and replace it with **MultiSubnetFailover** set to **Yes** and replace the server name in the connection string with an availability group listener. If a connection string uses **Failover_Partner** and **MultiSubnetFailover=Yes**, the driver will generate an error. However, if a connection string uses **Failover_Partner** and **MultiSubnetFailover=No** (or **ApplicationIntent=ReadWrite**), the application will use database mirroring.  
   
 The driver will return an error if database mirroring is used on the primary database in the availability group, and if **MultiSubnetFailover=Yes** is used in the connection string that connects to a primary database instead of to an availability group listener.  
-  
-## Specifying Application Intent  
-When **ApplicationIntent=ReadOnly**, the client requests a read workload when connecting to an Always On enabled database. The server will enforce the intent at connection time and during a `USE` database statement but only to an Always On enabled database.  
-  
-The **ApplicationIntent** keyword does not work with legacy, read-only databases.  
-  
-A database can allow or disallow read workloads on the targeted Always On database. (This is done with the **ALLOW_CONNECTIONS** clause of the **PRIMARY_ROLE** and **SECONDARY_ROLE**[!INCLUDE[tsql](../../../includes/tsql-md.md)] statements.)  
-  
-The **ApplicationIntent** keyword is used to enable read-only routing.  
-  
-## Read-Only Routing  
-Read-only routing is a feature that can ensure the availability of a read only replica of a database. To enable read-only routing:  
-  
-1.  You must connect to an Always On Availability Group availability group listener.  
-  
-2.  The **ApplicationIntent** connection string keyword must be set to **ReadOnly**.  
-  
-3.  The Always On Availability Group must be configured by the database administrator to enable read-only routing.  
-  
-It is possible that multiple connections using read-only routing will not all connect to the same read-only replica. Changes in database synchronization or changes in the server's routing configuration can result in client connections to different read-only replicas. To ensure that all read-only requests connect to the same read-only replica, do not pass an Always On Availability Group listener to the **Server** connection string keyword. Instead, specify the name of the read-only instance.  
-  
-Read-only routing may take longer than connecting to the primary because read only routing first connects to the primary and then looks for the best available readable secondary. Because of this, you should increase your login timeout.  
-  
+
+
+[!INCLUDE[specify-application-intent_read-only-routing](~/includes/paragraph-content/specify-application-intent-read-only-routing.md)]
+
+
 ## OLE DB  
 The OLE DB Driver for SQL Server supports both the **ApplicationIntent** and the **MultiSubnetFailover** keywords.   
   
diff --git a/docs/connect/php/php-driver-for-sql-server-support-for-high-availability-disaster-recovery.md b/docs/connect/php/php-driver-for-sql-server-support-for-high-availability-disaster-recovery.md
@@ -1,7 +1,7 @@
 ---
 title: "Support for High Availability, Disaster Recovery for the Microsoft Drivers for PHP for SQL Server | Microsoft Docs"
 ms.custom: ""
-ms.date: "03/26/2018"
+ms.date: "04/04/2018"
 ms.prod: "sql-non-specified"
 ms.prod_service: "drivers"
 ms.service: ""
@@ -68,29 +68,11 @@ A connection error will occur if the **MultiSubnetFailover** and **Failover_Part
 If you upgrade a [!INCLUDE[ssDriverPHP](../../includes/ssdriverphp_md.md)] application that currently uses database mirroring to a multi-subnet scenario, you should remove the **Failover_Partner** connection property and replace it with **MultiSubnetFailover** set to **Yes** and replace the server name in the connection string with an availability group listener. If a connection string uses **Failover_Partner** and **MultiSubnetFailover=true**, the driver will generate an error. However, if a connection string uses **Failover_Partner** and **MultiSubnetFailover=false** (or **ApplicationIntent=ReadWrite**), the application will use database mirroring.  
   
 The driver will return an error if database mirroring is used on the primary database in the AG, and if **MultiSubnetFailover=true** is used in the connection string that connects to a primary database instead of to an availability group listener.  
-  
-## Specifying Application Intent  
-When **ApplicationIntent=ReadOnly**, the client requests a read workload when connecting to an AlwaysOn enabled database. The server will enforce the intent at connection time and during a USE database statement but only to an Always On enabled database.  
-  
-The **ApplicationIntent** keyword does not work with legacy, read-only databases.  
-  
-A database can allow or disallow read workloads on the targeted AlwaysOn database. (This is done with the **ALLOW_CONNECTIONS** clause of the **PRIMARY_ROLE** and **SECONDARY_ROLE**[!INCLUDE[tsql](../../includes/tsql_md.md)] statements.)  
-  
-The **ApplicationIntent** keyword is used to enable read-only routing.  
-  
-## Read-Only Routing  
-Read-only routing is a feature that can ensure the availability of a read-only replica of a database. To enable read-only routing:  
-  
-1.  You must connect to an Always On Availability Group availability group listener.  
-  
-2.  The **ApplicationIntent** connection string keyword must be set to **ReadOnly**.  
-  
-3.  The Availability Group must be configured by the database administrator to enable read-only routing.  
-  
-It is possible that multiple connections using read-only routing will not all connect to the same read-only replica. Changes in database synchronization or changes in the server's routing configuration can result in client connections to different read-only replicas. To ensure that all read-only requests connect to the same read-only replica, do not pass an availability group listener to the **Server** connection string keyword. Instead, specify the name of the read-only instance.  
-  
-Read-only routing may take longer than connecting to the primary because read-only routing first connects to the primary and then looks for the best available readable secondary. In this case, the login timeout should be increased.  
-  
+
+
+[!INCLUDE[specify-application-intent_read-only-routing](~/includes/paragraph-content/specify-application-intent-read-only-routing.md)]
+
+
 ## See Also  
 [Connecting to the Server](../../connect/php/connecting-to-the-server.md)  
   
diff --git a/docs/includes/paragraph-content/specify-application-intent-read-only-routing.md b/docs/includes/paragraph-content/specify-application-intent-read-only-routing.md
@@ -13,7 +13,7 @@ The **ApplicationIntent** keyword does not work with legacy read-only databases.
 When a connection chooses **ReadOnly**, the connection is assigned to any of the following special configurations that might exist for the database:
 
 - [Always On](~/database-engine/availability-groups/windows/overview-of-always-on-availability-groups-sql-server.md)
-    - A database can allow or disallow read workloads on the targeted Always On database. This is done with the **ALLOW_CONNECTIONS** clause of the **PRIMARY_ROLE** and **SECONDARY_ROLE** Transact-SQL statements.
+    - A database can allow or disallow read workloads on the targeted Always On database. This choice is controlled by using the **ALLOW_CONNECTIONS** clause of the **PRIMARY_ROLE** and **SECONDARY_ROLE** Transact-SQL statements.
 
 - [Geo-Replication](https://docs.microsoft.com/azure/sql-database/sql-database-geo-replication-overview)
 
@@ -28,15 +28,15 @@ The **ApplicationIntent** keyword enables *read-only routing*.
 
 ## Read-Only Routing
 
-Read-only routing is a feature that can ensure the availability of a read only replica of a database. To enable read-only routing:
-  
+Read-only routing is a feature that can ensure the availability of a read-only replica of a database. To enable read-only routing:
+
 1. You must connect to an Always On Availability Group availability group listener.
-  
+
 2. The **ApplicationIntent** connection string keyword must be set to **ReadOnly**.
-  
+
 3. The Availability Group must be configured by the database administrator to enable read-only routing.
-  
-It is possible that multiple connections using read-only routing will not all connect to the same read-only replica. Changes in database synchronization or changes in the server's routing configuration can result in client connections to different read-only replicas. To ensure that all read-only requests connect to the same read-only replica, do not pass an availability group listener to the **Server** connection string keyword. Instead, specify the name of the read-only instance.
 
-Read-only routing may take longer than connecting to the primary because read only routing first connects to the primary and then looks for the best available readable secondary. Because of this, you should increase your login timeout.
-  
+Multiple connections each using read-only routing might not all connect to the same read-only replica. Changes in database synchronization or changes in the server's routing configuration can result in client connections to different read-only replicas. You can ensure that all read-only requests connect to the same read-only replica. Ensure this sameness by *not* passing an availability group listener to the **Server** connection string keyword. Instead, specify the name of the read-only instance.
+
+Read-only routing may take longer than connecting to the primary. The longer wait is because read-only routing first connects to the primary, and then looks for the best available readable secondary. Due to these multiple staps, you should increase your login timeout to to at least 30 seconds.
+
