Bringing even with master.

v-alje · v-alje · commit 70b527975710 · 2018-09-19T12:50:07.000-07:00
diff --git a/docs/relational-databases/indexes/create-filtered-indexes.md b/docs/relational-databases/indexes/create-filtered-indexes.md
@@ -67,7 +67,9 @@ monikerRange: "=azuresqldb-current||>=sql-server-2016||=sqlallproducts-allversio
   
 ###  <a name="Restrictions"></a> Limitations and Restrictions  
   
--   You cannot create a filtered index on a view. However, the query optimizer can benefit from a filtered index defined on a table that is referenced in a view. The query optimizer considers a filtered index for a query that selects from a view if the query results will be correct.  
+-   You cannot create a filtered index on a view. However, the query optimizer can benefit from a filtered index defined on a table that is referenced in a view. The query optimizer considers a filtered index for a query that selects from a view if the query results will be correct.
+
+-   You cannot create a filtered index on a table when the column accessed in the filter expression is of a CLR data type.
   
 -   Filtered indexes have the following advantages over indexed views:  
   
diff --git a/docs/relational-databases/system-catalog-views/sys-soap-endpoints-transact-sql.md b/docs/relational-databases/system-catalog-views/sys-soap-endpoints-transact-sql.md
@@ -39,7 +39,7 @@ manager: craigg
 |**is_sql_language_enabled**|**bit**|1 = BATCHES = ENABLED option was specified, meaning that ad-hoc SQL batches are allowed on the endpoint.|  
 |**wsdl_generator_procedure**|**nvarchar(776)**|The three-part name of the stored procedure that implements this method.<br /><br /> Names of methods require strict three-part syntax. one, two, or four-part names are not allowed.|  
 |**default_database**|**sysname**|The name of the default database given in the DATABASE = option.<br /><br /> NULL = DEFAULT was specified.|  
-|**default_namespace**|**nvarchar(384)**|The default namespace specified in the NAMESPACE = option, or 'http://tempuri.org' if DEFAULT was specified instead.|  
+|**default_namespace**|**nvarchar(384)**|The default namespace specified in the NAMESPACE = option, or `http://tempuri.org` if DEFAULT was specified instead.|  
 |**default_result_schema**|**tinyint**|The default value of the SCHEMA = option.<br /><br /> 0 = NONE<br /><br /> 1 = STANDARD|  
 |**default_result_schema_desc**|**nvarchar(60)**|Description of the default value of the SCHEMA = option.<br /><br /> NONE<br /><br /> STANDARD|  
 |**is_xml_charset_enforced**|**bit**|0 = CHARACTER_SET = SQL option was specified.<br /><br /> 1 = CHARACTER_SET = XML option was specified.|  
diff --git a/docs/ssma/access/what-s-new-in-ssma-for-access-accesstosql.md b/docs/ssma/access/what-s-new-in-ssma-for-access-accesstosql.md
@@ -2,7 +2,7 @@
 title: "What's New in SSMA for Access(AccessToSQL) | Microsoft Docs"
 ms.prod: sql
 ms.custom: ""
-ms.date: "08/14/2018"
+ms.date: "09/22/2018"
 ms.reviewer: ""
 ms.suite: "sql"
 ms.technology: ssma
@@ -20,6 +20,12 @@ manager: craigg
 # What's New in SSMA for Access (AccessToSQL)
 This article lists SSMA for Access changes in each release.  
 
+## SSMA v7.10
+The v7.10 release of SSMA for Access has been enhanced with targeted fixes designed to provide additional security and privacy protections to meet changes in global requirements.
+
+> [!IMPORTANT]
+> With SSMA v7.4 and later versions, .Net 4.5.2 is an installation pre-requisite.
+
 ## SSMA v7.9
 The v7.9 release of SSMA for Access contains the following changes:
 - Targeted fixes that improve quality and conversion metrics.
@@ -40,7 +46,7 @@ The v7.8 release of SSMA for Access contains the following changes:
 ## SSMA v7.7
 The v7.7 release of SSMA for Access contains the following changes:
 - SSMA for Access has been enhanced with targeted fixes that improve quality and conversion metrics.
-- Based on the popular demand, the 32-bit version of SSMA for Access is back. Compared to the previous implementation (prior to v7.4), there are two installer packages, but they cannot be installed side by side. As a result, you must choose the most appropriate version based on the connectivity components you have. It is always preferable to use the 64-bit version, if possible.
+- Based on the popular demand, the 32-bit version of SSMA for Access is back. Compared to the previous implementation (prior to v7.4), there are two installer packages, but they cannot be installed side by side. As a result, you must choose the most appropriate version based on the connectivity components you have. It's always preferable to use the 64-bit version, if possible.
 
 > [!IMPORTANT]
 > With SSMA v7.4 and later versions, .Net 4.5.2 is an installation pre-requisite.
@@ -78,7 +84,7 @@ The v7.3 release of SSMA for Access contains the following changes:
   - Libraries that can be consumed by SSMA for performing custom conversions.
     - You can now construct code that can handle custom syntax conversions and conversions that weren't previously handled by SSMA.
       - Instructions on how to construct a custom converter are available in this blog post, [Extending SQL Server Migration Assistant's conversion capabilities](https://blogs.msdn.microsoft.com/datamigration/2017/02/21/2185/).
-      - Sample project for conversion can be download this [blog post](https://blogs.msdn.microsoft.com/datamigration/ssmafororacleconversionsample/).
+      - Download a sample project for conversion from this [blog post](https://blogs.msdn.microsoft.com/datamigration/ssmafororacleconversionsample/).
 
 ## SSMA v7.2
 The v7.2 release of SSMA for Access contains the following changes:
@@ -88,7 +94,7 @@ The v7.2 release of SSMA for Access contains the following changes:
 ## SSMA v7.1
 The v7.1 release of SSMA for Access contains the following changes:
 - SQL Server 2017 on Windows and Linux CTP1 is now a supported target platform for migration. This feature is in technical preview and supports schema and data movement to target SQL servers.
-- SSMA now supports automatic updates to download the latest version of SSMA as soon as it is available.
+- SSMA now supports automatic updates to download the latest version of SSMA as soon as it's available.
 - SSMA installable binaries are now delivered through Windows installer package files (.msi).
 
 **Resources**
diff --git a/docs/ssma/db2/what-s-new-in-ssma-for-db2-db2tosql.md b/docs/ssma/db2/what-s-new-in-ssma-for-db2-db2tosql.md
@@ -2,7 +2,7 @@
 title: "What's New in SSMA  for DB2 (DB2ToSQL) | Microsoft Docs"
 ms.prod: sql
 ms.custom: ""
-ms.date: "08/14/2018"
+ms.date: "09/22/2018"
 ms.reviewer: ""
 ms.suite: "sql"
 ms.technology: ssma
@@ -20,11 +20,19 @@ manager: craigg
 # What's New in SSMA for DB2 (DB2ToSQL)
 This article lists SSMA for DB2 changes in each release.  
 
+## SSMA v7.10
+The v7.10 release of SSMA for DB2 contains the following changes:
+- Targeted fixes designed to provide additional security and privacy protections to meet changes in global requirements.
+- A fix for conversion of BEGIN-END blocks.
+
+> [!IMPORTANT]
+> With SSMA v7.4 and later versions, .Net 4.5.2 is an installation pre-requisite.
+
 ## SSMA v7.9
 The v7.9 release of SSMA for DB2 contains the following changes:
 - Targeted fixes that improve quality and conversion metrics.
 - Support in SSMA command line to alter Data Type mapping and Project Preferences.
-- Support for migrating data using SQL Server Integration Services (SSIS). After converting the schema, it is possible to create an SSIS package by using a right-click context menu option.
+- Support for migrating data using SQL Server Integration Services (SSIS). After converting the schema, it's possible to create an SSIS package by using a right-click context menu option.
 - The Azure SQL Database connection dialog in SSMA has also been altered to specify the fully qualified server name. In previous versions of SSMA, the Azure SQL Database prefix had to be explicitly mentioned inside projects settings.
 
 > [!IMPORTANT]
@@ -41,13 +49,13 @@ The v7.8 release of SSMA for DB2 contains the following changes:
 ## SSMA v7.7
 The v7.7 release of SSMA for DB2 contains the following changes:
 - SSMA for DB2 has been enhanced with targeted fixes that improve quality and conversion metrics.
-- Based on the popular demand, the 32-bit version of SSMA for DB2 is back. Compared to the previous implementation (prior to v7.4), there are two installer packages, but they cannot be installed side by side. As a result, you must choose the most appropriate version based on the connectivity components you have. It is always preferable to use the 64-bit version, if possible.
+- Based on the popular demand, the 32-bit version of SSMA for DB2 is back. Compared to the previous implementation (prior to v7.4), there are two installer packages, but they cannot be installed side by side. As a result, you must choose the most appropriate version based on the connectivity components you have. It's always preferable to use the 64-bit version, if possible.
 
 > [!IMPORTANT]
 > With SSMA v7.4 and later versions, .Net 4.5.2 is an installation pre-requisite.
 
 ## SSMA v7.6
-The v7.6 release of SSMA for DB2 has been enhanced with targeted fixes that improve quality and conversion metrics and with support for SQL Server 2017 (public preview). Support for SQL Server 2017 on Windows and Linux is in public preview and should not be used for production migrations.
+The v7.6 release of SSMA for DB2 has been enhanced with targeted fixes that improve quality and conversion metrics and with support for SQL Server 2017 (public preview). Support for SQL Server 2017 on Windows and Linux is in public preview and shouldn't be used for production migrations.
 
 > [!IMPORTANT]
 > With SSMA v7.4 and later versions, .Net 4.5.2 is an installation pre-requisite, and the 32-bit version of the tool has been discontinued.
@@ -78,7 +86,7 @@ The v7.3 release of SSMA for DB2 contains the following changes:
   - Libraries that can be consumed by SSMA for performing custom conversions.
     - You can now construct code that can handle custom syntax conversions and conversions that weren't previously handled by SSMA.
       - Instructions on how to construct a custom converter are available in this blog post, [Extending SQL Server Migration Assistant's conversion capabilities](https://blogs.msdn.microsoft.com/datamigration/2017/02/21/2185/).
-      - Sample project for conversion can be download this [blog post](https://blogs.msdn.microsoft.com/datamigration/ssmafororacleconversionsample/).
+      - Download a sample project for conversion from this [blog post](https://blogs.msdn.microsoft.com/datamigration/ssmafororacleconversionsample/).
 
 ## SSMA v7.2
 The v7.2 release of SSMA for DB2 contains the following changes:
@@ -88,7 +96,7 @@ The v7.2 release of SSMA for DB2 contains the following changes:
 ## SSMA v7.1
 The v7.1 release of SSMA for Access contains the following changes:
 - SQL Server 2017 on Windows and Linux CTP1 is now a supported target platform for migration. This feature is in technical preview and allows schema and data movement to target SQL servers.
-- SSMA now supports automatic updates to download the latest version of SSMA as soon as it is available.
+- SSMA now supports automatic updates to download the latest version of SSMA as soon as it's available.
 - SSMA installable binaries are now delivered through Windows installer package files (.msi).
 
 **Resources**
diff --git a/docs/ssma/mysql/what-s-new-in-ssma-for-mysql-mysqltosql.md b/docs/ssma/mysql/what-s-new-in-ssma-for-mysql-mysqltosql.md
@@ -2,7 +2,7 @@
 title: "What's New in SSMA for MySQL (MySQLToSql) | Microsoft Docs"
 ms.prod: sql
 ms.custom: ""
-ms.date: "08/14/2018"
+ms.date: "09/22/2018"
 ms.reviewer: ""
 ms.suite: "sql"
 ms.technology: ssma
@@ -20,6 +20,14 @@ manager: craigg
 # What's New in SSMA for MySQL (MySQLToSql)
 This article lists SSMA for MySQL changes in each release. 
 
+## SSMA v7.10
+The v7.10 release of SSMA for MySQL contains the following changes:
+- Targeted fixes designed to provide additional security and privacy protections to meet changes in global requirements.
+- A fix for conversion of spaces between function name and arguments list.
+
+> [!IMPORTANT]
+> With SSMA v7.4 and later versions, .Net 4.5.2 is an installation pre-requisite.
+
 ## SSMA v7.9
 The v7.9 release of SSMA for MySQL contains the following changes:
 - Targeted fixes that improve quality and conversion metrics.
@@ -79,7 +87,7 @@ The v7.3 release of SSMA for MySQL contains the following changes:
   - Libraries that can be consumed by SSMA for performing custom conversions.
     - You can now construct code that can handle custom syntax conversions and conversions that weren't previously handled by SSMA.
       - Instructions on how to construct a custom converter are available in this blog post, [Extending SQL Server Migration Assistant's conversion capabilities](https://blogs.msdn.microsoft.com/datamigration/2017/02/21/2185/).
-      - Sample project for conversion can be download this [blog post](https://blogs.msdn.microsoft.com/datamigration/ssmafororacleconversionsample/).
+      - Download a sample project for conversion from this [blog post](https://blogs.msdn.microsoft.com/datamigration/ssmafororacleconversionsample/).
 
 ## SSMA v7.2
 The v7.2 release of SSMA for MySQL contains the following changes:
diff --git a/docs/ssma/oracle/what-s-new-in-ssma-for-oracle-oracletosql.md b/docs/ssma/oracle/what-s-new-in-ssma-for-oracle-oracletosql.md
@@ -2,7 +2,7 @@
 title: "What's New in SSMA  for Oracle (OracleToSQL) | Microsoft Docs"
 ms.prod: sql
 ms.custom: ""
-ms.date: "08/14/2018"
+ms.date: "09/22/2018"
 ms.reviewer: ""
 ms.suite: "sql"
 ms.technology: ssma
@@ -17,12 +17,20 @@ manager: craigg
 # What's New in SSMA for Oracle (OracleToSQL)
 This article lists SSMA for Oracle changes in each release.  
 
+## SSMA v7.10
+The v7.10 release of SSMA for Oracle contains the following changes:
+- Targeted fixes designed to provide additional security and privacy protections to meet changes in global requirements.
+- A conversion improvement related to hierarchical queries.
+
+> [!IMPORTANT]
+> With SSMA v7.4 and later versions, .Net 4.5.2 is an installation pre-requisite.
+
 ## SSMA v7.9
 The v7.9 release of SSMA for Oracle contains the following changes:
 - Targeted fixes that improve quality and conversion metrics.
 - Support for migrating "Continue" statements from Oracle to SQL Server.
 - Support in SSMA command line to alter Data Type mapping and Project Preferences.
-- Support for migrating data using SQL Server Integration Services (SSIS). After converting the schema, it is possible to create an SSIS package by using a right-click context menu option.
+- Support for migrating data using SQL Server Integration Services (SSIS). After converting the schema, it's possible to create an SSIS package by using a right-click context menu option.
 - The Azure SQL Database connection dialog in SSMA has also been altered to specify the fully qualified server name. In previous versions of SSMA, the Azure SQL Database prefix had to be explicitly mentioned inside projects settings.
 
 > [!IMPORTANT]
@@ -43,15 +51,15 @@ The v7.8 release of SSMA for Oracle contains the following changes:
 ## SSMA v7.7
 The v7.7 release of SSMA for Oracle contains the following changes:
 - SSMA for Oracle has been enhanced with targeted fixes that improve quality and conversion metrics.
-- Based on the popular demand, the 32-bit version of SSMA for Oracle is back. Compared to the previous implementation (prior to v7.4), there are two installer packages, but they cannot be installed side by side. As a result, you must choose the most appropriate version based on the connectivity components you have. It is always preferable to use the 64-bit version, if possible.
-- SQL Server 2017 support is now official with the Oracle Extension Pack supported on Linux as well (new remote installation option). Note that Extension Pack functionality is limited when installed on Linux, as the tester and server-side data migration features are not supported 
+- Based on the popular demand, the 32-bit version of SSMA for Oracle is back. Compared to the previous implementation (prior to v7.4), there are two installer packages, but they can't be installed side by side. As a result, you must choose the most appropriate version based on the connectivity components you have. It's always preferable to use the 64-bit version, if possible.
+- SQL Server 2017 support is now official with the Oracle Extension Pack supported on Linux as well (new remote installation option). Note that Extension Pack functionality is limited when installed on Linux, as the tester and server-side data migration features aren't supported.
 - SSMA for Oracle allows you to migrate Materialized Views as regular tables (configurable through the settings at **Project Settings** -> **Synchronization** -> **Discover backing tables for Materialized Views**).
 
 > [!IMPORTANT]
 > With SSMA v7.4 and later versions, .Net 4.5.2 is an installation pre-requisite.
 
 ## SSMA v7.6
-The v7.6 release of SSMA for Oracle has been enhanced with targeted fixes that improve quality and conversion metrics and with support for SQL Server 2017 (public preview). Support for SQL Server 2017 on Windows and Linux is in public preview and should not be used for production migrations.
+The v7.6 release of SSMA for Oracle has been enhanced with targeted fixes that improve quality and conversion metrics and with support for SQL Server 2017 (public preview). Support for SQL Server 2017 on Windows and Linux is in public preview and shouldn't be used for production migrations.
 
 > [!IMPORTANT]
 > With SSMA v7.4 and later versions, .Net 4.5.2 is an installation pre-requisite, and the 32-bit version of the tool has been discontinued.
@@ -107,7 +115,7 @@ The v7.2 release of SSMA for Oracle contains the following changes:
 ## SSMA v7.1
 The v7.1 release of SSMA for Oracle contains the following changes:
 - SQL Server 2017 on Windows and Linux CTP1 is now a supported target platform for migration. This feature is in technical preview and allows schema and data movement to target SQL servers.
-- SSMA now supports automatic updates to download the latest version of SSMA as soon as it is available.
+- SSMA now supports automatic updates to download the latest version of SSMA as soon as it's available.
 - SSMA installable binaries are now delivered through Windows installer package files (.msi).
 
 **Resources**
@@ -122,8 +130,8 @@ The May 2016 release of SSMA for Oracle contains the following changes:
 - Added support for SQL Server 2016.
 - Added conversion of Oracle flashback archive tables to SQL Server temporal tables.
 
-    **Note** - SSMA does not copy history data from Oracle Flashback Data Archive tables. As a result, the history data must be copied manually during the migration process. In addition, while SSMA does not display the history table in the SQL Server metadata explorer because it’s treated as a system table, you can view the history table in SQL Server Management Studio.
-    SQL Server 2016 does not support several Oracle Flashback features, including:
+    **Note** - SSMA doesn't copy history data from Oracle Flashback Data Archive tables. As a result, the history data must be copied manually during the migration process. In addition, while SSMA doesn't display the history table in the SQL Server metadata explorer because it’s treated as a system table, you can view the history table in SQL Server Management Studio.
+    SQL Server 2016 doesn't support several Oracle Flashback features, including:
     - Oracle Flashback Transaction Query
     - DBMS_FLASHBACK Package
     - Flashback Transaction
diff --git a/docs/ssma/sybase/what-s-new-in-ssma-for-sybase-sybasetosql.md b/docs/ssma/sybase/what-s-new-in-ssma-for-sybase-sybasetosql.md
diff --git a/docs/t-sql/statements/create-external-file-format-transact-sql.md b/docs/t-sql/statements/create-external-file-format-transact-sql.md
