Merge pull request MicrosoftDocs#6090 from TwoUnder/master

Updating some T-SQL coverage for SQL DW

Author: PRMerger20

docs/relational-databases/system-catalog-views/sys-pdw-table-mappings-transact-sql.md

@@ -1,7 +1,7 @@
 ---
 title: "sys.pdw_table_mappings (Transact-SQL) | Microsoft Docs"
 ms.custom: ""
-ms.date: "03/03/2017"
+ms.date: "06/01/2018"
 ms.prod: ""
 ms.prod_service: "sql-data-warehouse, pdw"
 ms.service: "sql-data-warehouse"
@@ -18,10 +18,10 @@ caps.latest.revision: 7
 author: ronortloff
 ms.author: rortloff
 manager: craigg
-monikerRange: ">= aps-pdw-2016 || = azure-sqldw-latest || = sqlallproducts-allversions"
+monikerRange: ">= aps-pdw-2016 || = sqlallproducts-allversions"
 ---
 # sys.pdw_table_mappings (Transact-SQL)
-[!INCLUDE[tsql-appliesto-xxxxxx-xxxx-asdw-pdw-md](../../includes/tsql-appliesto-xxxxxx-xxxx-asdw-pdw-md.md)]
+[!INCLUDE[tsql-appliesto-xxxxxx-xxxx-xxxx-pdw-md](../../includes/tsql-appliesto-xxxxxx-xxxx-xxxx-pdw-md.md)]
 
   Ties user tables to internal object names by **object_id**.  
 

docs/t-sql/statements/alter-database-transact-sql-set-options.md

@@ -2,7 +2,7 @@
 title: "ALTER DATABASE SET Options (Transact-SQL) | Microsoft Docs"
 description: Learn about how to set database options such as automatic tuning, encryption, query store in a SQL Server and Azure SQL Database
 ms.custom: ""
-ms.date: "12/20/2017"
+ms.date: "6/01/2018"
 ms.prod: sql
 ms.prod_service: "database-engine, sql-database"
 ms.component: "t-sql|statements"
@@ -35,9 +35,9 @@ ms.author: edmaca
 manager: craigg
 ---
 # ALTER DATABASE SET Options (Transact-SQL) 
-[!INCLUDE[tsql-appliesto-ss2008-asdb-xxxx-xxx-md](../../includes/tsql-appliesto-ss2008-asdb-xxxx-xxx-md.md)]
+[!INCLUDE[tsql-appliesto-ss2008-asdb-asdw-xxx-md](../../includes/tsql-appliesto-ss2008-asdb-asdw-xxx-md.md)]
 
-  This topic contains the ALTER DATABASE syntax that is related to setting database options in [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)]. For other ALTER DATABASE syntax, see the following topics.  
+  This article contains the ALTER DATABASE syntax that is related to setting database options in [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)]. For other ALTER DATABASE syntax, see the following topics.  
 
 -   [ALTER DATABASE (Transact-SQL)](../../t-sql/statements/alter-database-transact-sql.md)  
 
@@ -269,7 +269,7 @@ SET
 
  `CURRENT` performs the action in the current database. `CURRENT` is not supported for all options in all contexts. If `CURRENT` fails, provide the database name.  
 
- **\<auto_option> ::=**  
+ **\<auto_option> ::=**
 
  Controls automatic options.  
  <a name="auto_close"></a> AUTO_CLOSE { ON | OFF }  
@@ -433,7 +433,7 @@ SET
  OFF  
  Cursors remain open when a transaction is committed; rolling back a transaction closes any cursors except those defined as INSENSITIVE or STATIC.  
 
- Connection-level settings that are set by using the SET statement override the default database setting for CURSOR_CLOSE_ON_COMMIT. By default, ODBC and OLE DB clients issue a connection-level SET statement setting CURSOR_CLOSE_ON_COMMIT to OFF for the session when connecting to an instance of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)]. For more information, see [SET CURSOR_CLOSE_ON_COMMIT &#40;Transact-SQL&#41;](../../t-sql/statements/set-cursor-close-on-commit-transact-sql.md).  
+ Connection-level settings that are set by using the SET statement override the default database setting for CURSOR_CLOSE_ON_COMMIT. By default, ODBC, and OLE DB clients issue a connection-level SET statement setting CURSOR_CLOSE_ON_COMMIT to OFF for the session when connecting to an instance of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)]. For more information, see [SET CURSOR_CLOSE_ON_COMMIT &#40;Transact-SQL&#41;](../../t-sql/statements/set-cursor-close-on-commit-transact-sql.md).  
 
  The status of this option can be determined by examining the is_cursor_close_on_commit_on column in the sys.databases catalog view or the IsCloseCursorsOnCommitEnabled property of the DATABASEPROPERTYEX function.  
 
@@ -533,7 +533,7 @@ SET
  SINGLE_USER  
  **Applies to**: [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)]. Not available in [!INCLUDE[ssSDS](../../includes/sssds-md.md)].  
 
- Specifies that only one user at a time can access the database. If SINGLE_USER is specified and there are other users connected to the database the ALTER DATABASE statement will be blocked until all users disconnect from the specified database. To override this behavior, see the WITH \<termination> clause.  
+ Specifies that only one user at a time can access the database. If SINGLE_USER is specified and there are other users connected to the database, the ALTER DATABASE statement will be blocked until all users disconnect from the specified database. To override this behavior, see the WITH \<termination> clause.  
 
  The database remains in SINGLE_USER mode even if the user that set the option logs off. At that point, a different user, but only one, can connect to the database.  
 

docs/t-sql/statements/alter-table-transact-sql.md

@@ -313,15 +313,15 @@ ALTER TABLE [ database_name . [schema_name ] . | schema_name. ] source_table_nam
 
 -   Associated with a default definition. However, the length, precision, or scale of a column can be changed if the data type is not changed.  
 
-The data type of **text**, **ntext** and **image** columns can be changed only in the following ways:  
+The data type of **text**, **ntext, and **image** columns can be changed only in the following ways:  
 
 -   **text** to **varchar(max)**, **nvarchar(max)**, or **xml**  
 
 -   **ntext** to **varchar(max)**, **nvarchar(max)**, or **xml**  
 
 -   **image** to **varbinary(max)**  
 
-Some data type changes may cause a change in the data. For example, changing an **nchar** or **nvarchar** column to **char** or **varchar** may cause the conversion of extended characters. For more information, see [CAST and CONVERT (Transact-SQL)](../../t-sql/functions/cast-and-convert-transact-sql.md). Reducing the precision or scale of a column may cause data truncation.  
+Some data type changes may cause a change in the data. For example, changing a nchar** or **nvarchar** column to **char** or **varchar** may cause the conversion of extended characters. For more information, see [CAST and CONVERT (Transact-SQL)](../../t-sql/functions/cast-and-convert-transact-sql.md). Reducing the precision or scale of a column may cause data truncation.  
 
 > [!NOTE]
 > The data type of a column of a partitioned table cannot be changed.