Merge branch 'master' into ssis-lift-shift

Author: douglaslMS

contributor-guide/templates/overview-template-annotated-example.md

@@ -116,7 +116,7 @@ A SQL Database backup includes both local database backups and geo-redundant bac
 	Explains first component of the backup capabilities
 ------------------>
 
-For local backups, SQL Database uses SQL Server technology to create [full](https://msdn.microsoft.com/library/ms186289.aspx), [differential](https://msdn.microsoft.com/library/ms175526.aspx ), and [transaction log](https://msdn.microsoft.com/library/ms191429.aspx) backups. The transaction log backups happen every five minutes, which allows you to do a point-in-time restore to the same server that hosts the database. When you restore a database, the service figures out which full, differential, and transaction log backups need to be restored.
+For local backups, SQL Database uses SQL Server technology to create [full](/sql-docs/docs/relational-databases/backup-restore/full-database-backups-sql-server), [differential](/sql-docs/docs/relational-databases/backup-restore/differential-backups-sql-server) backups. The transaction log backups happen every five minutes, which allows you to do a point-in-time restore to the same server that hosts the database. When you restore a database, the service figures out which full, differential, and transaction log backups need to be restored.
 
 <!--------------- 
 	Explicit list of what to do with a local backup. "Use a ..." helps people to scan the topic and find the uses quickly.
@@ -156,7 +156,7 @@ SQL Database provides up to 200% of your maximum provisioned database storage as
 
 ## How often do backups happen?
 
-For local database backups, full database backups happen weekly, differential database backups happen hourly, and transaction log backups happen every five minutes. The first full backup is scheduled immediately after a database is created. It usually completes within 30 minutes, but it can take longer when the database is of a significant size. For example, the initial backup can take longer on a restored database or a database copy. After the first full backup, all further backups are scheduled automatically and managed silently in the background. The exact timing of full and [differential](https://msdn.microsoft.com/library/ms175526.aspx) database backups is determined as it balances the overall system workload. 
+For local database backups, full database backups happen weekly, differential database backups happen hourly, and transaction log backups happen every five minutes. The first full backup is scheduled immediately after a database is created. It usually completes within 30 minutes, but it can take longer when the database is of a significant size. For example, the initial backup can take longer on a restored database or a database copy. After the first full backup, all further backups are scheduled automatically and managed silently in the background. The exact timing of full and [differential](/sql-docs/docs/relational-databases/backup-restore/differential-backups-sql-server) database backups is determined as it balances the overall system workload. 
 
 For geo-redundant backups, full and differential backups are copied according to the Azure Storage replication schedule.
 

docs-msdn/analytics-platform-system/acquire-and-configure-backup-server.md

@@ -94,9 +94,9 @@ PDW will access the backup server through a UNC file share. To set up the file s
   
     For more information, see these stored procedures:  
   
-    -   [sp_pdw_add_network_credentials](https://msdn.microsoft.com/library/mt204011.aspx)  
+    -   [sp_pdw_add_network_credentials](/sql-docs/docs/relational-databases/system-stored-procedures/sp-pdw-add-network-credentials-sql-data-warehouse)  
   
-    -   [sp_pdw_remove_network_credentials](https://msdn.microsoft.com/library/mt204038.aspx)  
+    -   [sp_pdw_remove_network_credentials](/sql-docs/docs/relational-databases/system-stored-procedures/sp-pdw-remove-network-credentials-sql-data-warehouse)  
   
 ## <a name="Step5"></a>Step 5: Start backing up your data  
 You are now ready to start backing up data to your backup server.  
@@ -117,9 +117,9 @@ FROM DISK = '\\10.172.14.255\backups\yearly\Invoices2013Full'
   
 For more information, see: 
   
--   [BACKUP DATABASE](https://msdn.microsoft.com/library/mt631607.aspx)   
+-   [BACKUP DATABASE](/sql-docs/docs/t-sql/statements/backup-database-parallel-data-warehouse)   
   
--   [RESTORE DATABASE](https://msdn.microsoft.com/library/mt631612.aspx)  
+-   [RESTORE DATABASE](/sql-docs/docs/t-sql/statements/restore-database-parallel-data-warehouse)  
   
 ## <a name="Security"></a>Security notices  
 The backup server is not joined to the private domain for the appliance. It is in your own network, and there is no trust relationship between your own domain and private appliance domain.  
@@ -133,11 +133,11 @@ Network access to the backup directory is based on standard Windows file sharing
 > [!IMPORTANT]  
 > To reduce security risks with your data, we advise that you designate one Windows account solely for the purpose of performing backup and restore operations. Allow this account to have permissions to the backup location and nowhere else.  
   
-To store the user name and password in PDW, use the [sp_pdw_add_network_credentials](https://msdn.microsoft.com/library/mt204011.aspx) stored procedure. PDW uses Windows Credential Manager to store and encrypt user names and passwords on the Control node and Compute nodes. The credentials are not backed up with the BACKUP DATABASE command.  
+To store the user name and password in PDW, use the [sp_pdw_add_network_credentials](/sql-docs/docs/relational-databases/system-stored-procedures/sp-pdw-add-network-credentials-sql-data-warehouse) stored procedure. PDW uses Windows Credential Manager to store and encrypt user names and passwords on the Control node and Compute nodes. The credentials are not backed up with the BACKUP DATABASE command.  
   
-To remove network credentials from PDW, use the [sp_pdw_remove_network_credentials](https://msdn.microsoft.com/library/mt204038.aspx) stored procedure.  
+To remove network credentials from PDW, use the [sp_pdw_remove_network_credentials](/sql-docs/docs/relational-databases/system-stored-procedures/sp-pdw-remove-network-credentials-sql-data-warehouse) stored procedure.  
   
-To list all of the network credentials stored in SQL Server PDW, use the [sys.dm_pdw_network_credentials](https://msdn.microsoft.com/library/mt203915.aspx) dynamic management view.  
+To list all of the network credentials stored in SQL Server PDW, use the [sys.dm_pdw_network_credentials](/sql-docs/docs/relational-databases/system-dynamic-management-views/sys-dm-pdw-network-credentials-transact-sql) dynamic management view.  
   
 ### Secure communications  
   

docs-msdn/analytics-platform-system/appliance-installation-and-configuration-overview.md

@@ -73,4 +73,4 @@ After you have completed all of the preceding steps, your appliance is ready for
 |Monitor queries and appliance users|Use the Admin Console and other resources to monitor the queries and appliance users. See [Monitor the Appliance by Using the Admin Console &#40;Analytics Platform System&#41;](monitor-the-appliance-by-using-the-admin-console.md)<!-- MISSING LINKS and [User Sessions &#40;SQL Server PDW&#41;](../sqlpdw/user-sessions-sql-server-pdw.md)-->.|  
 |Load data to SQL Server PDW|Load data to your appliance. <!-- MISSING LINKS See [Load &#40;SQL Server PDW&#41;](../sqlpdw/load-sql-server-pdw.md).-->|  
 |Create a disaster recovery plan|Plan how you will protect your data from hardware failures or data overwrites. Create a plan using regular backups and restore plans in case of data corruption or loss. <!-- MISSING LINKS See [Create a Disaster Recovery Plan &#40;SQL Server PDW&#41;](../sqlpdw/create-a-disaster-recovery-plan-sql-server-pdw.md).-->|  
-|Monitor the appliance|Monitor the appliance state, health, and performance by using system views, logs, and the Admin Console. Correct or report any problems. See [Monitor Appliance Health State &#40;Analytics Platform System&#41;](monitor-appliance-health-state.md) and [sys.dm_pdw_component_health_status](https://msdn.microsoft.com/library/mt631628.aspx).|  
+|Monitor the appliance|Monitor the appliance state, health, and performance by using system views, logs, and the Admin Console. Correct or report any problems. See [Monitor Appliance Health State &#40;Analytics Platform System&#41;](/sql-docs/docs/relational-databases/system-dynamic-management-views/sys-dm-pdw-component-health-status-transact-sql).|  

docs-msdn/analytics-platform-system/backup-and-restore-overview.md

@@ -19,7 +19,7 @@ Describes how data backup and restore works for SQL Server Parallel Data Warehou
 ## <a name="BackupRestoreBasics"></a>Backup and restore basics  
 A PDW *database backup* is a copy of an appliance database, stored in a format so that it can be used to restore the original database to an appliance.  
 
-A PDW database backup is created with the [BACKUP DATABASE](https://msdn.microsoft.com/library/mt631607.aspx) t-sql statement and formatted for use with the [RESTORE DATABASE](https://msdn.microsoft.com/library/mt631612.aspx) statement; it is unusable for any other purpose. The backup can only be restored to an appliance with the same number or a greater number of Compute nodes.  
+A PDW database backup is created with the [BACKUP DATABASE](/sql-docs/docs/t-sql/statements/backup-database-parallel-data-warehouse) t-sql statement and formatted for use with the [RESTORE DATABASE](/sql-docs/docs/t-sql/statements/restore-database-parallel-data-warehouse) statement; it is unusable for any other purpose. The backup can only be restored to an appliance with the same number or a greater number of Compute nodes.  
 
 <!-- MISSING LINKS
 
@@ -97,7 +97,7 @@ When restoring data, the appliance detects the number of Compute nodes on the so
 
 1.  The database backup to be restored is available on a Windows file share on a non-appliance backup server. For best performance, this server is usually connected to the appliance InfiniBand network.  
 
-2.  User submits a [RESTORE DATABASE](https://msdn.microsoft.com/library/mt631612.aspx) tsql statement to the Control node.  
+2.  User submits a [RESTORE DATABASE](/sql-docs/docs/t-sql/statements/restore-database-parallel-data-warehouse) tsql statement to the Control node.  
 
     -   The restore is either a full restore or a header restore. The full restore restores a full backup and then optionally restores a differential backup.  
 
@@ -119,15 +119,15 @@ Restoring a backup to an appliance with a larger number of Compute nodes grows t
 
 For example, when restoring a 60 GB database from a 2-node appliance (30 GB per node) to a 6-node appliance, SQL Server PDW creates a 180 GB database (6 nodes with 30 GB per node) on the 6-node appliance. SQL Server PDW initially restores the database to 2 nodes to match the source configuration, and then redistributes the data to all 6 nodes.  
 
-After the redistribution each Compute node will contain less actual data and more free space than each Compute node on the smaller source appliance. Use the additional space to add more data to the database. If the restored database size is larger than you need, you can use [ALTER DATABASE](https://msdn.microsoft.com/library/mt631606.aspx) to shrink the database file sizes.  
+After the redistribution each Compute node will contain less actual data and more free space than each Compute node on the smaller source appliance. Use the additional space to add more data to the database. If the restored database size is larger than you need, you can use [ALTER DATABASE](/sql-docs/docs/t-sql/statements/alter-database-parallel-data-warehouse) to shrink the database file sizes.  
 
 ## Related Tasks  
 
 |Backup and Restore Task|Description|  
 |---------------------------|---------------|  
 |Prepare a server as a backup server.|[Acquire and configure a backup server ](acquire-and-configure-backup-server.md)|  
-|Backup a database.|[BACKUP DATABASE](https://msdn.microsoft.com/library/mt631607.aspx)|  
-|Restore a database.|[RESTORE DATABASE](https://msdn.microsoft.com/library/mt631612.aspx)|  
+|Backup a database.|[BACKUP DATABASE](/sql-docs/docs/t-sql/statements/backup-database-parallel-data-warehouse)|  
+|Restore a database.|[RESTORE DATABASE](/sql-docs/docs/t-sql/statements/restore-database-parallel-data-warehouse)|  
 
 
 

docs-msdn/analytics-platform-system/configure-an-external-smp-sql-server-to-receive-remote-table-copies.md

@@ -42,7 +42,7 @@ To configure SQL Server, use the following steps:
 ## <a name="BPSQLConfig"></a>Best Practices for SMP SQL Server Configuration for Remote Table Copy  
 When configuring the SMP SQL Server to receive remote table copies, use the following best practices to improve performance.  
 
-1.  Follow best practices as documented in SQL Server product documentation. For example, enable data encryption. For more information about securing SQL Server, see [Securing SQL Server](https://msdn.microsoft.com/library/bb283235.aspx) on MSDN.  
+1.  Follow best practices as documented in SQL Server product documentation. For example, enable data encryption. For more information about securing SQL Server, see [Securing SQL Server](/sql-docs/docs/relational-databases/security/securing-sql-server) on MSDN.  
 
 2.  Use the bulk-logged or simple recovery model.  
 

docs-msdn/analytics-platform-system/configure-polybase-connectivity-to-external-data.md

@@ -19,7 +19,7 @@ Explains how to configure PolyBase in SQL Server PDW to connect to external Hado
 
     ![hadoop connectivity setting](./media/configure-polybase-connectivity-to-external-data/APS_PDW_sp_configure.png "APS_PDW_sp_configure")  
 
-2.  Decide which Hadoop connectivity setting you need and whether you need to change the current setting. This option applies to the entire SQL Server PDW region. For a full list of the configuration settings and versions, see [sp_configure](https://msdn.microsoft.com/library/ms188787.aspx).  
+2.  Decide which Hadoop connectivity setting you need and whether you need to change the current setting. This option applies to the entire SQL Server PDW region. For a full list of the configuration settings and versions, see [sp_configure](/sql-docs/docs/relational-databases/system-stored-procedures/sp-configure-transact-sql).  
 
 3.  To change the 'hadoop connectivity' setting, run sp_configure with RECONFIGURE. Here are some examples.  
 

docs-msdn/analytics-platform-system/determine-which-cluster-node-failed.md

@@ -25,7 +25,7 @@ After a cluster failover, when SQL Server PDW reports on node status, the passiv
 1.  Open the Admin Console. For more information about the Admin Console, see [Monitor the Appliance by Using the Admin Console (Analytics Platform System)](monitor-the-appliance-by-using-the-admin-console.md). After failover occurs, the failover event is included in the number of alerts on the **HEALTH** page. There is an **HEALTH** page for the PDW region, the HDI region, and for the fabric region of the appliance. Each Health page has an **ALERTS** tab. To learn more about an alert, click the Health page, the Alerts tab, and then click an alert.  
 
 ## <a name="SystemView"></a>System View Solution  
-The following SQL statement shows how to use the [sys.dm_pdw_component_health_active_alerts](https://msdn.microsoft.com/library/mt631630.aspx) system view to find the name of the server that failed.  
+The following SQL statement shows how to use the [sys.dm_pdw_component_health_active_alerts](/sql-docs/docs/relational-databases/system-dynamic-management-views/sys-dm-pdw-component-health-active-alerts-transact-sql) system view to find the name of the server that failed.  
 
 ```  
 SELECT  

docs-msdn/analytics-platform-system/dwloader-data-type-conversion-rules.md

@@ -134,7 +134,7 @@ The following table defines the rules for loading literal values into a column o
 |Decimal literal|123344.34455|  
 
 ### float and real Data Types  
-The following table defines rules for loading literal values into a column of type **float** or **real**. Data conversion rules are the same as for SQL Server. For more information, see [Data Type Conversion (Database Engine)](https://msdn.microsoft.com/library/ms191530.aspx) on MSDN.  
+The following table defines rules for loading literal values into a column of type **float** or **real**. Data conversion rules are the same as for SQL Server. For more information, see [Data Type Conversion (Database Engine)](/sql-docs/docs/t-sql/data-types/data-type-conversion-database-engine) on MSDN.  
 
 |Input Data Type|Input Data Examples|  
 |-------------------|-----------------------|  

docs-msdn/analytics-platform-system/dwloader.md

@@ -519,7 +519,7 @@ Loaded data might require more or less space on the appliance than in the source
 Although **dwloader** is a transaction process and will roll back gracefully on failure, it cannot be rolled back once the bulk load has been completed successfully. To cancel an active **dwloader** process, type CTRL+C.  
 
 ## Limitations and Restrictions  
-The total size of all loads occurring concurrently must be smaller than LOG_SIZE for the database, and we recommend the total size of all concurrent loads is less than 50% of the LOG_SIZE. To achieve this size limitation, you can split large loads  into multiple batches. For more information on LOG_SIZE, see [CREATE DATABASE](https://msdn.microsoft.com/library/mt631608.aspx)  
+The total size of all loads occurring concurrently must be smaller than LOG_SIZE for the database, and we recommend the total size of all concurrent loads is less than 50% of the LOG_SIZE. To achieve this size limitation, you can split large loads  into multiple batches. For more information on LOG_SIZE, see [CREATE DATABASE](/sql-docs/docs/t-sql/statements/create-database-parallel-data-warehouse)  
 
 When loading multiple files with one load command, all rejected rows are written to the same reject file. The reject file does not show which input file contains each rejected row.  
 

docs-msdn/analytics-platform-system/grant-permissions.md

@@ -141,7 +141,7 @@ This section describes how to grant permissions to manage logins, database users
 ### <a name="PermsAdminConsole"></a>Grant Permissions to Manage Logins  
 **Add or Manage Logins**  
 
-The following SQL statements create a Login named KimAbercrombie  that can create new logins by using the [CREATE LOGIN](https://msdn.microsoft.com/library/ms189751.aspx) statement and alter existing logins by using the [ALTER LOGIN](https://msdn.microsoft.com/library/ms189828.aspx) statement.  
+The following SQL statements create a Login named KimAbercrombie  that can create new logins by using the [CREATE LOGIN](/sql-docs/docs/t-sql/statements/create-login-transact-sql) statement and alter existing logins by using the [ALTER LOGIN](/sql-docs/docs/t-sql/statements/alter-login-transact-sql) statement.  
 
 The **ALTER ANY LOGIN** permission grants the ability to create new logins and drop exisiting. Once a login exists, the login can be managed by logins with the **ALTER ANY LOGIN** permission or the **ALTER** permission on that login. A login can change the password and default database for its own login.  
 
@@ -238,7 +238,7 @@ GO
 To create admin logins, see [Fixed Server Roles](pdw-permissions.md#fixed-server-roles).  
 
 ## See also
-[CREATE LOGIN](https://msdn.microsoft.com/library/ms189751.aspx)  
-[CREATE USER](https://msdn.microsoft.com/library/ms173463.aspx)  
-[CREATE ROLE](https://msdn.microsoft.com/library/ms187936.aspx)  
+[CREATE LOGIN](/sql-docs/docs/t-sql/statements/create-login-transact-sql)  
+[CREATE USER](/sql-docs/docs/t-sql/statements/create-user-transact-sql)  
+[CREATE ROLE](/sql-docs/docs/t-sql/statements/create-role-transact-sql)  
 [Load](load-overview.md)