fixed links from previous commit

Author: mikeblome

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](/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.
+For local backups, SQL Database uses SQL Server technology to create [full](../../docs/relational-databases/backup-restore/full-database-backups-sql-server.md), [differential](../../docs/relational-databases/backup-restore/differential-backups-sql-server.md) 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](/sql-docs/docs/relational-databases/backup-restore/differential-backups-sql-server) 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](../../docs/relational-databases/backup-restore/differential-backups-sql-server.md) 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

@@ -117,9 +117,9 @@ FROM DISK = '\\10.172.14.255\backups\yearly\Invoices2013Full'
   
 For more information, see: 
   
--   [BACKUP DATABASE](/sql-docs/docs/t-sql/statements/backup-database-parallel-data-warehouse)   
+-   [BACKUP DATABASE](../../docs/t-sql/statements/backup-database-parallel-data-warehouse.md)   
   
--   [RESTORE DATABASE](/sql-docs/docs/t-sql/statements/restore-database-parallel-data-warehouse)  
+-   [RESTORE DATABASE](../../docs/t-sql/statements/restore-database-parallel-data-warehouse.md)  
   
 ## <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.  

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](/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.  
+A PDW database backup is created with the [BACKUP DATABASE](../../docs/t-sql/statements/backup-database-parallel-data-warehouse.md) t-sql statement and formatted for use with the [RESTORE DATABASE](../../docs/t-sql/statements/restore-database-parallel-data-warehouse.md) 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](/sql-docs/docs/t-sql/statements/restore-database-parallel-data-warehouse) tsql statement to the Control node.  
+2.  User submits a [RESTORE DATABASE](../../docs/t-sql/statements/restore-database-parallel-data-warehouse.md) 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](/sql-docs/docs/t-sql/statements/alter-database-parallel-data-warehouse) 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](../../docs/t-sql/statements/alter-database-parallel-data-warehouse.md) 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](/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)|  
+|Backup a database.|[BACKUP DATABASE](../../docs/t-sql/statements/backup-database-parallel-data-warehouse.md)|  
+|Restore a database.|[RESTORE DATABASE](../../docs/t-sql/statements/restore-database-parallel-data-warehouse.md)|  
 
 
 

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](/sql-docs/docs/relational-databases/security/securing-sql-server) 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](../../docs/relational-databases/security/securing-sql-server.md) on MSDN.  
 
 2.  Use the bulk-logged or simple recovery model.  
 

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](/sql-docs/docs/t-sql/statements/create-database-parallel-data-warehouse)  
+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](../../docs/t-sql/statements/create-database-parallel-data-warehouse.md)  
 
 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](/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 following SQL statements create a Login named KimAbercrombie  that can create new logins by using the [CREATE LOGIN](../../docs/t-sql/statements/create-login-transact-sql.md) statement and alter existing logins by using the [ALTER LOGIN](../../docs/t-sql/statements/alter-login-transact-sql.md) 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](/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)  
+[CREATE LOGIN](../../docs/t-sql/statements/create-login-transact-sql.md)  
+[CREATE USER](../../docs/t-sql/statements/create-user-transact-sql.md)  
+[CREATE ROLE](../../docs/t-sql/statements/create-role-transact-sql.md)  
 [Load](load-overview.md)  

docs-msdn/analytics-platform-system/instant-file-initialization-configuration.md

@@ -19,7 +19,7 @@ Instant file initialization is a SQL Server feature that allows data file operat
 Instant file initialization is not available when TDE is enabled.  
 
 ## Add Permission for the Backup Account  
-The backup process requires a network credential (Windows user account) that can access the backup storage location. You authorize PDW to use account by using the [sp_pdw_add_network_credentials](/sql-docs/docs/relational-databases/system-stored-procedures/sp-pdw-add-network-credentials-sql-data-warehouse) procedure. See [BACKUP DATABASE](/sql-docs/docs/t-sql/statements/backup-database-parallel-data-warehouse) for the entire backup process. To use instant file initialization, the backup account must be granted the `Perform volume maintenance tasks` permission.  
+The backup process requires a network credential (Windows user account) that can access the backup storage location. You authorize PDW to use account by using the [sp_pdw_add_network_credentials](/sql-docs/docs/relational-databases/system-stored-procedures/sp-pdw-add-network-credentials-sql-data-warehouse) procedure. See [BACKUP DATABASE](../../docs/t-sql/statements/backup-database-parallel-data-warehouse.md) for the entire backup process. To use instant file initialization, the backup account must be granted the `Perform volume maintenance tasks` permission.  
 
 1.  On the backup server, open the **Local Security Policy** application (`secpol.msc`).  
 

docs-msdn/analytics-platform-system/load-overview.md

@@ -14,7 +14,7 @@ caps.latest.revision: 22
 ---
 
 # Load (SQL Server PDW)
-You can load or insert data into SQL Server Parallel Data Warehouse (PDW) by using Integration Services, [bcp Utility](/sql-docs/docs/tools/bcp-utility), **dwloader** Command-line Loader, or the SQL INSERT statement.  
+You can load or insert data into SQL Server Parallel Data Warehouse (PDW) by using Integration Services, [bcp Utility](../../docs/tools/bcp-utility.md), **dwloader** Command-line Loader, or the SQL INSERT statement.  
 
 ## Loading Environment  
 To load data, you need one or more loading servers. You can use your own existing ETL or other servers, or you can purchase new servers. For more information, see [Acquire and Configure a Loading Server](acquire-and-configure-loading-server.md). These instructions include a [Loading Server Capacity Planning Worksheet](loading-server-capacity-planning-worksheet.md) to help you plan the right solution for loading.  

docs-msdn/analytics-platform-system/load-with-insert.md

@@ -16,7 +16,7 @@ author: BarbKess
 
 # Load data with INSERT
 
-You can use the tsql INSERT statement to load data into a SQL Server Parallel Data Warehouse (PDW) distributed or replicated table. For more information about INSERT, see [INSERT](/sql-docs/docs/t-sql/statements/insert-transact-sql). For replicated tables and all non-distribution columns in a distributed table, PDW uses SQL Server to implicitly convert the data values specified in the statement to the data type of the destination column. For more information about SQL Server data conversion rules, see [Data type conversion for SQL](http://msdn.microsoft.com/library/ms191530(v=sql11(.aspx). However, for distribution columns, PDW supports only a subset of implicit conversions that SQL Server supports. Therefore, when you use the INSERT statement to load data into a distribution column, the source data must be specified in one of the formats defined in the following tables.  
+You can use the tsql INSERT statement to load data into a SQL Server Parallel Data Warehouse (PDW) distributed or replicated table. For more information about INSERT, see [INSERT](../../docs/t-sql/statements/insert-transact-sql.md). For replicated tables and all non-distribution columns in a distributed table, PDW uses SQL Server to implicitly convert the data values specified in the statement to the data type of the destination column. For more information about SQL Server data conversion rules, see [Data type conversion for SQL](http://msdn.microsoft.com/library/ms191530(v=sql11(.aspx). However, for distribution columns, PDW supports only a subset of implicit conversions that SQL Server supports. Therefore, when you use the INSERT statement to load data into a distribution column, the source data must be specified in one of the formats defined in the following tables.  
 
 
 ## <a name="InsertingLiteralsBinary"></a>Insert literals into binary types  
@@ -156,7 +156,7 @@ The following table defines the accepted formats and rules for inserting literal
 ## See Also  
 
 [Distributed data](https://azure.microsoft.com/documentation/articles/sql-data-warehouse-distributed-data/)  
-[INSERT](/sql-docs/docs/t-sql/statements/insert-transact-sql)  
+[INSERT](../../docs/t-sql/statements/insert-transact-sql.md)  
 
 <!-- MISSING LINKS
 [Grant permissions to load data](grant-permissions-to-load-data.md)  

docs-msdn/analytics-platform-system/master-database.md

@@ -38,7 +38,7 @@ You *cannot:*
 
 |Task|Description|  
 |--------|---------------|  
-|Create a full backup of master.|Example:<br /><br />`BACKUP DATABASE master TO backup_directory;`<br /><br />For more information, see [BACKUP DATABASE](/sql-docs/docs/t-sql/statements/backup-database-parallel-data-warehouse).|  
+|Create a full backup of master.|Example:<br /><br />`BACKUP DATABASE master TO backup_directory;`<br /><br />For more information, see [BACKUP DATABASE](../../docs/t-sql/statements/backup-database-parallel-data-warehouse.md).|  
 |Restore the master database|To restore the master database, use the [Restore the Master Database](restore-the-master-database.md) page in the Configuration Manager tool.|  
 |View database catalog information.|`SELECT * FROM master.sys.databases;`|  
 |View system-wide login and permission information.|`SELECT * FROM master.sys.server_permissions;`<br /><br />`SELECT * FROM master.sys.server_principals;`<br /><br />`SELECT * FROM master.sys.sql_logins;`|