1471191, worked on rows 10-30.

john-par · john-par · commit f7869853c2c5 · 2019-03-15T16:54:29.000-07:00
diff --git a/docs/analysis-services/languages-and-collations-analysis-services.md b/docs/analysis-services/languages-and-collations-analysis-services.md
@@ -62,7 +62,7 @@ manager: kfile
   
 -   0x0416 or 1046 for **Portuguese (Brazil)**.  
   
- To view a longer list, see [Locale IDs Assigned by Microsoft](http://msdn.microsoft.com/goglobal/bb964664.aspx). For more background, see [Encoding and Code Pages](http://msdn.microsoft.com/goglobal/bb688114.aspx).  
+ To view a longer list, see [Locale IDs Assigned by Microsoft](http://msdn.microsoft.com/goglobal/bb964664.aspx). For more background, see [Encoding and Code Pages](/globalization/encoding/encoding-overview).  
   
 > [!NOTE]  
 >  The **Language** property does not determine the language for returning system messages, or which strings appear in the user interface. Errors, warnings, and messages are localized into all languages supported in Office and Office 365 and are used automatically when the client connection specifies one of the supported locales.  
diff --git a/docs/connect/jdbc/reference/getcatalogs-method-sqlserverdatabasemetadata.md b/docs/connect/jdbc/reference/getcatalogs-method-sqlserverdatabasemetadata.md
@@ -39,7 +39,7 @@ public java.sql.ResultSet getCatalogs()
  This getCatalogs method is specified by the getCatalogs method in the java.sql.DatabaseMetaData interface.  
   
 > [!NOTE]  
->  On SQL Azure, you should connect to the master database to call **SQLServerDatabaseMetaData.getCatalogs**. SQL Azure does not support returning the entire set of catalogs from a user database. **SQLServerDatabaseMetaData.getCatalogs** uses the sys.databases view to get the catalogs. Please refer to the discussion of permissions in [sys.databases (SQL Azure Database)](https://go.microsoft.com/fwlink/?LinkId=217396) to understand **SQLServerDatabaseMetaData.getCatalogs** behavior on SQL Azure.  
+>  On SQL Azure, you should connect to the master database to call **SQLServerDatabaseMetaData.getCatalogs**. SQL Azure does not support returning the entire set of catalogs from a user database. **SQLServerDatabaseMetaData.getCatalogs** uses the sys.databases view to get the catalogs. Please refer to the discussion of permissions in [sys.database_usage (Azure SQL Database)](../../../relational-databases/system-catalog-views/sys-database-usage-azure-sql-database) to understand **SQLServerDatabaseMetaData.getCatalogs** behavior on SQL Azure.  
   
  The result set returned by the getCatalogs method will contain the following information:  
   
diff --git a/docs/data-quality-services/reference-data-services-in-dqs.md b/docs/data-quality-services/reference-data-services-in-dqs.md
@@ -53,7 +53,7 @@ manager: craigg
   
 1.  **Configuring the reference data provider details in DQS**: Before you can use reference data in DQS, you must configure reference data service details in DQS.  
   
-    1.  If you are using Marketplace, provide a valid Marketplace account key, browse to the [Data Quality Services](https://go.microsoft.com/fwlink/?LinkId=227587) data category in Marketplace, and subscribe to the required providers.  
+    1.  If you are using Marketplace, provide a valid Marketplace account key, browse to the [Data Services](https://azuremarketplace.microsoft.com/en-us/marketplace/apps/category/azure-active-directory-apps?page=1&subcategories=data-services) data category in Marketplace, and subscribe to the required providers.  
   
     2.  If you are using a direct online reference data provider, you must add direct reference data provider details in DQS before you can use it.  
   
diff --git a/docs/database-engine/install-windows/choose-a-database-engine-upgrade-method.md b/docs/database-engine/install-windows/choose-a-database-engine-upgrade-method.md
@@ -23,7 +23,7 @@ There are several approaches to consider when you are planning to upgrade the [!
   
 -   To download [!INCLUDE[SSnoversion](../../includes/ssnoversion-md.md)], go to  **[Evaluation Center](https://www.microsoft.com/evalcenter/evaluate-sql-server)**.  
   
--   Have an Azure account?  Then go **[Here](https://azuremarketplace.microsoft.com/marketplace/apps/Microsoft.FreeLicenseSQLServer2016SP1DeveloperWindowsServer2016)** to spin up a Virtual Machine with [!INCLUDE[ssnoversion](../../includes/ssnoversion-md.md)] Developer Edition already installed.  
+-   Have an Azure account?  Then go **[Here](https://azuremarketplace.microsoft.com/en-us/marketplace/apps/microsoftsqlserver.sql2019-ws2016?tab=Overview)** to spin up a Virtual Machine with [!INCLUDE[ssnoversion](../../includes/ssnoversion-md.md)] Developer Edition already installed.  
   
 > [!NOTE]  
 >  You may also consider upgrading the Azure SQL Database or virtualizing your SQL Server environment as part of your upgrade plan. These articles are out of scope for this article, but here are some links:
diff --git a/docs/relational-databases/errors-events/mssqlserver-823-database-engine-error.md b/docs/relational-databases/errors-events/mssqlserver-823-database-engine-error.md
@@ -28,7 +28,7 @@ manager: craigg
 |Message Text|The operating system returned error %ls to SQL Server during a %S_MSG at offset %#016I64x in file '%ls'. Additional messages in the SQL Server error log and system event log may provide more detail. This is a severe system-level error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.|  
   
 ## Explanation  
-A Windows read or write request has failed. The error code that is returned by Windows and the corresponding text are inserted into the message. In the read case, [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] will have already retried the read request four times. This error is often the result of a hardware error, but may be caused by the device driver. For more information about error 823, see [https://support.microsoft.com/kb/828339](https://support.microsoft.com/kb/828339). For more information about I/O errors, see [Microsoft SQL Server I/O Basics, Chapter 2](https://go.microsoft.com/fwlink/?LinkId=69370).  
+A Windows read or write request has failed. The error code that is returned by Windows and the corresponding text are inserted into the message. In the read case, [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] will have already retried the read request four times. This error is often the result of a hardware error, but may be caused by the device driver. For more information about error 823, see [https://support.microsoft.com/kb/828339](https://support.microsoft.com/kb/828339). For more information about I/O errors, see [Microsoft SQL Server I/O Basics, Chapter 2](/previous-versions/sql/sql-server-2005/administrator/cc917726(v=technet.10)).  
   
 ## User Action  
 Check for additional information in the system event log. Contact the hardware manufacturer or Microsoft Customer Services and Support to determine the cause and corrective action. After the hardware error is fixed, restore all databases and run DBCC CHECKDB.  
diff --git a/docs/relational-databases/errors-events/mssqlserver-825-database-engine-error.md b/docs/relational-databases/errors-events/mssqlserver-825-database-engine-error.md
@@ -28,7 +28,7 @@ manager: craigg
 |Message Text|A read of the file '%ls' at offset %#016I64x succeeded after failing %d time(s) with error: %ls. Additional messages in the SQL Server error log and system event log may provide more detail. This error condition threatens database integrity and must be corrected. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.|  
   
 ## Explanation  
-This message indicates that the read operation had to be reissued at least one time, and indicates a major problem with the disk hardware. This message does not currently indicate a [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] problem, but the disk problem could cause data loss or database corruption if it is not resolved. The system event log may contain related events that help to diagnose the problem. For more information about I/O errors, see [Microsoft SQL Server I/O Basics, Chapter 2](https://go.microsoft.com/fwlink/?LinkId=69370).  
+This message indicates that the read operation had to be reissued at least one time, and indicates a major problem with the disk hardware. This message does not currently indicate a [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] problem, but the disk problem could cause data loss or database corruption if it is not resolved. The system event log may contain related events that help to diagnose the problem. For more information about I/O errors, see [Microsoft SQL Server I/O Basics, Chapter 2](previous-versions/sql/sql-server-2005/administrator/cc917726(v=technet.10)).  
   
 ## User Action  
 The following actions may help you identify and resolve the underlying problem:  
diff --git a/docs/relational-databases/policy-based-management/check-disk-input-and-output-subsystem-for-io-delay-problems.md b/docs/relational-databases/policy-based-management/check-disk-input-and-output-subsystem-for-io-delay-problems.md
@@ -36,6 +36,4 @@ manager: craigg
   
  [Microsoft Knowledge Base article 897284](https://go.microsoft.com/fwlink/?linkid=117743)  
   
- [SQL Server I/O Basics, Chapter 2](https://go.microsoft.com/fwlink/?LinkId=69370)  
-  
-  
+ [SQL Server I/O Basics, Chapter 2](previous-versions/sql/sql-server-2005/administrator/cc917726(v=technet.10))
diff --git a/docs/relational-databases/search/create-and-manage-full-text-catalogs.md b/docs/relational-databases/search/create-and-manage-full-text-catalogs.md
@@ -40,7 +40,7 @@ GO
   
 3.  Select **New Full-Text Catalog**.  
   
-4.  In the **New Full-Text Catalog** dialog box, specify the information for the catalog that you are re-creating. For more information, see [New Full-Text Catalog &#40;General Page&#41;](https://msdn.microsoft.com/library/5ed6f7cd-d9af-4439-9f33-fc935b883d91).  
+4.  In the **New Full-Text Catalog** dialog box, specify the information for the catalog that you are re-creating. For more information, see [New Full-Text Catalog &#40;General Page&#41;](../../2014/database-engine/new-full-text-catalog-general-page.md).  
   
     > [!NOTE]  
     >  Full-text catalog IDs begin at 00005 and are incremented by one for each new catalog created.  
diff --git a/docs/relational-databases/security/encryption/setup-steps-for-extensible-key-management-using-the-azure-key-vault.md b/docs/relational-databases/security/encryption/setup-steps-for-extensible-key-management-using-the-azure-key-vault.md
@@ -170,7 +170,7 @@ SQL Server Version  |Redistributable Install Link
  
     1. Create your encryption key locally on a local HSM device. (Make sure this is an asymmetric, RSA 2048 key so it's is supported by SQL Server.)
     2. Import the encryption key to Azure Key Vault. See the steps below for how to do that.
-    3. Before using the key in Azure Key Vault for the first time, take an Azure Key Vault key backup. Learn more about the [Backup-AzureKeyVaultKey](https://msdn.microsoft.com/library/mt126292.aspx) command.
+    3. Before using the key in Azure Key Vault for the first time, take an Azure Key Vault key backup. Learn more about the [Backup-AzureKeyVaultKey](/sql/relational-databases/security/encryption/setup-steps-for-extensible-key-management-using-the-azure-key-vault) command.
     4. Whenever any changes are made to the key (for example add ACLs, add tags, add key attributes), be sure to take another Azure Key Vault key backup.
 
         > [!NOTE]  
diff --git a/docs/relational-databases/system-catalog-views/sys-pdw-nodes-tables-transact-sql.md b/docs/relational-databases/system-catalog-views/sys-pdw-nodes-tables-transact-sql.md
@@ -21,7 +21,7 @@ monikerRange: ">= aps-pdw-2016 || = azure-sqldw-latest || = sqlallproducts-allve
   
 |Column Name|Data Type|Description|Range|  
 |-----------------|---------------|-----------------|-----------|  
-|\<inherited columns>||For a list of columns that this view inherits, see [sys.objects](https://msdn.microsoft.com/c36fa71e-549a-4533-a6cd-1314d26f533f).||  
+|\<inherited columns>||For a list of columns that this view inherits, see [sys.objects](../system-dynamic-management-views/sys-dm-pdw-request-steps-transact-sql.md).||  
 |lob_data_space_id|**int**||Always 0.|  
 |filestream_data_space_id|**int**|Data space ID for a FILESTREAM filegroup or [!INCLUDE[ssInfoNA](../../includes/ssinfona-md.md)]|NULL|  
 |max_column_id_used|**int**|Maximum column ID used by this table.||  
diff --git a/docs/reporting-services/security/reporting-services-roles-tasks-vs-sharepoint-groups-permissions.md b/docs/reporting-services/security/reporting-services-roles-tasks-vs-sharepoint-groups-permissions.md
@@ -24,7 +24,7 @@ ms.author: maghan
   
 ||  
 |-|  
-| [!INCLUDE[applies](../../includes/applies-md.md)]<br /><br /> [!INCLUDE[ssRSnoversion](../../includes/ssrsnoversion-md.md)] SharePoint mode &#124; SharePoint 2010 and SharePoint 2013<br /><br /> [!INCLUDE[ssRSnoversion](../../includes/ssrsnoversion-md.md)] Native mode|  
+| [!INCLUDE[applies](../../includes/applies-md.md)]<br /><br /> [!INCLUDE[ssRSnoversion](../../includes/ssrsnoversion-md.md)] SharePoint mode &#124; SharePoint 2010 and SharePoint 2013<br /><br /> [!INCLUDE[ssRSnoversion](../../includes/ssrsnoversion-md.md)] Native mode|  
   
  **In this topic:**  
   
@@ -47,7 +47,7 @@ ms.author: maghan
 |---|**Permission level group:** For example "View Only" for the "Viewers" group.|  
 |**Tasks:** for example "Manage Reports".|**Permissions:** For example, within the "View Only" group there are list related permissions of view items, view versions, and view application pages.|  
   
- For more information on SharePoint permissions, see [Permission levels and permissions](https://office.microsoft.com/windows-sharepoint-services-help/permission-levels-and-permissions-HA010100149.aspx) and [Determine permission levels and groups in SharePoint 2013](https://technet.microsoft.com/library/cc262690.aspx).  
+ For more information on SharePoint permissions, see [Permission levels and permissions](https://support.office.com/en-us/article/Understand-groups-and-permissions-on-a-SharePoint-site-258E5F33-1B5A-4766-A503-D86655CF950D) and [Determine permission levels and groups in SharePoint 2013](https://technet.microsoft.com/library/cc262690.aspx).  
   
 ##  <a name="bkmk_compare_roles_groups"></a> Compare Native mode Roles and SharePoint Groups  
  The following table compares the predefined role definitions in [!INCLUDE[ssRSnoversion](../../includes/ssrsnoversion-md.md)] in native mode to standard SharePoint groups. If the SharePoint groups do not match the specific role that you want, you can create a custom group and assign permission levels in SharePoint.  
diff --git a/docs/sql-server/sql-server-2012-sp4-release-notes.md b/docs/sql-server/sql-server-2012-sp4-release-notes.md
@@ -89,7 +89,7 @@ Use the table below to identify the location and name of the file to download ba
 
 ### Download pages  
 - [SQL Server 2012 SP1 Feature Pack](https://go.microsoft.com/fwlink/p/?LinkID=268158)
-- [SQL Server 2012 SP1 Express](https://go.microsoft.com/fwlink/p/?LinkID=26815)
+- [SQL Server 2012 SP1 Express](https://www.microsoft.com/en-us/download/details.aspx?id=35579)
 
 
 Use the following table to determine which file to download and install. Verify that you have the correct system requirements before installing the service pack. The system requirements are provided on the download pages that are linked to in the table.  
diff --git a/docs/sql-server/what-s-new-in-sql-server-2017.md b/docs/sql-server/what-s-new-in-sql-server-2017.md
@@ -80,7 +80,7 @@ SQL Server Analysis Services 2017 introduces many enhancements for tabular model
 - DAX Editor for SSDT. (CTP 2.0)
 - Encoding hints, an advanced feature for optimizing data refresh of large in-memory tabular models. (CTP 1.3)
 - Support for the **1400 Compatibility level** for tabular models. To create new or upgrade existing tabular model projects to the 1400 compatibility level, download and install [SQL Server Data Tools (SSDT) 17.0 RC2](https://go.microsoft.com/fwlink?LinkId=837939). (CTP 1.1)
-- A modern **Get Data** experience for tabular models at the 1400 compatibility level. See the [Analysis Services Team Blog](https://blogs.msdn.microsoft.com/analysisservices/2016/12/16/introducing-a-modern-get-data-experience-for-sql-server-2017-on-windows-ctp-1-1-for-analysis-services/). (CTP 1.1)
+- A modern **Get Data** experience for tabular models at the 1400 compatibility level. See the [Analysis Services Team Blog](https://blogs.msdn.microsoft.com/analysisservices/2016/12/16/introducing-a-modern-get-data-experience-for-sql-server-vnext-on-windows-ctp-1-1-for-analysis-services/). (CTP 1.1)
 - **Hide Members** property to hide blank members in ragged hierarchies. (CTP 1.1)
 - New **Detail Rows** end-user action to **Show Details** for aggregated information. [SELECTCOLUMNS](https://msdn.microsoft.com/library/mt761759.aspx) and **DETAILROWS** functions for creating Detail Rows expressions. (CTP 1.1)
 - DAX **IN** operator for specifying multiple values. (CTP 1.1)
diff --git a/docs/t-sql/queries/explain-transact-sql.md b/docs/t-sql/queries/explain-transact-sql.md
@@ -61,7 +61,7 @@ EXPLAIN SQL_statement
 |\<sql>|Echoes *SQL_statement*.|  
 |\<params>|This tag is not used at this time.|  
 |\<dsql_operations>|Summarizes and contains the query steps, and includes cost information for the query. Also contains all of the `<dsql_operation>` blocks. This tag contains count information for the entire query:<br /><br /> `<dsql_operations total_cost=total_cost total_number_operations=total_number_operations>`<br /><br /> *total_cost* is the total estimated time for the query to run, in ms.<br /><br /> *total_number_operations* is the total number of operations for the query. An operation that will be parallelized and run on multiple nodes is counted as a single operation.|  
-|\<dsql_operation>|Describes a single operation within the query plan. The \<dsql_operation> tag contains the operation type as an attribute:<br /><br /> `<dsql_operation operation_type=operation_type>`<br /><br /> *operation_type* is one of the values found in [Querying Data (SQL Server PDW)](https://msdn.microsoft.com/3f4f5643-012a-4c36-b5ec-691c4bbe668c).<br /><br /> The content in the `\<dsql_operation>` block is dependent on the operation type.<br /><br /> See the table below.|  
+|\<dsql_operation>|Describes a single operation within the query plan. The \<dsql_operation> tag contains the operation type as an attribute:<br /><br /> `<dsql_operation operation_type=operation_type>`<br /><br /> *operation_type* is one of the values found in [sys.dm_pdw_request_steps (Transact-SQL)](../../relational-databases/system-dynamic-management-views/sys-dm-pdw-request-steps-transact-sql.md).<br /><br /> The content in the `\<dsql_operation>` block is dependent on the operation type.<br /><br /> See the table below.|  
   
 |Operation Type|Content|Example|  
 |--------------------|-------------|-------------|  
diff --git a/docs/t-sql/statements/delete-transact-sql.md b/docs/t-sql/statements/delete-transact-sql.md
@@ -452,7 +452,7 @@ OPTION ( LABEL = N'label1' );
 ```  
   
 ### N. Using a label and a query hint with the DELETE statement  
- This query shows the basic syntax for using a query join hint with the DELETE statement. For more information on join hints and how to use the OPTION clause, see [OPTION (SQL Server PDW)](https://msdn.microsoft.com/72bbce98-305b-42fa-a19f-d89620621ecc).  
+ This query shows the basic syntax for using a query join hint with the DELETE statement. For more information on join hints and how to use the OPTION clause, see [OPTION Clause (Transact-SQL)](../queries/option-clause-transact-sql).
   
 ```sql
 -- Uses AdventureWorks  
