Merge pull request #14881 from David-Engel/fix-links

garycentric · web-flow · commit f7b77db39a2f · 2020-05-06T20:27:26.000-07:00
Fixing links, adding descriptions
diff --git a/docs/connect/jdbc/accessing-diagnostic-information-in-the-extended-events-log.md b/docs/connect/jdbc/accessing-diagnostic-information-in-the-extended-events-log.md
@@ -1,7 +1,8 @@
 ---
-title: "Accessing diagnostic information in the extended events log | Microsoft Docs"
+title: "Accessing diagnostic information in the extended events log"
+description: "Learn how to access extended events on the server that are related to events from the Microsoft JDBC Driver for SQL Server."
 ms.custom: ""
-ms.date: "08/12/2019"
+ms.date: "05/06/2020"
 ms.prod: sql
 ms.prod_service: connectivity
 ms.reviewer: ""
@@ -14,10 +15,10 @@ ms.author: v-daenge
 # Accessing diagnostic information in the extended events log
 [!INCLUDE[Driver_JDBC_Download](../../includes/driver_jdbc_download.md)]
 
-  In the [!INCLUDE[jdbc_40](../../includes/jdbc_40_md.md)], tracing ([Tracing driver operation](../../connect/jdbc/tracing-driver-operation.md)) has been updated to make it easier to correlate client events with diagnostic information, such as connection failures, from the server's connectivity ring buffer and application performance information in the extended events log. For information about reading the extended events log, see [View Event Session Data](https://msdn.microsoft.com/library/hh710068(SQL.110).aspx).  
+  In the [!INCLUDE[jdbc_40](../../includes/jdbc_40_md.md)], tracing ([Tracing driver operation](../../connect/jdbc/tracing-driver-operation.md)) has been updated to make it easier to correlate client events with diagnostic information, such as connection failures, from the server's connectivity ring buffer and application performance information in the extended events log. For information about reading the extended events log, see [Extended Events](../../relational-databases/extended-events/extended-events.md).  
   
 ## Details  
- For connection operations, the [!INCLUDE[jdbcNoVersion](../../includes/jdbcnoversion_md.md)] will send a client connection ID. If the connection fails, you can access the connectivity ring buffer ([Connectivity troubleshooting in SQL Server 2008 with the Connectivity Ring Buffer](https://go.microsoft.com/fwlink/?LinkId=207752)) and find the **ClientConnectionID** field and get diagnostic information about the connection failure. Client connection IDs are logged in the ring buffer only if an error occurs. (If a connection fails before sending the prelogin packet, a client connection ID won't be generated.) The client connection ID is a 16-byte GUID. You can also find the client connection ID in the extended events target output, if the **client_connection_id** action is added to events in an extended events session. If you need further client driver diagnostic assistance, you can enable tracing and rerun the connection command to observe the **ClientConnectionID** field in the trace.  
+ For connection operations, the [!INCLUDE[jdbcNoVersion](../../includes/jdbcnoversion_md.md)] will send a client connection ID. If the connection fails, you can access the connectivity ring buffer ([Connectivity troubleshooting in SQL Server 2008 with the Connectivity Ring Buffer](/archive/blogs/sql_protocols/connectivity-troubleshooting-in-sql-server-2008-with-the-connectivity-ring-buffer)) and find the **ClientConnectionID** field and get diagnostic information about the connection failure. Client connection IDs are logged in the ring buffer only if an error occurs. (If a connection fails before sending the prelogin packet, a client connection ID won't be generated.) The client connection ID is a 16-byte GUID. You can also find the client connection ID in the extended events target output, if the **client_connection_id** action is added to events in an extended events session. If you need further client driver diagnostic assistance, you can enable tracing and rerun the connection command to observe the **ClientConnectionID** field in the trace.  
   
  You can get the client connection ID programmatically by using [ISQLServerConnection Interface](../../connect/jdbc/reference/isqlserverconnection-interface.md). The connection ID will also be present in any connection-related exceptions.  
   
@@ -45,7 +46,6 @@ add event rpc_completed (action (client_connection_id))
 add target ring_buffer with (track_causality=on)  
 ```  
   
-## See also  
- [Diagnosing problems with the JDBC driver](../../connect/jdbc/diagnosing-problems-with-the-jdbc-driver.md)  
-  
-  
+## See also
+
+[Diagnosing problems with the JDBC driver](../../connect/jdbc/diagnosing-problems-with-the-jdbc-driver.md)  
diff --git a/docs/connect/odbc/using-transparent-network-ip-resolution.md b/docs/connect/odbc/using-transparent-network-ip-resolution.md
@@ -1,7 +1,8 @@
 ---
-title: "Using Transparent Network IP Resolution | Microsoft Docs"
+title: "Using Transparent Network IP Resolution"
+description: "Learn about Transparent Network IP Resolution in the ODBC Driver for SQL Server and how it affects the MultiSubnetFailover feature."
 ms.custom: ""
-ms.date: "01/19/2017"
+ms.date: "05/06/2020"
 ms.prod: sql
 ms.prod_service: connectivity
 ms.reviewer: ""
@@ -20,7 +21,7 @@ TransparentNetworkIPResolution is a revision of the existing MultiSubnetFailover
 * 1: All IPs are attempted in parallel
 * 2: All IPs are attempted one after another
 
-|TransparentNetworkIPResolution|MultiSubnetFailover|Behaviour|
+|TransparentNetworkIPResolution|MultiSubnetFailover|Behavior|
 |:-:|:-:|:-:|
 |(default)|(default)|0|
 |(default)|Enabled|1|
@@ -44,8 +45,8 @@ Connection Attribute|	Size/Type|	Default| Value|	Description
 -|-|-|-|-
 `SQL_COPT_SS_TNIR` (1249)| `SQL_IS_INTEGER` or `SQL_IS_UINTEGER`| `SQL_IS_ON`(1), `SQL_IS_OFF`(0)|`SQL_IS_ON`|Enables or disables TNIR.
 
-For more information about MultiSubnetFailover, see [ODBC Driver on Linux and macOS - High Availability and Disaster Recovery](../../connect/odbc/linux-mac/odbc-driver-on-linux-support-for-high-availability-disaster-recovery.md)
+For more information about MultiSubnetFailover, see [ODBC Driver on Linux and macOS - High Availability and Disaster Recovery](linux-mac/odbc-driver-on-linux-support-for-high-availability-disaster-recovery.md)
 --------------------------------------------------
 ## See Also  
-* [Microsoft ODBC Driver for SQL Server on Windows](../../connect/odbc/windows/microsoft-odbc-driver-for-sql-server-on-windows.md)
-* [SQL Server Multi-Subnet Clustering (SQL Server)](https://msdn.microsoft.com/library/ff878716.aspx#RelatedContent)
+* [Microsoft ODBC Driver for SQL Server on Windows](windows/microsoft-odbc-driver-for-sql-server-on-windows.md)
+* [SQL Server Multi-Subnet Clustering (SQL Server)](../../sql-server/failover-clusters/windows/sql-server-multi-subnet-clustering-sql-server.md)
diff --git a/docs/connect/odbc/windows/features-of-the-microsoft-odbc-driver-for-sql-server-on-windows.md b/docs/connect/odbc/windows/features-of-the-microsoft-odbc-driver-for-sql-server-on-windows.md
@@ -1,7 +1,8 @@
 ---
-title: "Features of the Microsoft ODBC Driver for SQL Server on Windows | Microsoft Docs"
+title: "Features of the Microsoft ODBC Driver"
+description: "Learn about the different features supported by the Microsoft ODBC Driver for SQL Server on Windows."
 ms.custom: ""
-ms.date: "01/19/2017"
+ms.date: "05/06/2020"
 ms.prod: sql
 ms.prod_service: connectivity
 ms.reviewer: ""
@@ -35,11 +36,11 @@ The ODBC Driver 13.1 for SQL Server contains all the functionality of the previo
   
 Always Encrypted allows clients to encrypt sensitive data inside client applications and never reveal the encryption keys to SQL Server. An Always Encrypted enabled driver installed on the client computer achieves this by automatically encrypting and decrypting sensitive data in the SQL Server client application. The driver encrypts the data in sensitive columns before passing the data to SQL Server, and automatically rewrites queries so that the semantics to the application are preserved. Similarly, the driver transparently decrypts data stored in encrypted database columns that are contained in query results. For more information, see [Using Always Encrypted with the ODBC Driver](../../../connect/odbc/using-always-encrypted-with-the-odbc-driver.md).
  
-Azure Active Directory allows users, DBA's, and application programmers to use Azure Active Directory authentication as a mechanism of connecting to Microsoft Azure SQL Database and Microsoft SQL Server 2016 by using identities in Azure Active Directory (Azure AD). For more information, see [Using Azure Active Directory with the ODBC Driver](../../../connect/odbc/using-azure-active-directory.md), and [Connecting to SQL Database or SQL Data Warehouse By Using Azure Active Directory Authentication](https://azure.microsoft.com/documentation/articles/sql-database-aad-authentication/).   
+Azure Active Directory allows users, DBA's, and application programmers to use Azure Active Directory authentication as a mechanism of connecting to Microsoft Azure SQL Database and Microsoft SQL Server 2016 by using identities in Azure Active Directory (Azure AD). For more information, see [Using Azure Active Directory with the ODBC Driver](../using-azure-active-directory.md), and [Connecting to SQL Database or SQL Data Warehouse By Using Azure Active Directory Authentication](/azure/sql-database/sql-database-aad-authentication).   
   
 ## Microsoft ODBC Driver 11 for SQL Server on Windows  
 
-The ODBC Driver for [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] contains all the functionality of the [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] Native Client ODBC driver that shipped in [!INCLUDE[ssSQL11](../../../includes/sssql11-md.md)]. For more information, see [SQL Server Native Client Programming](../../../relational-databases/native-client/sql-server-native-client-programming.md). The [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] Native Client ODBC driver is based on the ODBC driver that ships in the Windows operating system. For more information, see [Windows Data Access Components SDK](https://msdn.microsoft.com/library/aa968814(VS.85).aspx).  
+The ODBC Driver for [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] contains all the functionality of the [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] Native Client ODBC driver that shipped in [!INCLUDE[ssSQL11](../../../includes/sssql11-md.md)]. For more information, see [SQL Server Native Client Programming](../../../relational-databases/native-client/sql-server-native-client-programming.md). The [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] Native Client ODBC driver is based on the ODBC driver that ships in the Windows operating system. For more information, see [Windows Data Access Components SDK](/previous-versions/windows/desktop/legacy/aa968814(v=vs.85)).  
   
 This release of the ODBC Driver for [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] contains the following new features:  
   
@@ -48,23 +49,23 @@ This release of the ODBC Driver for [!INCLUDE[ssNoVersion](../../../includes/ssn
 The -l option specifies the number of seconds before a `bcp.exe` login to [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] times out when you try to connect to a server. The default login timeout is 15 seconds. The login timeout must be a number between 0 and 65534. If the value supplied is not numeric or does not fall into that range, `bcp.exe` generates an error message. A value of 0 specifies an infinite timeout. A login timeout of less than (approximately) 10 seconds is not reliable.  
   
 ### Driver-Aware Connection Pooling  
-The ODBC Driver for [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] supports [Driver-Aware Connection Pooling](https://msdn.microsoft.com/library/hh405031(VS.85).aspx). For more information, see [Driver-Aware Connection Pooling in the ODBC Driver for SQL Server](../../../connect/odbc/windows/driver-aware-connection-pooling-in-the-odbc-driver-for-sql-server.md).  
+The ODBC Driver for [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] supports [Driver-Aware Connection Pooling](../../../odbc/reference/develop-app/driver-aware-connection-pooling.md). For more information, see [Driver-Aware Connection Pooling in the ODBC Driver for SQL Server](driver-aware-connection-pooling-in-the-odbc-driver-for-sql-server.md).  
   
 ### Asynchronous Execution (Notification Method)  
-The ODBC Driver for [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] supports [Asynchronous Execution (Notification Method)](https://msdn.microsoft.com/library/hh405038(VS.85).aspx). For a usage sample, see [Asynchronous Execution &#40;Notification Method&#41; Sample](../../../connect/odbc/windows/asynchronous-execution-notification-method-sample.md).  
+The ODBC Driver for [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] supports [Asynchronous Execution (Notification Method)](../../../odbc/reference/develop-app/asynchronous-execution-notification-method.md). For a usage sample, see [Asynchronous Execution &#40;Notification Method&#41; Sample](asynchronous-execution-notification-method-sample.md).  
   
 ### Connection Resiliency
-To ensure that applications remain connected to a Microsoft Azure SQL Database, the ODBC driver on Windows can restore idle connections. For more information, see [Connection Resiliency in the Windows ODBC Driver](../../../connect/odbc/windows/connection-resiliency-in-the-windows-odbc-driver.md).  
+To ensure that applications remain connected to a Microsoft Azure SQL Database, the ODBC driver on Windows can restore idle connections. For more information, see [Connection Resiliency in the Windows ODBC Driver](connection-resiliency-in-the-windows-odbc-driver.md).  
   
 ## Behavior Changes
 
 In [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] Native Client, the `-y0` option for `sqlcmd.exe` caused output to be truncated at 1 MB if the display width was 0.
   
-Beginning in the ODBC Driver 11 for [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)], there is no limit on the amount of data that can be retrieved in a single column when `-y0` is specified. `sqlcmd.exe` now streams columns as large as 2 GB ( [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] data type maximum).  
+Beginning in the ODBC Driver 11 for [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)], there is no limit on the amount of data that can be retrieved in a single column when `-y0` is specified. `sqlcmd.exe` now streams columns as large as 2 GB ([!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] data type maximum).  
   
 Another difference is that specifying both `-h` and `-y0` now produces an error reporting that the options are incompatible. `-h`, which specifies the number of rows to print between the column headings and has never been compatible with `-y0`, was ignored although no headers were printed.
   
 Note that `-y0` can cause performance issues on both the server and the network, depending on the size of the data returned.
 
 ## See Also  
-[Microsoft ODBC Driver for SQL Server on Windows](../../../connect/odbc/windows/microsoft-odbc-driver-for-sql-server-on-windows.md)  
+[Microsoft ODBC Driver for SQL Server on Windows](microsoft-odbc-driver-for-sql-server-on-windows.md)  
diff --git a/docs/connect/sql-data-developer.md b/docs/connect/sql-data-developer.md
@@ -2,7 +2,7 @@
 title: "SQL Data Developer | Microsoft Docs"
 description: "Use Microsoft's SQL data platform to create data-centric solutions across mobile devices and desktops for web servers, enterprise servers, and the cloud."
 ms.custom: ""
-ms.date: "03/28/2017"
+ms.date: "05/06/2020"
 ms.prod: sql
 ms.prod_service: "database-engine"
 ms.reviewer: ""
@@ -27,20 +27,17 @@ Use Microsoft's SQL data platform to create data-centric solutions across mobile
 
 ## SQL Data access
 * [SQL Client Drivers](sql-connection-libraries.md):  Use SQL drivers to connect, query, update, insert, or delete data from a SQL database.
-* [Entity Framework](https://msdn.microsoft.com/library/gg696172.aspx): Use the  Entity Framework to easily access databases using LINQ, with direct access to SQL Server and the option to control the mapping between an Entity Data Model (EDM) and raw relational structures. 
-* [Windows Communication Foundation (WCF)](https://msdn.microsoft.com/library/dd456779.aspx): Use  Data Services for a near-turnkey solution to easily create and consume OData services on both the web and intranet
-* [Sync Framework](https://msdn.microsoft.com/library/jj839436.aspx): Use the  Sync Framework to enable offline access to any data type, any data store, any transfer protocol, and any network topology.
-* [Reactive Extensions](https://msdn.microsoft.com/library/hh242985.aspx): Use the  Reactive Extensions (Rx) to perform event stream programming and simplify asynchronous programming using observable sequences and LINQ-style query operators.  Use the  Reactive Extensions for JavaScript (RxJS) to simplify asynchronous callback-based and event-driven programming on the web using observable sequences.
+* [Entity Framework](/ef/): Use the  Entity Framework to easily access databases using LINQ, with direct access to SQL Server and the option to control the mapping between an Entity Data Model (EDM) and raw relational structures. 
+* [Windows Communication Foundation (WCF)](/dotnet/framework/wcf/): Use  Data Services for a near-turnkey solution to easily create and consume OData services on both the web and intranet
+* [Sync Framework](/previous-versions/sql/synchronization/mt490616(v=msdn.10)): Use the  Sync Framework to enable offline access to any data type, any data store, any transfer protocol, and any network topology.
+* [Reactive Extensions](https://github.com/dotnet/reactive): Use the  Reactive Extensions (Rx) to perform event stream programming and simplify asynchronous programming using observable sequences and LINQ-style query operators.  Use the  Reactive Extensions for JavaScript (RxJS) to simplify asynchronous callback-based and event-driven programming on the web using observable sequences.
 * [CLR Integration](../relational-databases/clr-integration/common-language-runtime-clr-integration-programming-concepts.md):  Use CLR Integration to write stored procedures, triggers, user-defined types, user-defined functions, user-defined aggregates, and streaming table-valued functions, using any .NET Framework language, including Microsoft Visual Basic .NET and Microsoft Visual C#. 
 * [SQLXML 4.0](../relational-databases/sqlxml/sqlxml-4-0-programming-concepts.md): Use SQLXML 4.0 to export relational data to XML.
 
 ## Data collection, processing, and visualization
-* [Analysis Services](https://docs.microsoft.com/analysis-services/analysis-services-developer-documentation)
+* [Analysis Services](/analysis-services/analysis-services-developer-documentation)
 * [Integration Services](../integration-services/integration-services-developer-documentation.md)  
 * [Master Data Services](../master-data-services/develop/master-data-services-developer-documentation.md)
 * [Replication Services](../relational-databases/replication/concepts/replication-developer-documentation.md)
 * [Reporting Services](../reporting-services/reporting-services-developer-documentation.md)
 * [Service Broker](../database-engine/configure-windows/sql-server-service-broker.md)
-
-
- 
