Merge pull request #17343 from DCtheGeek/dmc-links-relationaldatabases-1

Links: SQL - relational-databases - 1

Author: MikeRayMSFT

docs/relational-databases/clr-integration/database-objects/getting-started-with-clr-integration.md

@@ -84,7 +84,7 @@ End Class
 
 ```  
 
-This simple program contains a single static method on a public class. This method uses two new classes, **[SqlContext](https://msdn.microsoft.com/library/microsoft.sqlserver.server.sqlcontext.aspx)** and **[SqlPipe](https://msdn.microsoft.com/library/microsoft.sqlserver.server.sqlpipe.aspx)**, for creating managed database objects to output a simple text message. The method also assigns the string "Hello world!" as the value of an out parameter. This method can be declared as a stored procedure in [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)], and then run in the same manner as a [!INCLUDE[tsql](../../../includes/tsql-md.md)] stored procedure.  
+This simple program contains a single static method on a public class. This method uses two new classes, **[SqlContext](/dotnet/api/microsoft.sqlserver.server.sqlcontext)** and **[SqlPipe](/dotnet/api/microsoft.sqlserver.server.sqlpipe)**, for creating managed database objects to output a simple text message. The method also assigns the string "Hello world!" as the value of an out parameter. This method can be declared as a stored procedure in [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)], and then run in the same manner as a [!INCLUDE[tsql](../../../includes/tsql-md.md)] stored procedure.  
 
 Compile this program as a library, load it into [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)], and run it as a stored procedure.  
 
@@ -169,7 +169,7 @@ IF EXISTS (SELECT name FROM sys.assemblies WHERE name = 'helloworld')
 
 For more information about CLR integration in SQL Server, see the following articles:
 
-- [CLR Stored Procedures](https://msdn.microsoft.com/library/bbdd51b2-a9b4-4916-ba6f-7957ac6c3f33)
+- [CLR Stored Procedures](/dotnet/framework/data/adonet/sql/clr-stored-procedures)
 - [SQL Server In-Process Specific Extensions to ADO.NET](../../../relational-databases/clr-integration-data-access-in-process-ado-net/sql-server-in-process-specific-extensions-to-ado-net.md)
 - [Debugging CLR Database Objects](../../../relational-databases/clr-integration/debugging-clr-database-objects.md)
-- [CLR Integration Security](../../../relational-databases/clr-integration/security/clr-integration-security.md)
+- [CLR Integration Security](../../../relational-databases/clr-integration/security/clr-integration-security.md)

docs/relational-databases/clr-integration/debugging-clr-database-objects.md

@@ -41,7 +41,7 @@ Due to the above restrictions, we recommend that [!INCLUDE[tsql](../../includes/
 
 Debugging in [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] follows a per-connection model. A debugger can detect and debug activities only to the client connection to which it is attached. Because the functionality of the debugger is not limited by the type of connection, both tabular data stream (TDS) and HTTP connections can be debugged. However, [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] does not allow debugging existing connections. Debugging supports all common debugging features within routines executing on the server. The interaction between a debugger and [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] happens through distributed Component Object Model (COM).  
 
-For more information and scenarios about debugging managed stored procedures, functions, triggers, user-defined types, and aggregates, see [SQL Server CLR Integration Database Debugging](https://go.microsoft.com/fwlink/?LinkId=120378) in the Visual Studio documentation.  
+For more information and scenarios about debugging managed stored procedures, functions, triggers, user-defined types, and aggregates, see [SQL Server CLR Integration Database Debugging](/previous-versions/ms165050(v=vs.100)) in the Visual Studio documentation.  
 
 The TCP/IP network protocol must be enabled on the [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] instance in order to use Visual Studio for remote development, debugging, and development. For more information about enabling TCP/IP protocol on the server, see [Configure Client Protocols](../../database-engine/configure-windows/configure-client-protocols.md).  
 
@@ -110,6 +110,6 @@ EXEC GetVersion
 
 ## Next steps
 
-For more information about debugging managed code using Visual Studio, see [Debugging Managed Code](https://go.microsoft.com/fwlink/?LinkId=120377) in the Visual Studio documentation.  
+For more information about debugging managed code using Visual Studio, see [Debugging Managed Code](/visualstudio/debugger/debugging-managed-code) in the Visual Studio documentation.  
 
 For more information, see [Common Language Runtime integration programming concepts](../../relational-databases/clr-integration/common-language-runtime-clr-integration-programming-concepts.md)  

docs/relational-databases/clr-integration/deploying-clr-database-objects.md

@@ -70,7 +70,7 @@ ms.author: "jroth"
 
  `EXTERNAL NAME HelloWorld.Procedures.HelloWorld`  
 
- For more information about creating the different types of managed database objects in [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)], see [CLR User-Defined Functions](../../relational-databases/clr-integration-database-objects-user-defined-functions/clr-user-defined-functions.md), [CLR User-Defined Aggregates](../../relational-databases/clr-integration-database-objects-user-defined-functions/clr-user-defined-aggregates.md), [CLR User-Defined Types](../../relational-databases/clr-integration-database-objects-user-defined-types/clr-user-defined-types.md), [CLR Stored Procedures](https://msdn.microsoft.com/library/bbdd51b2-a9b4-4916-ba6f-7957ac6c3f33), and [CLR Triggers](https://msdn.microsoft.com/library/302a4e4a-3172-42b6-9cc0-4a971ab49c1c).  
+ For more information about creating the different types of managed database objects in [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)], see [CLR User-Defined Functions](../../relational-databases/clr-integration-database-objects-user-defined-functions/clr-user-defined-functions.md), [CLR User-Defined Aggregates](../../relational-databases/clr-integration-database-objects-user-defined-functions/clr-user-defined-aggregates.md), [CLR User-Defined Types](../../relational-databases/clr-integration-database-objects-user-defined-types/clr-user-defined-types.md), [CLR Stored Procedures](/dotnet/framework/data/adonet/sql/clr-stored-procedures), and [CLR Triggers](/dotnet/framework/data/adonet/sql/clr-triggers).  
 
 ## Deploying the Assembly to Production Servers  
  Once the CLR database objects have been tested and verified on the test server, they can be distributed to production servers. For more information about debugging managed database objects, see [Debugging CLR Database Objects](../../relational-databases/clr-integration/debugging-clr-database-objects.md).  
@@ -103,4 +103,3 @@ ms.author: "jroth"
 ## See Also  
  [Common Language Runtime (CLR) Integration Programming Concepts](../../relational-databases/clr-integration/common-language-runtime-clr-integration-programming-concepts.md)  
 
-  

docs/relational-databases/clr-integration/monitoring-and-troubleshooting-managed-database-objects.md

@@ -24,7 +24,7 @@ ms.author: "jroth"
 
 |Event|Description|  
 |-----------|-----------------|  
-|[Assembly Load Event Class](https://docs.microsoft.com/sql/relational-databases/event-classes/sql-server-event-class-reference)|Used to monitor assembly load requests (success and failures).|  
+|[Assembly Load Event Class](../event-classes/sql-server-event-class-reference.md)|Used to monitor assembly load requests (success and failures).|  
 |[SQL:BatchStarting Event Class](../../relational-databases/event-classes/sql-batchstarting-event-class.md), [SQL:BatchCompleted Event Class](../../relational-databases/event-classes/sql-batchcompleted-event-class.md)|Provides information about [!INCLUDE[tsql](../../includes/tsql-md.md)] batches that have started or completed.|  
 |[SP:Starting Event Class](../../relational-databases/event-classes/sp-starting-event-class.md), [SP:Completed Event Class](../../relational-databases/event-classes/sp-completed-event-class.md)|Used to monitor the execution of [!INCLUDE[tsql](../../includes/tsql-md.md)] stored procedures.|  
 |[SQL:StmtStarting Event Class](../../relational-databases/event-classes/sql-stmtstarting-event-class.md), [SQL:StmtCompleted Event Class](../../relational-databases/event-classes/sql-stmtcompleted-event-class.md)|Used to monitor the execution of CLR and [!INCLUDE[tsql](../../includes/tsql-md.md)] routines.|  
@@ -81,4 +81,3 @@ ms.author: "jroth"
 ## See Also  
  [Common Language Runtime (CLR) Integration Programming Concepts](../../relational-databases/clr-integration/common-language-runtime-clr-integration-programming-concepts.md)  
 
-  

docs/relational-databases/clr-integration/security/clr-integration-security.md

@@ -42,10 +42,10 @@ ms.author: "jroth"
  [Host Protection Attributes and CLR Integration Programming](../../../relational-databases/clr-integration-security-host-protection-attributes/host-protection-attributes-and-clr-integration-programming.md)  
  Provides information about the host protection attribute (HPA) values that are disallowed in SAFE and EXTERNAL_ACCESS assemblies.  
 
- [Links in CLR Integration Security](https://msdn.microsoft.com/library/168efd01-d12e-4bdf-a1b3-0b5c76474eaf)  
+ [Links in CLR Integration Security]()  
  Describes how pieces of user-code can call each other in [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)].  
 
- [Impersonation and CLR Integration Security](https://msdn.microsoft.com/library/1495a7af-2248-4cee-afdb-9269fb3a7774)  
+ [Impersonation and CLR Integration Security](../data-access/impersonation-and-credentials-for-connections.md)  
  Discusses how managed code accesses external resources using impersonation.  
 
  Discusses issues that arise when a managed method invokes a method in a class contained in another assembly.  
@@ -56,4 +56,3 @@ ms.author: "jroth"
 ## See Also  
  [Managing CLR Integration Assemblies](../../../relational-databases/clr-integration/assemblies/managing-clr-integration-assemblies.md)  
 
-  

docs/relational-databases/collations/collation-and-unicode-support.md

@@ -423,7 +423,7 @@ SELECT name FROM customer ORDER BY name COLLATE Latin1_General_CS_AI;
 ```    
 
 ###  <a name="Locale_Defn"></a> Locale    
-A locale is a set of information that's associated with a location or a culture. The information can include the name and identifier of the spoken language, the script that's used to write the language, and cultural conventions. Collations can be associated with one or more locales. For more information, see [Locale IDs Assigned by Microsoft](https://msdn.microsoft.com/goglobal/bb964664.aspx).    
+A locale is a set of information that's associated with a location or a culture. The information can include the name and identifier of the spoken language, the script that's used to write the language, and cultural conventions. Collations can be associated with one or more locales. For more information, see [Locale IDs Assigned by Microsoft](/openspecs/windows_protocols/ms-lcid/a9eac961-e77d-41a6-90a5-ce1a8b0cdb9c).    
 
 ###  <a name="Code_Page_Defn"></a> Code page    
 A code page is an ordered set of characters of a given script in which a numeric index, or code point value, is associated with each character. A Windows code page is typically referred to as a *character set* or a *charset*. Code pages are used to provide support for the character sets and keyboard layouts that are used by different Windows system locales.     
@@ -650,4 +650,4 @@ For more information, see the following related content:
 [Contained Database Collations](../../relational-databases/databases/contained-database-collations.md)     
 [Choose a Language When Creating a Full-Text Index](../../relational-databases/search/choose-a-language-when-creating-a-full-text-index.md)     
 [sys.fn_helpcollations (Transact-SQL)](../../relational-databases/system-functions/sys-fn-helpcollations-transact-sql.md)       
-[Single-Byte and Multibyte Character Sets](https://docs.microsoft.com/cpp/c-runtime-library/single-byte-and-multibyte-character-sets)      
+[Single-Byte and Multibyte Character Sets](/cpp/c-runtime-library/single-byte-and-multibyte-character-sets)

docs/relational-databases/collations/set-or-change-the-database-collation.md

@@ -139,8 +139,7 @@ GO
  [COLLATE (Transact-SQL)](~/t-sql/statements/collations.md)   
  [Collation Precedence (Transact-SQL)](../../t-sql/statements/collation-precedence-transact-sql.md)   
  [CREATE TABLE (Transact-SQL)](../../t-sql/statements/create-table-transact-sql.md)   
- [CREATE DATABASE (SQL Server Transact-SQL)](../../t-sql/statements/create-database-sql-server-transact-sql.md)   
+ [CREATE DATABASE (SQL Server Transact-SQL)](../../t-sql/statements/create-database-transact-sql.md)   
  [ALTER TABLE (Transact-SQL)](../../t-sql/statements/alter-table-transact-sql.md)   
  [ALTER DATABASE (Transact-SQL)](../../t-sql/statements/alter-database-transact-sql.md)  
 
-  

docs/relational-databases/collations/set-or-change-the-server-collation.md

@@ -56,7 +56,7 @@ ms.author: "sstein"
 > Instead of changing the default collation of an instance of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)], you can specify a default collation for each new database you create via the `COLLATE` clause of the `CREATE DATABASE` and `ALTER DATABASE` statements. For more information, see [Set or Change the Database Collation](set-or-change-the-database-collation.md).  
   
 ## Setting the server collation in Managed Instance
-Server-level collation in Azure SQL Managed Instance can be specified when the instance is created and cannot be changed later. You can set server-level collation via [Azure portal](https://docs.microsoft.com/azure/sql-database/sql-database-managed-instance-get-started#create-a-managed-instance) or [PowerShell and Resource Manager template](https://docs.microsoft.com/azure/sql-database/scripts/sql-managed-instance-create-powershell-azure-resource-manager-template) while you are creating the instance. Default server-level collation is **SQL_Latin1_General_CP1_CI_AS**. Unicode-only and new UTF-8 collations cannot be specified as server-level collation.
+Server-level collation in Azure SQL Managed Instance can be specified when the instance is created and cannot be changed later. You can set server-level collation via [Azure portal](/azure/sql-database/sql-database-managed-instance-get-started#create-a-managed-instance) or [PowerShell and Resource Manager template](/azure/sql-database/scripts/sql-managed-instance-create-powershell-azure-resource-manager-template) while you are creating the instance. Default server-level collation is **SQL_Latin1_General_CP1_CI_AS**. Unicode-only and new UTF-8 collations cannot be specified as server-level collation.
 If you are migrating databases from SQL Server to Managed Instance, check the server collation in the source SQL Server using `SERVERPROPERTY(N'Collation')` function and create a Managed Instance that matches the collation of your SQL Server. Migrating a database from SQL Server to Managed Instance with the server-level collations that are not matched might cause several unexpected errors in the queries. You cannot change the server-level collation on the existing Managed Instance.
 
 ## See Also
@@ -65,4 +65,3 @@ If you are migrating databases from SQL Server to Managed Instance, check the se
  [Set or Change the Database Collation](../../relational-databases/collations/set-or-change-the-database-collation.md)   
  [Set or Change the Column Collation](../../relational-databases/collations/set-or-change-the-column-collation.md)   
  [Rebuild System Databases](../../relational-databases/databases/rebuild-system-databases.md)  
- 

docs/relational-databases/data-collection/configure-the-management-data-warehouse-sql-server-management-studio.md

@@ -67,7 +67,7 @@ ms.author: mathoma
  Use this page to select a [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] database server and management data warehouse. The management data warehouse is a relational database that will store collected data.  
 
 > [!NOTE]  
->  You must have the appropriate level of permissions in order to create the management data warehouse on the server. For more information, see [CREATE DATABASE (SQL Server Transact-SQL)](../../t-sql/statements/create-database-sql-server-transact-sql.md). You also must have the appropriate level of permissions to create logins for management data warehouse roles.  
+>  You must have the appropriate level of permissions in order to create the management data warehouse on the server. For more information, see [CREATE DATABASE (SQL Server Transact-SQL)](../../t-sql/statements/create-database-transact-sql.md). You also must have the appropriate level of permissions to create logins for management data warehouse roles.  
   
  **Server name**  
  Specifies the name of the server that will host the management data warehouse.  
@@ -134,4 +134,3 @@ ms.author: mathoma
  [Data Collection](../../relational-databases/data-collection/data-collection.md)   
  [Manage Data Collection](../../relational-databases/data-collection/manage-data-collection.md)  
 
-  

docs/relational-databases/data-collection/data-collection.md

@@ -24,7 +24,7 @@ ms.author: mathoma
 
  The data collector enables you to adjust the scope of data collection to suit your test and production environments. The data collector also uses a data warehouse, a relational database that enables you to manage the data that you collect by setting different retention periods for your data.  
 
- The data collector supports dynamic tuning for data collection and is extensible through its API. For more information, see [Data Collector Programming](https://docs.microsoft.com/sql/relational-databases/system-functions/data-collector-functions-transact-sql).  
+ The data collector supports dynamic tuning for data collection and is extensible through its API. For more information, see [Data Collector Programming](../system-functions/data-collector-functions-transact-sql.md).  
 
  The following illustration shows how the data collector fits in the overall strategy for data collection and data management in [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)].  
 
@@ -45,7 +45,7 @@ ms.author: mathoma
 
 -   Proxy accounts  
 
- For more information, see [Automated Administration Tasks (SQL Server Agent)](https://msdn.microsoft.com/library/541ee5ac-2c9f-4b74-b4f0-13b7bd5920b0).  
+ For more information, see [Automated Administration Tasks (SQL Server Agent)](../../ssms/agent/automated-administration-tasks-sql-server-agent.md).  
 
  [!INCLUDE[ssISnoversion](../../includes/ssisnoversion-md.md)] ([!INCLUDE[ssIS](../../includes/ssis-md.md)]) is used to execute packages that collect data from individual data providers. You should be familiar with the following [!INCLUDE[ssIS](../../includes/ssis-md.md)] tools and concepts:  
 
@@ -113,5 +113,3 @@ ms.author: mathoma
 |Use the Management Data Warehouse to collect data from a server that is a data collection target.|[Management Data Warehouse](../../relational-databases/data-collection/management-data-warehouse.md)| 
 |Exploit the server-side trace capabilities of SQL Server Profiler to export a trace definition that you can use to create a collection set that uses the Generic SQL Trace collector type| [Use SQL Server Profiler to Create a SQL Trace Collection Set (SQL Server Management Studio)](use-sql-server-profiler-to-create-a-sql-trace-collection-set.md)
 
-  
-