Merge pull request MicrosoftDocs#2466 from barbkess/wp2

fix syntax bug

Author: PRMerger9

docs/relational-databases/polybase/polybase-t-sql-objects.md

@@ -2,7 +2,7 @@
 title: "PolyBase T-SQL objects | Microsoft Docs"
 ms.custom: 
   - "SQL2016_New_Updated"
-ms.date: "03/08/2016"
+ms.date: "07/13/2017"
 ms.prod: "sql-server-2016"
 ms.reviewer: ""
 ms.suite: ""
@@ -21,7 +21,7 @@ ms.author: "barbkess"
 manager: "jhubbard"
 ---
 # PolyBase T-SQL objects
-[!INCLUDE[tsql-appliesto-ss2016-xxxx-xxxx-xxx_md](../../includes/tsql-appliesto-ss2016-xxxx-xxxx-xxx-md.md)]
+[!INCLUDE[tsql-appliesto-ss2016-xxxx-asdw-pdw_md](../../includes/tsql-appliesto-ss2016-xxxx-asdw-pdw-md.md)]
 
   To use  PolyBase, you must create external tables to reference your external data.  
 

docs/relational-databases/system-dynamic-management-views/sys-dm-db-column-store-row-group-physical-stats-transact-sql.md

@@ -44,10 +44,10 @@ manager: "jhubbard"
 |**total_rows**|**bigint**|Number of rows physical stored in the row group. For compressed row groups, this includes the rows that are marked deleted.|  
 |**deleted_rows**|**bigint**|Number of rows physically stored in a compressed row group that are marked for deletion.<br /><br /> 0 for row groups that are in the delta store.|  
 |**size_in_bytes**|**bigint**|Combined size, in bytes, of all the pages in this row group. This size does not include the size required to store metadata or shared dictionaries.|  
-|**transition_to_compressed_state**|tinyint|Shows how this rowgroup got moved from the deltastore to a compressed state in the columnstore.<br /><br /> 1- NOT_APPLICABLE<br /><br /> 2 – INDEX_BUILD<br /><br /> 3 – TUPLE_MOVER<br /><br /> 4 – REORG_NORMAL<br /><br /> 5 – REORG_FORCED<br /><br /> 6 - BULKLOAD<br /><br /> 7 - MERGE|  
-|**transition_to_compressed_state_desc**|nvarchar(60)|NOT_APPLICABLE – the operation does not apply to the deltastore. Or, the rowgroup was compressed prior to upgrading to [!INCLUDE[ssSQL15](../../includes/sssql15-md.md)] in which case the history is not preserved.<br /><br /> INDEX_BUILD – An index create or index rebuild compressed the rowgroup.<br /><br /> TUPLE_MOVER – The tuple mover running in the background compressed the rowgroup. This happens after the rowgroup changes state from OPEN to CLOSED.<br /><br /> REORG_NORMAL – The reorganization operation, ALTER INDEX … REORG, moved the CLOSED rowgroup from the deltastore to the columnstore. This occurred before the tuple-mover had time to move the rowgroup.<br /><br /> REORG_FORCED – This rowgroup was open in the deltastore and was forced into the columnstore before it had a full number of rows.<br /><br /> BULKLOAD – A bulk load operation compressed the rowgroup directly without using the deltastore.<br /><br /> MERGE – A merge operation consolidated one or more rowgroups into this rowgroup and then performed the columnstore compression.|  
 |**trim_reason**|**tinyint**|Reason that triggered the COMPRESSED row group to have less than the maximum number of rows.<br /><br /> 0 – UNKNOWN_UPGRADED_FROM_PREVIOUS_VERSION<br /><br /> 1 - NO_TRIM<br /><br /> 2 - BULKLOAD<br /><br /> 3 – REORG<br /><br /> 4 – DICTIONARY_SIZE<br /><br /> 5 – MEMORY_LIMITATION<br /><br /> 6 – RESIDUAL_ROW_GROUP<br /><br /> 7  -  STATS_MISMATCH<br /><br /> 8 - SPILLOVER|  
 |**trim_reason_desc**|**nvarchar(60)**|Description of *trim_reason*.<br /><br /> 0 – UNKNOWN_UPGRADED_FROM_PREVIOUS_VERSION: Occurred when upgrading from the previous version of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)].<br /><br /> 1 - NO_TRIM: The row group was not trimmed. The row group was compressed with the maximum of 1,048,476 rows.  The number of rows could be less if a subsset of rows was deleted after delta rowgroup was closed<br /><br /> 2 – BULKLOAD: The bulk load batch size limited the number of rows.<br /><br /> 3 – REORG:  Forced compression as part of REORG command.<br /><br /> 4 – DICTIONARY_SIZE: Dictionary size grew too big to compress all of the rows together.<br /><br /> 5 – MEMORY_LIMITATION: Not enough available memory to compress all the rows together.<br /><br /> 6 – RESIDUAL_ROW_GROUP:  Closed as part of last row group with rows < 1 million during index build operation<br /><br /> STATS_MISMATCH: Only for columnstore on in-memory table. If stats incorrectly indicated >= 1 million qualified rows in the tail but we found fewer, the compressed rowgroup will have < 1 million rows<br /><br /> SPILLOVER: Only for columnstore on in-memory table. If tail has > 1 million qualified rows, the last batch remaining rows are compressed if the count is between 100k and 1 million|  
+|**transition_to_compressed_state**|tinyint|Shows how this rowgroup got moved from the deltastore to a compressed state in the columnstore.<br /><br /> 1- NOT_APPLICABLE<br /><br /> 2 – INDEX_BUILD<br /><br /> 3 – TUPLE_MOVER<br /><br /> 4 – REORG_NORMAL<br /><br /> 5 – REORG_FORCED<br /><br /> 6 - BULKLOAD<br /><br /> 7 - MERGE|  
+|**transition_to_compressed_state_desc**|nvarchar(60)|NOT_APPLICABLE – the operation does not apply to the deltastore. Or, the rowgroup was compressed prior to upgrading to [!INCLUDE[ssSQL15](../../includes/sssql15-md.md)] in which case the history is not preserved.<br /><br /> INDEX_BUILD – An index create or index rebuild compressed the rowgroup.<br /><br /> TUPLE_MOVER – The tuple mover running in the background compressed the rowgroup. This happens after the rowgroup changes state from OPEN to CLOSED.<br /><br /> REORG_NORMAL – The reorganization operation, ALTER INDEX … REORG, moved the CLOSED rowgroup from the deltastore to the columnstore. This occurred before the tuple-mover had time to move the rowgroup.<br /><br /> REORG_FORCED – This rowgroup was open in the deltastore and was forced into the columnstore before it had a full number of rows.<br /><br /> BULKLOAD – A bulk load operation compressed the rowgroup directly without using the deltastore.<br /><br /> MERGE – A merge operation consolidated one or more rowgroups into this rowgroup and then performed the columnstore compression.|  
 |**has_vertipaq_optimization**|bit|Vertipaq optimization improves columnstore compression by rearranging the order of the rows in the rowgroup to achieve higher compression. This optimization occurs automatically in most cases. There are two cases Vertipaq optimization is not used:<br/>  a. when a delta rowgroup moves into the columnstore and there are one or more nonclustered indexes on the columnstore index - in this case Vertipaq optimization is skipped to minimizes changes to the mapping index;<br/> b. for columnstore indexes on memory-optimized tables. <br /><br /> 0 = No<br /><br /> 1 = Yes|  
 |**generation**|bigint|Row group generation associated with this row group.|  
 |**created_time**|datetime2|Clock time for when this rowgroup was created.<br /><br /> NULL – for a columnstore index on an in-memory table.|  

docs/t-sql/statements/create-columnstore-index-transact-sql.md

@@ -2,7 +2,7 @@
 title: "CREATE COLUMNSTORE INDEX (Transact-SQL) | Microsoft Docs"
 ms.custom: 
   - "SQL2016_New_Updated"
-ms.date: "06/26/2017"
+ms.date: "07/13/2017"
 ms.prod: "sql-non-specified"
 ms.reviewer: ""
 ms.suite: ""
@@ -73,9 +73,9 @@ CREATE CLUSTERED COLUMNSTORE INDEX index_name
 CREATE [NONCLUSTERED]  COLUMNSTORE INDEX index_name   
     ON [database_name. [schema_name ] . | schema_name . ] table_name   
         ( column  [ ,...n ] )  
+    [ WHERE <filter_expression> [ AND <filter_expression> ] ]
     [ WITH ( < with_option> [ ,...n ] ) ]  
-    [ ON <on_option> ]  
-    [ WHERE <filter_expression> [ AND <filter_expression> ] ]  
+    [ ON <on_option> ]   
 [ ; ]  
   
 <with_option> ::=