Documentation/release notes updates

Author: cheenamalhotra

doc/snippets/Microsoft.Data.SqlClient/SqlConnectionStringBuilder.xml

@@ -210,10 +210,30 @@ Modified: Data Source=(local);Initial Catalog=AdventureWorks;Integrated Security
         <ConnectRetryCount>
             <summary>The number of reconnections attempted after identifying that there was an idle connection failure. This must be an integer between 0 and 255. Default is 1. Set to 0 to disable reconnecting on idle connection failures. An <see cref="T:System.ArgumentException" /> will be thrown if set to a value outside of the allowed range.</summary>
             <value>The number of reconnections attempted after identifying that there was an idle connection failure.</value>
+            <remarks>
+              <format type="text/markdown">
+                <![CDATA[  
+  
+  ## Remarks  
+   This property corresponds to the "Connect Retry Count" key within the <xref:Microsoft.Data.SqlClient.SqlConnection> connection string.
+  
+   ]]>
+              </format>
+            </remarks>
         </ConnectRetryCount>
         <ConnectRetryInterval>
             <summary>Amount of time (in seconds) between each reconnection attempt after identifying that there was an idle connection failure. This must be an integer between 1 and 60. The default is 10 seconds. An <see cref="T:System.ArgumentException" /> will be thrown if set to a value outside of the allowed range.</summary>
             <value>Amount of time (in seconds) between each reconnection attempt after identifying that there was an idle connection failure.</value>
+            <remarks>
+              <format type="text/markdown">
+                <![CDATA[  
+  
+    ## Remarks  
+     This property corresponds to the "Connect Retry Interval" key within the <xref:Microsoft.Data.SqlClient.SqlConnection> connection string.
+  
+     ]]>
+              </format>
+            </remarks>
         </ConnectRetryInterval>
         <ConnectTimeout>
             <summary>Gets or sets the length of time (in seconds) to wait for a connection to the server before terminating the attempt and generating an error.</summary>
@@ -500,7 +520,7 @@ False
             <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This property corresponds to the "MultipleActiveResultSets" key within the connection string.  
+ This property corresponds to the "Multiple Active Result Sets" key within the connection string.  
   
    
   
@@ -582,10 +602,13 @@ False
             <summary>The blocking period behavior for a connection pool.</summary>
             <value>The available blocking period settings.</value>
             <remarks>
-            <format type="text/markdown"><![CDATA[  
+            <format type="text/markdown">
+              <![CDATA[  
   
 ## Remarks  
- When connection pooling is enabled and  a timeout error or other login error occurs, an exception will be thrown and subsequent connection attempts will fail for the next five seconds, the "blocking period". If the application attempts to connect within the blocking period, the first exception will be thrown again. Subsequent failures after a blocking period ends will result in a new blocking period that is twice as long as the previous blocking period, up to a maximum of one minute.  
+ This property corresponds to the "Pool Blocking Period" key within the connection string.
+ 
+ When connection pooling is enabled and a timeout error or other login error occurs, an exception will be thrown and subsequent connection attempts will fail for the next five seconds, the "blocking period". If the application attempts to connect within the blocking period, the first exception will be thrown again. Subsequent failures after a blocking period ends will result in a new blocking period that is twice as long as the previous blocking period, up to a maximum of one minute.  
   
  Attempting to connect to Azure SQL databases can fail with transient errors which are typically recovered within a few seconds. However, with the connection pool blocking period behavior, you may not be able to reach your database for extensive periods even though the database is  available. This is especially problematic for apps that need to render fast. The **PoolBlockingPeriod** enables you to select the blocking period best suited for your app. See the <xref:Microsoft.Data.SqlClient.PoolBlockingPeriod> enumeration for available settings.  
   
@@ -721,9 +744,9 @@ Database = AdventureWorks
             <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- If the `MultiSubnetFailover` key is set to `true`, `TransparentNetworkIPResolution` is ignored.  
+ If the `Multi Subnet Failover` key is set to `true`, `Transparent Network IP Resolution` is ignored.  
   
- If the `Failover Partner` key is set, `TransparentNetworkIPResolution` is ignored.  
+ If the `Failover Partner` key is set, `Transparent Network IP Resolution` is ignored.  
   
  The value of this key must be `true`, `false`, `yes`, or `no`.  
   
@@ -757,7 +780,7 @@ Database = AdventureWorks
             <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- When `TrustServerCertificate` is set to `true`, the transport layer will use SSL to encrypt the channel and bypass walking the certificate chain to validate trust. If `TrustServerCertificate` is set to `true` and encryption is turned on, the encryption level specified on the server will be used even if `Encrypt` is set to `false`. The connection will fail otherwise.  
+ When `Trust Server Certificate` is set to `true`, the transport layer will use SSL to encrypt the channel and bypass walking the certificate chain to validate trust. If `Trust Server Certificate` is set to `true` and encryption is enforced by target server, the encryption level specified on the server will be used even if `Encrypt` is set to `false`. The connection will fail otherwise.
   
  For more information, see [Encryption Hierarchy](/sql/relational-databases/security/encryption/encryption-hierarchy) and [Using Encryption Without Validation](/sql/relational-databases/native-client/features/using-encryption-without-validation).
   
@@ -774,9 +797,7 @@ Database = AdventureWorks
             <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:Microsoft.Data.SqlClient.SqlConnectionStringBuilder.TryGetValue%2A> method lets developers safely retrieve a value from a <xref:Microsoft.Data.SqlClient.SqlConnectionStringBuilder> without needing to verify that the supplied key name is a valid key name. Because **TryGetValue** does not raise an exception when you call it, passing in a nonexistent key, you do not have to look for a key before retrieving its value.  Calling **TryGetValue** with a nonexistent key will place the value null (`Nothing` in Visual Basic) in the `value` parameter.  
-  
-   
+ The <xref:Microsoft.Data.SqlClient.SqlConnectionStringBuilder.TryGetValue%2A> method lets developers safely retrieve a value from a <xref:Microsoft.Data.SqlClient.SqlConnectionStringBuilder> without needing to verify that the supplied key name is a valid key name. Because **TryGetValue** does not raise an exception when you call it, passing in a nonexistent key, you do not have to look for a key before retrieving its value.  Calling **TryGetValue** with a nonexistent key will place the value null (`Nothing` in Visual Basic) in the `value` parameter.
   
 ## Examples  
  The following example demonstrates the behavior of the **TryGetValue** method.  

release-notes/2.0/2.0.0-preview4.md

@@ -20,7 +20,7 @@ This update brings the below changes over the previous release:
 
 ### Breaking Changes
 - For .NET Framework applications consuming **Microsoft.Data.SqlClient**, the `SNI.dll` files previously downloaded to the `bin\x64` and `bin\x86` folders are now named `Microsoft.Data.SqlClient.SNI.x64.dll` and `Microsoft.Data.SqlClient.SNI.x86.dll` and will be downloaded to the `bin` directory, to support auto-loading in the application process [#570](https://github.com/dotnet/SqlClient/pull/570). This change is not going to impact client applications unless a direct reference has been made to `SNI.dll` or the x86 and x64 folders.
-
+- New connection string property synonyms will replace old properties when fetching connection string from `SqlConnectionStringBuilder` for consistency. [Read More](#new-connection-string-property-synonyms)
 
 ## New Connection string property synonyms
 
@@ -37,7 +37,7 @@ The below connection properties can be interchangeably used with the new synonym
 | TransparentNetworkIPResolution | Transparent Network IP Resolution |
 | TrustServerCertificate | Trust Server Certificate |
 
-> Note: This is not a breaking change. Old properties will continue to be supported for backwards compatibility.
+> Old properties will continue to be supported for backwards compatibility, but the new connection string properties will now be included when fetching connection string from [SqlConnectionStringBuilder](https://docs.microsoft.com/dotnet/api/microsoft.data.sqlclient.sqlconnectionstringbuilder).
 
 ## Target Platform Support
 

release-notes/2.0/2.0.0.md

@@ -102,6 +102,7 @@ All changes in Microsoft.Data.SqlClient v2.0 over v1.1:
 - For .NET Framework applications consuming **Microsoft.Data.SqlClient**, the `SNI.dll` files previously downloaded to the `bin\x64` and `bin\x86` folders are now named `Microsoft.Data.SqlClient.SNI.x64.dll` and `Microsoft.Data.SqlClient.SNI.x86.dll` and will be downloaded to the `bin` directory, to support auto-loading in the application process [#570](https://github.com/dotnet/SqlClient/pull/570). _This change is not going to impact client applications unless a direct reference has been made to `SNI.dll` or the x86 and x64 folders._
 - Modified enclave provider interface `SqlColumnEncryptionEnclaveProvider` to be internal along with related classes `SqlEnclaveAttestationParameters` and `SqlEnclaveSession` [#602](https://github.com/dotnet/SqlClient/pull/602) - _This change is not likely to impact customer applications since secure enclaves is a relatively new feature and they would have had to implement their own enclave provider, which is not a trivial task_.
 - Updated `SqlClientMetaDataCollectionNames` exposed constants by removing non-existing constants and adding new to the metadata collection [#580](https://github.com/dotnet/SqlClient/pull/580)
+- New connection string property synonyms will replace old properties when fetching connection string from `SqlConnectionStringBuilder` for consistency. [Read More](#new-connection-string-property-synonyms)
 
 
 ### Additional Active Directory authentication modes
@@ -182,7 +183,7 @@ The below connection properties can be interchangeably used with the new synonym
 | TransparentNetworkIPResolution | Transparent Network IP Resolution |
 | TrustServerCertificate | Trust Server Certificate |
 
-> [Note] This is not a breaking change. Old properties will continue to be supported for backwards compatibility.
+> Old properties will continue to be supported for backwards compatibility, but the new connection string properties will now be included when fetching connection string from [SqlConnectionStringBuilder](https://docs.microsoft.com/dotnet/api/microsoft.data.sqlclient.sqlconnectionstringbuilder).
 
 
 #### SqlBulkCopy.RowsCopied property