Merge pull request #6703 from mzaman1/apsau7

changed link to alter-database on all docs

Author: PRMerger14

docs/analytics-platform-system/appliance-feature-switch.md

@@ -17,7 +17,7 @@ The **Feature Switch** page displays information about the two feature switches
 ![DWConig Appliance Feature Switch](media/feature-switch/SQL_Server_PDW_DWConfig_feature_switch.png "DWConig Appliance Feature Switch") 
 
 ##AutoStatsEnabled Switch
-Controls the auto statistics feature. This feature switch is set to true by default after upgrading to AU7. Any database created after the upgrade will inherit auto creation and asynchronous update of statistics. For existing databases, database administrators can enable auto statistics with [alter database] (/sql/t-sql/statements/alter-database-parallel-data-warehouse). For more information on statistics, see [Statistics](../relational-databases/statistics/statistics.md).
+Controls the auto statistics feature. This feature switch is set to true by default after upgrading to AU7. Any database created after the upgrade will inherit auto creation and asynchronous update of statistics. For existing databases, database administrators can enable auto statistics with [ALTER DATABASE (Parallel Data Warehouse)](../t-sql/statements/alter-database-transact-sql.md?tabs=sqlpdw). For more information on statistics, see [Statistics](../relational-databases/statistics/statistics.md).
 
 ##DmsProcessStopMessageTimeoutInSeconds Switch
 Controls the time Data Movement Service (DMS) waits to synchronize on a busy system when a query involving data movement is cancelled. Updating to AU7 sets this value to 900 seconds (15 minutes) by default. The valid range is 0 – 3600 seconds.

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

@@ -93,7 +93,7 @@ The following diagram shows the flow of data during a database restore.
 
 When restoring data, the appliance detects the number of Compute nodes on the source appliance and the destination appliance. If both appliances have an equal number of Compute nodes, the restore process works as follows:  
 
-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.  
+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 connected to the appliance InfiniBand network.  
 
 2.  User submits a [RESTORE DATABASE](../t-sql/statements/restore-database-parallel-data-warehouse.md) tsql statement to the Control node.  
 
@@ -115,9 +115,9 @@ When restoring data, the appliance detects the number of Compute nodes on the so
 
 Restoring a backup to an appliance with a larger number of Compute nodes grows the allocated database size in proportion to the number of Compute nodes.  
 
-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.  
+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](../t-sql/statements/alter-database-parallel-data-warehouse.md) 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](../t-sql/statements/alter-database-transact-sql.md?tabs=sqlpdw) to shrink the database file sizes.  
 
 ## Related Tasks  
 

docs/analytics-platform-system/configure-auto-statistics.md

@@ -39,7 +39,7 @@ After upgrading to APS AU7, auto statistics is enabled by default. The system ad
 Changing any feature switch values requires a service restart on APS.
 
 ## Change auto statistics settings on a database
-When auto statistics is enabled by the system administrator, you can use [ALTER DATABASE (Parallel Data Warehouse)](/sql/t-sql/statements/alter-database-parallel-data-warehouse) to change the statistics settings on a database. If auto statistics feature switch is enabled by the system administrator, any new databases created after the upgrade to AU7 will have auto statistics enabled. All databases that existed before the upgrade to AU7 have auto statistics disabled. 
+When auto statistics is enabled by the system administrator, you can use [ALTER DATABASE (Parallel Data Warehouse)](../t-sql/statements/alter-database-transact-sql.md?tabs=sqlpdw) to change the statistics settings on a database. If auto statistics feature switch is enabled by the system administrator, any new databases created after the upgrade to AU7 will have auto statistics enabled. All databases that existed before the upgrade to AU7 have auto statistics disabled. 
 The following example enables auto statistics on the existing database myPDW.
 
 ```sql

docs/analytics-platform-system/staging-database.md

@@ -46,7 +46,7 @@ For more information, see [Grant Permissions to load data](grant-permissions-to-
 
 1.  There should only be one staging database per appliance. The staging database can be shared by all load jobs for all destination databases.  
 
-2.  The size of the staging database is customer-specific. Initially, when first populating the appliance, the staging database should be large enough to accommodate the initial load jobs. These load jobs tend to be large because multiple loads can occur concurrently. After initial load jobs have completed and the system is in production, the size of each load job is likely to be smaller. When loads are small, you can reduce the size of the staging database to accommodate the smaller load sizes. To reduce the size, you can drop the staging database and create it again with smaller size allocations, or you can use the [ALTER DATABASE](../t-sql/statements/alter-database-parallel-data-warehouse.md) statement.  
+2.  The size of the staging database is customer-specific. Initially, when first populating the appliance, the staging database should be large enough to accommodate the initial load jobs. These load jobs tend to be large because multiple loads can occur concurrently. After initial load jobs have completed and the system is in production, the size of each load job is likely to be smaller. When loads are small, you can reduce the size of the staging database to accommodate the smaller load sizes. To reduce the size, you can drop the staging database and create it again with smaller size allocations, or you can use the [ALTER DATABASE](../t-sql/statements/alter-database-transact-sql.md?tabs=sqlpdw) statement.  
 
     When creating the staging database, use the following guidelines.  
 

docs/analytics-platform-system/transparent-data-encryption.md

@@ -118,7 +118,7 @@ The following table provides links and explanations of TDE commands and function
 |[CREATE DATABASE ENCRYPTION KEY](../t-sql/statements/create-database-encryption-key-transact-sql.md)|Creates a key that is used to encrypt a database.|  
 |[ALTER DATABASE ENCRYPTION KEY](../t-sql/statements/alter-database-encryption-key-transact-sql.md)|Changes the key that is used to encrypt a database.|  
 |[DROP DATABASE ENCRYPTION KEY](../t-sql/statements/drop-database-encryption-key-transact-sql.md)|Removes the key that was used to encrypt a database.|  
-|[ALTER DATABASE](../t-sql/statements/alter-database-parallel-data-warehouse.md)|Explains the **ALTER DATABASE** option that is used to enable TDE.|  
+|[ALTER DATABASE](../t-sql/statements/alter-database-transact-sql.md?tabs=sqlpdw)|Explains the **ALTER DATABASE** option that is used to enable TDE.|  
 
 ## Catalog Views and Dynamic Management Views  
 The following table shows TDE catalog views and dynamic management views.  
@@ -273,7 +273,7 @@ The following links contain general information about how SQL Server manages enc
 
 
 ## See Also  
-[ALTER DATABASE](../t-sql/statements/alter-database-parallel-data-warehouse.md)  
+[ALTER DATABASE](../t-sql/statements/alter-database-transact-sql.md?tabs=sqlpdw)  
 [CREATE MASTER KEY](../t-sql/statements/create-master-key-transact-sql.md)  
 [CREATE DATABASE ENCRYPTION KEY](../t-sql/statements/create-database-encryption-key-transact-sql.md)  
 [BACKUP CERTIFICATE](../t-sql/statements/backup-certificate-transact-sql.md)  

docs/analytics-platform-system/tsql-statements.md

@@ -15,7 +15,7 @@ ms.reviewer: martinle
 Transact-SQL (T-SQL) statements for Analytic Platform System (APS) SQL Server Parallel Data Warehouse (PDW).
 
 ## Data Definition Language (DDL) statements
-* [ALTER DATABASE](../t-sql/statements/alter-database-azure-sql-data-warehouse.md)
+* [ALTER DATABASE](../t-sql/statements/alter-database-transact-sql.md?tabs=sqlpdw)
 * [ALTER INDEX](../t-sql/statements/alter-index-transact-sql.md)
 * [ALTER PROCEDURE](../t-sql/statements/alter-procedure-transact-sql.md)
 * [ALTER SCHEMA](../t-sql/statements/alter-schema-transact-sql.md)

docs/analytics-platform-system/whats-new-analytics-platform-system.md

@@ -19,7 +19,7 @@ See what’s new in the latest Appliance Updates for Microsoft® Analytics Platf
 APS 2016 is a prerequisite to upgrade to AU7. The following are new in APS AU7:
 
 ### Auto-create and auto-update statistics
-APS AU7 creates and updates statistics automatically, by default. To update statistics settings, administrators can use a new feature switch menu item in the [Configuration Manager](appliance-configuration.md#CMTasks). The [feature switch](appliance-feature-switch.md) controls the auto-create, auto-update, and asynchronous update behavior of statistics. You can also update statistics settings with the [ALTER DATABASE (Parallel Data Warehouse)](/sql/t-sql/statements/alter-database-parallel-data-warehouse) statement.
+APS AU7 creates and updates statistics automatically, by default. To update statistics settings, administrators can use a new feature switch menu item in the [Configuration Manager](appliance-configuration.md#CMTasks). The [feature switch](appliance-feature-switch.md) controls the auto-create, auto-update, and asynchronous update behavior of statistics. You can also update statistics settings with the [ALTER DATABASE (Parallel Data Warehouse)](../t-sql/statements/alter-database-transact-sql.md?tabs=sqlpdw) statement.
 
 ### T-SQL
 Select @var is now supported. For more information, see [select local variable] (/sql/t-sql/language-elements/select-local-variable-transact-sql)