Merge pull request #17349 from DCtheGeek/dmc-links-relationaldatabases-7

Links: SQL - relational-databases - 7

Author: v-shmck

docs/relational-databases/native-client/applications/installing-sql-server-native-client.md

@@ -46,7 +46,7 @@ You can also get sqlncli.msi from the SQL Server 2012 Feature Pack web page. To
 
  In addition to installing [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] Native Client as part of the [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] installation, there is also a redistributable installation program named sqlncli.msi, which can be found on the [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] installation disk in the following location: `%CD%\Setup\`.  
 
- You can distribute [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] Native Client through sqlncli.msi. You might have to install [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] Native Client when you deploy an application. One way to install multiple packages in what seems to the user to be a single installation is to use chainer and bootstrapper technology. For more information, see [Authoring a Custom Bootstrapper Package for Visual Studio 2005](https://go.microsoft.com/fwlink/?LinkId=115667) and [Adding Custom Prerequisites](https://go.microsoft.com/fwlink/?LinkId=115668).  
+ You can distribute [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] Native Client through sqlncli.msi. You might have to install [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] Native Client when you deploy an application. One way to install multiple packages in what seems to the user to be a single installation is to use chainer and bootstrapper technology. For more information, see [Authoring a Custom Bootstrapper Package for Visual Studio 2005](/previous-versions/aa730839(v=vs.80)) and [Adding Custom Prerequisites](/visualstudio/deployment/creating-bootstrapper-packages).  
 
  The x64 and Itanium versions of sqlncli.msi also install the 32-bit version of [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] Native Client. If your application targets a platform other than the one it was developed on, you can download versions of sqlncli.msi for x64, Itanium, and x86 from the Microsoft Download Center.  
 
@@ -66,6 +66,5 @@ You can also get sqlncli.msi from the SQL Server 2012 Feature Pack web page. To
 
 ## See Also  
  [Building Applications with SQL Server Native Client](../../../relational-databases/native-client/applications/installing-sql-server-native-client.md)   
- [Installation How-to Topics](https://msdn.microsoft.com/library/59de41e7-557f-462a-8914-53ec35496baa)  
-  
+ [Installation How-to Topics](/previous-versions/sql/)  
 

docs/relational-databases/native-client/features/accessing-diagnostic-information-in-the-extended-events-log.md

@@ -14,9 +14,9 @@ monikerRange: ">=aps-pdw-2016||=azuresqldb-current||=azure-sqldw-latest||>=sql-s
 # Accessing SQL Server Native Client Diagnostic Information in the Extended Events Log
 [!INCLUDE [SQL Server](../../../includes/applies-to-version/sql-asdb-asdbmi-asa-pdw.md)]
 
-  Beginning in [!INCLUDE[ssSQL11](../../../includes/sssql11-md.md)], [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] Native Client and data access tracing ([Data Access Tracing](https://go.microsoft.com/fwlink/?LinkId=125805)) have been updated to make it easier to get diagnostic information about connection failures from the connectivity ring buffer and application performance information from the extended events log.  
+  Beginning in [!INCLUDE[ssSQL11](../../../includes/sssql11-md.md)], [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] Native Client and data access tracing ([Data Access Tracing](/previous-versions/sql/sql-server-2008/cc765421(v=sql.100))) have been updated to make it easier to get diagnostic information about connection failures from the connectivity ring buffer and application performance information from the extended events log.  
 
- For information about reading the extended events log, see [View Event Session Data](https://msdn.microsoft.com/library/ac742a01-2a95-42c7-b65e-ad565020dc49).  
+ For information about reading the extended events log, see [View Event Session Data](../../extended-events/advanced-viewing-of-target-data-from-extended-events-in-sql-server.md).  
 
 > [!NOTE]  
 >  This feature is intended only for troubleshooting and diagnostic purposes and may not be suitable for auditing or security purposes.  
@@ -210,4 +210,3 @@ class Bid2Etw_SQLNCLI11_1_Trace_TextW : Bid2Etw_SQLNCLI11_1_Trace
 ## See Also  
  [Handling Errors and Messages](../../../relational-databases/native-client-odbc-error-messages/handling-errors-and-messages.md)  
 
-  

docs/relational-databases/native-client/features/changing-passwords-programmatically.md

@@ -29,7 +29,7 @@ monikerRange: ">=aps-pdw-2016||=azuresqldb-current||=azure-sqldw-latest||>=sql-s
   Before [!INCLUDE[ssVersion2005](../../../includes/ssversion2005-md.md)], when a user's password expired, only an administrator could reset it. Beginning with [!INCLUDE[ssVersion2005](../../../includes/ssversion2005-md.md)], [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] Native Client supports handling password expiration programmatically through both the [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] Native Client OLE DB provider and the [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] Native Client ODBC driver, and through changes to the **SQL Server Login** dialog boxes.  
 
 > [!NOTE]  
->  When possible, prompt users to enter their credentials at run time and avoid storing their credentials in a persisted format. If you must persist their credentials, you should encrypt them using the [Win32 crypto API](https://go.microsoft.com/fwlink/?LinkId=64532). For more information about the use of passwords, see [Strong Passwords](../../../relational-databases/security/strong-passwords.md).  
+>  When possible, prompt users to enter their credentials at run time and avoid storing their credentials in a persisted format. If you must persist their credentials, you should encrypt them using the [Win32 crypto API](/windows/win32/seccrypto/cryptography-reference). For more information about the use of passwords, see [Strong Passwords](../../../relational-databases/security/strong-passwords.md).  
   
 ## SQL Server Login Error Codes  
  When a connection cannot be made because of authentication problems, one of the following SQL Server error codes will be available to the application to assist diagnosis and recovery.  
@@ -115,4 +115,3 @@ monikerRange: ">=aps-pdw-2016||=azuresqldb-current||=azure-sqldw-latest||>=sql-s
 ## See Also  
  [SQL Server Native Client Features](../../../relational-databases/native-client/features/sql-server-native-client-features.md)  
 
-  

docs/relational-databases/native-client/features/service-principal-name-spn-support-in-client-connections.md

@@ -36,7 +36,7 @@ monikerRange: ">=aps-pdw-2016||=azuresqldb-current||=azure-sqldw-latest||>=sql-s
 
 -   [Kerberos Technical Supplement for Windows](/previous-versions/msp-n-p/ff649429(v=pandp.10))  
 
--   [Microsoft Kerberos](https://go.microsoft.com/fwlink/?LinkID=100758)  
+-   [Microsoft Kerberos](/windows/win32/secauthn/microsoft-kerberos)  
 
 ## Usage  
  The following table describes the most common scenarios in which client applications can enable secure authentication.  
@@ -108,4 +108,3 @@ monikerRange: ">=aps-pdw-2016||=azuresqldb-current||=azure-sqldw-latest||>=sql-s
 ## See Also  
  [SQL Server Native Client Features](../../../relational-databases/native-client/features/sql-server-native-client-features.md)  
 [Register a Service Principal Name for Kerberos Connections](../../../database-engine/configure-windows/register-a-service-principal-name-for-kerberos-connections.md)  
-  

docs/relational-databases/native-client/features/sql-server-native-client-support-for-localdb.md

@@ -22,7 +22,7 @@ monikerRange: ">=aps-pdw-2016||=azuresqldb-current||=azure-sqldw-latest||>=sql-s
 
 -   [SQL Server Express LocalDB Reference](../../../relational-databases/sql-server-express-localdb-reference.md)  
 
--   [SQL Server 2016 Express LocalDB](../../../database-engine/configure-windows/sql-server-2016-express-localdb.md)  
+-   [SQL Server 2016 Express LocalDB](../../../database-engine/configure-windows/sql-server-express-localdb.md)  
 
  To summarize, LocalDB allows you to:  
 
@@ -41,4 +41,3 @@ SERVER=(localdb)\v11.0
 ## See Also  
  [SQL Server Native Client Features](../../../relational-databases/native-client/features/sql-server-native-client-features.md)  
 
-  

docs/relational-databases/native-client/features/working-with-query-notifications.md

@@ -110,7 +110,7 @@ RECEIVE * FROM MyQueue
 
 -   SQL_SOPT_SS_QUERYNOTIFICATION_TIMEOUT  
 
- If SQL_SOPT_SS_QUERYNOTIFICATION_MSGTEXT and SQL_SOPT_SS_QUERYNOTIFICATION_OPTIONS are not NULL, the query notifications TDS header containing the three attributes defined above will be sent to the server each time the command is executed. If either of them is null, the header is not sent, and SQL_SUCCESS_WITH_INFO is returned. The validation occurs on [SQLPrepare Function](https://go.microsoft.com/fwlink/?LinkId=59360), **SqlExecDirect**, and **SqlExecute**, all of which fail if the attributes are not valid. Similarly, when these query notification attributes are set for [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] versions before [!INCLUDE[ssVersion2005](../../../includes/ssversion2005-md.md)], the execution fails with SQL_SUCCESS_WITH_INFO.  
+ If SQL_SOPT_SS_QUERYNOTIFICATION_MSGTEXT and SQL_SOPT_SS_QUERYNOTIFICATION_OPTIONS are not NULL, the query notifications TDS header containing the three attributes defined above will be sent to the server each time the command is executed. If either of them is null, the header is not sent, and SQL_SUCCESS_WITH_INFO is returned. The validation occurs on [SQLPrepare Function](../../../odbc/reference/syntax/sqlprepare-function.md), **SqlExecDirect**, and **SqlExecute**, all of which fail if the attributes are not valid. Similarly, when these query notification attributes are set for [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] versions before [!INCLUDE[ssVersion2005](../../../includes/ssversion2005-md.md)], the execution fails with SQL_SUCCESS_WITH_INFO.  
 
 > [!NOTE]  
 >  Prepare statements will never cause the subscription to be initiated; subscription can be initiated by statement execution.  
@@ -133,4 +133,3 @@ RECEIVE * FROM MyQueue
 ## See Also  
  [SQL Server Native Client Features](../../../relational-databases/native-client/features/sql-server-native-client-features.md)  
 
-  

docs/relational-databases/native-client/finding-more-sql-server-native-client-information.md

@@ -23,10 +23,10 @@ monikerRange: ">=aps-pdw-2016||=azuresqldb-current||=azure-sqldw-latest||>=sql-s
  [Data Access and Storage Developer Center](https://go.microsoft.com/fwlink?linkid=4173)  
  This site provides technical articles, sample code, and other resources for [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Native Client and other data access technologies.  
 
- [Data Access Blog](https://docs.microsoft.com/archive/blogs/dataaccess/quick-update-re-data-access-blog)  
+ [Data Access Blog](/archive/blogs/dataaccess/quick-update-re-data-access-blog)  
  This blog site provides information about data access technologies and allows you to interact directly with members of the product team.  
 
- [Windows Data Access Components](https://go.microsoft.com/fwlink/?LinkId=107907)  
+ [Windows Data Access Components](/previous-versions/windows/desktop/ms692897(v=vs.85))  
  This site contains the latest Windows Data Access Components (Windows DAC) SDK documentation. Windows DAC is the version of the data access components (called MDAC in earlier versions) that is included in Windows Vista and Windows Server 2008.  
 
  The Window DAC SDK includes documentation for ActiveX Data Objects (ADO), OLE DB, and Open Database Connectivity (ODBC).  
@@ -35,4 +35,3 @@ monikerRange: ">=aps-pdw-2016||=azuresqldb-current||=azure-sqldw-latest||>=sql-s
 ## See Also  
  [SQL Server Native Client Programming](../../relational-databases/native-client/sql-server-native-client-programming.md)  
 
-  

docs/relational-databases/native-client/odbc/creating-a-driver-application.md

@@ -105,7 +105,7 @@ LIB=c:\Program Files\Microsoft Data Access SDK 2.8\Libs\x86\lib;C:\Program Files
 INCLUDE=c:\Program Files\Microsoft Data Access SDK 2.8\inc;C:\Program Files\Microsoft SQL Server\100\Tools\SDK\Include;  
 ```  
 
- One design decision made early in the process of building an application is whether the application needs to have multiple ODBC calls outstanding at the same time. There are two methods for supporting multiple concurrent ODBC calls, which are described in the remaining topics in this section. For more information, see the [ODBC Programmer's Reference](https://go.microsoft.com/fwlink/?LinkId=45250).  
+ One design decision made early in the process of building an application is whether the application needs to have multiple ODBC calls outstanding at the same time. There are two methods for supporting multiple concurrent ODBC calls, which are described in the remaining topics in this section. For more information, see the [ODBC Programmer's Reference](../../../odbc/reference/odbc-programmer-s-reference.md).  
 
 ## In This Section  
 
@@ -116,4 +116,3 @@ INCLUDE=c:\Program Files\Microsoft Data Access SDK 2.8\inc;C:\Program Files\Micr
 ## See Also  
  [SQL Server Native Client (ODBC)](../../../relational-databases/native-client/odbc/sql-server-native-client-odbc.md)  
 
-  

docs/relational-databases/native-client/odbc/performing-transactions-distributed-transactions.md

@@ -54,7 +54,7 @@ _(1)_ MSDTC can be invoked without ODBC. In such a case, MSDTC becomes the trans
 
 Suppose that your C++ Native Client ODBC application is enlisted in a distributed transaction. Next the application enlists in a second distributed transaction. In this case, the [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] Native Client ODBC driver leaves the original distributed transaction, and enlists in the new distributed transaction.
 
-For more information, see [DTC Programmer's Reference](https://docs.microsoft.com/previous-versions/windows/desktop/ms686108\(v=vs.85\)).
+For more information, see [DTC Programmer's Reference](/previous-versions/windows/desktop/ms686108(v=vs.85)).
 
 ## C# alternative for SQL Database in the cloud
 
@@ -72,4 +72,4 @@ The following other programming languages might not provide any support for dist
 
 ## See also
 
-[Performing Transactions (ODBC)](performing-transactions-in-odbc.md)
+[Performing Transactions (ODBC)](performing-transactions-in-odbc.md)

docs/relational-databases/native-client/odbc/performing-transactions-in-odbc.md

@@ -39,6 +39,5 @@ monikerRange: ">=aps-pdw-2016||=azuresqldb-current||=azure-sqldw-latest||>=sql-s
  ODBC applications should not use Transact-SQL transaction statements such as BEGIN TRANSACTION, COMMIT TRANSACTION, or ROLLBACK TRANSACTION because this can cause indeterminate behavior in the driver. An ODBC application should run in autocommit mode and not use any transaction management functions or statements, or run in manual-commit mode and use the ODBC **SQLEndTran** function to either commit or roll back transactions.  
 
 ## See Also  
- [Performing Transactions (ODBC)](https://msdn.microsoft.com/library/f431191a-5762-4f0b-85bb-ac99aff29724)  
-  
+ [Performing Transactions (ODBC)]()