Merge branch 'release-sqlseattle' of

HeidiSteen · HeidiSteen · commit 93b41847c1ea · 2018-09-14T10:06:00.000-07:00
diff --git a/docs/integration-services/lift-shift/ssis-azure-connect-to-catalog-database.md b/docs/integration-services/lift-shift/ssis-azure-connect-to-catalog-database.md
@@ -1,7 +1,7 @@
 ---
 title: "Connect to the SSIS Catalog  (SSISDB) in Azure | Microsoft Docs"
 description: Find the connection information you need to connect to the SSIS Catalog (SSISDB) hosted on an Azure SQL Database server.
-ms.date: "09/25/2017"
+ms.date: "09/23/2018"
 ms.topic: conceptual
 ms.prod: sql
 ms.prod_service: "integration-services"
@@ -24,7 +24,7 @@ Find the connection information you need to connect to the SSIS Catalog (SSISDB)
 > You can't create the SSISDB Catalog database on Azure SQL Database at this time independently of creating the Azure-SSIS Integration Runtime in Azure Data Factory. The Azure-SSIS IR is the runtime environment that runs SSIS packages on Azure. For a walkthrough of the process, see [Deploy and run an SSIS package in Azure](https://docs.microsoft.com/azure/data-factory/tutorial-create-azure-ssis-runtime-portal). 
 
 ## Prerequisites
-Before you start, make sure you have version 17.2 or later of SQL Server Management Studio (SSMS). If the SSISDB Catalog database is hosted on SQL Database Managed Instance (Preview), make sure you have version 17.6 or later of SSMS. To download the latest version of SSMS, see [Download SQL Server Management Studio (SSMS)](https://docs.microsoft.com/sql/ssms/download-sql-server-management-studio-ssms).
+Before you start, make sure you have version 17.2 or later of SQL Server Management Studio (SSMS). If the SSISDB Catalog database is hosted on SQL Database Managed Instance, make sure you have version 17.6 or later of SSMS. To download the latest version of SSMS, see [Download SQL Server Management Studio (SSMS)](https://docs.microsoft.com/sql/ssms/download-sql-server-management-studio-ssms).
 
 ## Get the connection info from the Azure portal
 1. Log in to the [Azure portal](https://portal.azure.com/).
diff --git a/docs/integration-services/lift-shift/ssis-azure-lift-shift-ssis-packages-overview.md b/docs/integration-services/lift-shift/ssis-azure-lift-shift-ssis-packages-overview.md
@@ -1,7 +1,7 @@
 ---
 title: "Deploy and run SSIS packages in Azure | Microsoft Docs"
 description: Learn how you can move your SQL Server Integration Services (SSIS) projects, packages, and workloads to the Microsoft Azure cloud.
-ms.date: "07/01/2018"
+ms.date: "09/23/2018"
 ms.topic: conceptual
 ms.prod: sql
 ms.prod_service: "integration-services"
@@ -14,7 +14,7 @@ ms.reviewer: douglasl
 manager: craigg
 ---
 # Lift and shift SQL Server Integration Services workloads to the cloud
-You can now move your SQL Server Integration Services (SSIS) projects, packages, and workloads to the Azure cloud. Deploy, run, and manage SSIS projects and packages in the SSIS Catalog (SSISDB) on Azure SQL Database or SQL Database Managed Instance (Preview) with familiar tools such as SQL Server Management Studio (SSMS).
+You can now move your SQL Server Integration Services (SSIS) projects, packages, and workloads to the Azure cloud. Deploy, run, and manage SSIS projects and packages in the SSIS Catalog (SSISDB) on Azure SQL Database or SQL Database Managed Instance with familiar tools such as SQL Server Management Studio (SSMS).
 
 ## Benefits
 Moving your on-premises SSIS workloads to Azure has the following potential benefits:
@@ -30,7 +30,7 @@ The most significant difference is the separation of storage from runtime. Azure
 | Location | Storage | Runtime | Scalability |
 |---|---|---|---|
 | On premises | SQL Server | SSIS runtime hosted by SQL Server | SSIS Scale Out (in SQL Server 2017 and later)<br/><br/>Custom solutions (in prior versions of SQL Server) |
-| On Azure | SQL Database or SQL Database Managed Instance (Preview) | Azure-SSIS Integration Runtime, a component of Azure Data Factory | Scaling options for the Azure-SSIS Integration Runtime |
+| On Azure | SQL Database or SQL Database Managed Instance | Azure-SSIS Integration Runtime, a component of Azure Data Factory | Scaling options for the Azure-SSIS Integration Runtime |
 | | | | |
 
 ## Provision SSIS on Azure
diff --git a/docs/integration-services/lift-shift/ssis-azure-schedule-packages-ssms.md b/docs/integration-services/lift-shift/ssis-azure-schedule-packages-ssms.md
@@ -1,7 +1,7 @@
 ---
 title: "Schedule SSIS packages in Azure with SSMS | Microsoft Docs"
 description: "Describes how to schedule SSIS packages deployed to Azure SQL Database by using the Schedule command in SQL Server Management Studio (SSMS)."
-ms.date: "05/09/2018"
+ms.date: "09/23/2018"
 ms.topic: conceptual
 ms.prod: sql
 ms.prod_service: "integration-services"
@@ -15,7 +15,7 @@ manager: craigg
 ---
 # Schedule the execution of SSIS packages deployed in Azure with SQL Server Management Studio (SSMS)
 
-You can use SQL Server Management Studio (SSMS) to schedule SSIS packages deployed to Azure SQL Database. SQL Server on premises and SQL Database Managed Instance (Preview) have SQL Server Agent and Managed Instance Agent respectively as a first-class SSIS job scheduler. SQL Database, on the other hand, does not have a built-in first-class SSIS job scheduler. The SSMS feature described in this article provides a familiar user interface that's similar to SQL Server Agent for scheduling packages deployed to SQL Database.
+You can use SQL Server Management Studio (SSMS) to schedule SSIS packages deployed to Azure SQL Database. SQL Server on premises and SQL Database Managed Instance have SQL Server Agent and Managed Instance Agent respectively as a first-class SSIS job scheduler. SQL Database, on the other hand, does not have a built-in first-class SSIS job scheduler. The SSMS feature described in this article provides a familiar user interface that's similar to SQL Server Agent for scheduling packages deployed to SQL Database.
 
 If you're using SQL Database to host the SSIS catalog, `SSISDB`, you can use this SSMS feature to generate the Data Factory pipelines, activities, and triggers required to schedule SSIS packages. Later you can optionally edit and extend these objects in Data Factory.
 
diff --git a/docs/relational-databases/import-export/import-data-from-excel-to-sql.md b/docs/relational-databases/import-export/import-data-from-excel-to-sql.md
@@ -1,7 +1,7 @@
 ---
 title: "Import data from Excel to SQL | Microsoft Docs"
 ms.custom: ""
-ms.date: "06/29/2018"
+ms.date: "09/23/2018"
 ms.prod: sql
 ms.prod_service: "database-engine, sql-database"
 ms.component: "import-export"
@@ -65,7 +65,7 @@ To start learning how to build SSIS packages, see the tutorial [How to Create an
 ## <a name="openrowset"></a> OPENROWSET and linked servers
 
 > [!NOTE]
-> In Azure, the OPENROWSET and OPENDATASOURCE functions are available only on SQL Database Managed Instance (Preview).
+> In Azure, the OPENROWSET and OPENDATASOURCE functions are available only on SQL Database Managed Instance.
 
 > [!NOTE]
 > The ACE provider (formerly the Jet provider) that connects to Excel data sources is intended for interactive client-side use. If you use the ACE provider on the server, especially in automated processes or processes running in parallel, you may see unexpected results.
diff --git a/docs/relational-databases/replication/configure-publishing-and-distribution.md b/docs/relational-databases/replication/configure-publishing-and-distribution.md
@@ -1,7 +1,7 @@
 ---
 title: "Configure Publishing and Distribution | Microsoft Docs"
 ms.custom: ""
-ms.date: "06/15/2018"
+ms.date: "09/23/2018"
 ms.prod: sql
 ms.prod_service: "database-engine"
 ms.component: "replication"
@@ -63,7 +63,7 @@ Replication publishing and distribution can be configured programmatically using
 
 2. At the Distributor, which is also the Publisher, execute [sp_adddistpublisher &#40;Transact-SQL&#41;](../../relational-databases/system-stored-procedures/sp-adddistpublisher-transact-sql.md), specifying the UNC share that will be used as default snapshot folder for `@working_directory`.
 
-   For a distributor on SQL Database Managed Instance (preview) use an Azure storage account for `@working_directory` and the storage access key for `@storage_connection_string`. 
+   For a distributor on SQL Database Managed Instance, use an Azure storage account for `@working_directory` and the storage access key for `@storage_connection_string`. 
 
 3. At the Publisher, execute [sp_replicationdboption &#40;Transact-SQL&#41;](../../relational-databases/system-stored-procedures/sp-replicationdboption-transact-sql.md). Specify the database being published for `@dbname`, the type of replication for `@optname`, and a value of `true` for `@value`.
 
@@ -77,7 +77,7 @@ Replication publishing and distribution can be configured programmatically using
 
 2. At the Distributor, execute [sp_adddistpublisher &#40;Transact-SQL&#41;](../../relational-databases/system-stored-procedures/sp-adddistpublisher-transact-sql.md), specifying the UNC share that will be used as default snapshot folder for `@working_directory`. If the Distributor will use [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Authentication when connecting to the Publisher, you must also specify a value of `0` for `@security_mode` and the [!INCLUDE[msCoName](../../includes/msconame-md.md)] [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] login information for `@login` and `@password`.
 
-   For a distributor on SQL Database Managed Instance (preview) use an Azure storage account for `@working_directory` and the storage access key for `@storage_connection_string`. 
+   For a distributor on SQL Database Managed Instance, use an Azure storage account for `@working_directory` and the storage access key for `@storage_connection_string`. 
 
 3. At the Publisher on the master database, execute [sp_adddistributor &#40;Transact-SQL&#41;](../../relational-databases/system-stored-procedures/sp-adddistributor-transact-sql.md). Specify the strong password used in step 1 for `@password`. This password will be used by the Publisher when connecting to the Distributor.
 
diff --git a/docs/relational-databases/replication/replication-to-sql-database.md b/docs/relational-databases/replication/replication-to-sql-database.md
@@ -1,7 +1,7 @@
 ---
 title: "Replication to SQL Database | Microsoft Docs"
 ms.custom: ""
-ms.date: "04/24/2016"
+ms.date: "09/23/2018"
 ms.prod: sql
 ms.prod_service: "database-engine, sql-database"
 ms.component: "replication"
@@ -30,7 +30,7 @@ monikerRange: "=azuresqldb-current||>=sql-server-2016||=sqlallproducts-allversio
  - [!INCLUDE[ssSDS](../../includes/sssds-md.md)] must be a push subscriber of a [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] publisher.  
  -  The distribution database and the replication agents cannot be placed on [!INCLUDE[ssSDS](../../includes/sssds-md.md)].  
  - Snapshot and one-way transactional replication are supported. Peer-to-peer transactional replication and merge replication are not supported.
- - SQL Database Managed Instance (preview) supports publisher and distributor databases. For more information, see [Replication with SQL Database Managed Instance](replication-with-sql-database-managed-instance.md).
+ - Replication is available for public preview on Azure SQL Database Managed Instance. Managed Instance can host publisher, distributor, and subscriber databases. For more information, see [Replication with SQL Database Managed Instance](replication-with-sql-database-managed-instance.md).
  
  ## Versions  
  - The publisher and distributor must be at least at one of the following versions:  
diff --git a/docs/relational-databases/replication/replication-with-sql-database-managed-instance.md b/docs/relational-databases/replication/replication-with-sql-database-managed-instance.md
@@ -1,7 +1,7 @@
 ---
 title: "Replication with SQL Database Managed Instance| Microsoft Docs"
 ms.custom: ""
-ms.date: "06/15/2018"
+ms.date: "09/23/2018"
 ms.prod: sql
 ms.prod_service: "database-engine, sql-database"
 ms.component: "replication"
@@ -25,7 +25,7 @@ monikerRange: "=azuresqldb-current||>=sql-server-2016||=sqlallproducts-allversio
 
 [!INCLUDE[appliesto-ss-asdbmi-xxxx-xxx-md](../../includes/appliesto-ss-asdbmi-xxxx-xxx-md.md)]
 
-Azure SQL Database Managed Instance (preview) supports transactional replication. Managed Instance can host publisher, distributor, and subscriber databases.
+Replication is available for public preview on Azure SQL Database Managed Instance. Managed Instance can host publisher, distributor, and subscriber databases.
 
 ## Common configurations
 
@@ -202,4 +202,4 @@ The following features are not supported:
 
 ## See Also
 
-- [What is a Managed Instance (preview)?](http://docs.microsoft.com/azure/sql-database/sql-database-managed-instance)
+- [What is a Managed Instance?](http://docs.microsoft.com/azure/sql-database/sql-database-managed-instance)
diff --git a/docs/ssms/sql-server-management-studio-changelog-ssms.md b/docs/ssms/sql-server-management-studio-changelog-ssms.md
@@ -1,7 +1,7 @@
 ---
 title: "SQL Server Management Studio - Changelog (SSMS) | Microsoft Docs"
 ms.custom: ""
-ms.date: "09/04/2018"
+ms.date: "09/23/2018"
 ms.prod: sql
 ms.prod_service: "sql-tools"
 ms.component: "ssms"
@@ -190,7 +190,7 @@ Azure SQL Data Warehouse:
 
 **Integration Services (IS)**
 
-- Added a scheduling feature for SSIS packages deployed to Azure SQL Database. Unlike SQL Server on premises and SQL Database Managed Instance (Preview), which have SQL Server Agent as a first-class job scheduler, SQL Database does not have a built-in scheduler. This new SSMS feature provides a familiar user interface that's similar to SQL Server Agent for scheduling packages deployed to SQL Database. If you're using SQL Database to host the SSIS catalog database, SSISDB, you can use this SSMS feature to generate the Data Factory pipelines, activities, and triggers required to schedule SSIS packages. You can then edit and extend these objects in Data Factory. For more info, see [Schedule SSIS package execution on Azure SQL Database with SSMS](../integration-services/lift-shift/ssis-azure-schedule-packages-ssms.md). To learn more about Azure Data Factory pipelines, activities, and triggers, see [Pipelines and activities in Azure Data Factory](https://docs.microsoft.com/azure/data-factory/concepts-pipelines-activities) and [Pipeline execution and triggers in Azure Data Factory](https://docs.microsoft.com/azure/data-factory/concepts-pipeline-execution-triggers).
+- Added a scheduling feature for SSIS packages deployed to Azure SQL Database. Unlike SQL Server on premises and SQL Database Managed Instance, which have SQL Server Agent as a first-class job scheduler, SQL Database does not have a built-in scheduler. This new SSMS feature provides a familiar user interface that's similar to SQL Server Agent for scheduling packages deployed to SQL Database. If you're using SQL Database to host the SSIS catalog database, SSISDB, you can use this SSMS feature to generate the Data Factory pipelines, activities, and triggers required to schedule SSIS packages. You can then edit and extend these objects in Data Factory. For more info, see [Schedule SSIS package execution on Azure SQL Database with SSMS](../integration-services/lift-shift/ssis-azure-schedule-packages-ssms.md). To learn more about Azure Data Factory pipelines, activities, and triggers, see [Pipelines and activities in Azure Data Factory](https://docs.microsoft.com/azure/data-factory/concepts-pipelines-activities) and [Pipeline execution and triggers in Azure Data Factory](https://docs.microsoft.com/azure/data-factory/concepts-pipeline-execution-triggers).
 - Support for SSIS package scheduling in SQL Agent on SQL Managed instance. It is now possible to create SQL Agent jobs to execute SSIS packages on the managed instance. 
 
 ### Bug fixes
@@ -253,7 +253,7 @@ Release date: March 20, 2018
 
 SQL Database Managed Instance:
 
-- Added a support for [Azure SQL Database Managed Instance](https://docs.microsoft.com/azure/sql-database/sql-database-managed-instance). Azure SQL Database Managed Instance (preview) is a new flavor of Azure SQL Database, providing near 100% compatibility with SQL Server on-premises, a native [virtual network (VNet)](https://docs.microsoft.com/azure/virtual-network/virtual-networks-overview) implementation that addresses common security concerns, and a [business model](https://azure.microsoft.com/pricing/details/sql-database/) favorable for on-premises SQL Server customers.
+- Added a support for [Azure SQL Database Managed Instance](https://docs.microsoft.com/azure/sql-database/sql-database-managed-instance). Azure SQL Database Managed Instance provides near 100% compatibility with SQL Server on-premises, a native [virtual network (VNet)](https://docs.microsoft.com/azure/virtual-network/virtual-networks-overview) implementation that addresses common security concerns, and a [business model](https://azure.microsoft.com/pricing/details/sql-database/) favorable for on-premises SQL Server customers.
 - Support for common management scenarios like:
    - Create and alter databases.
    - Backup and restore databases.
