Merge pull request #7148 from MikeRayMSFT/release-sqlseattle

Merge master into release-sqlseattle

Author: MikeRayMSFT

docs/database-engine/configure-windows/sql-server-service-broker.md

@@ -1,7 +1,7 @@
 ---
 title: "SQL Server Service Broker | Microsoft Docs"
 ms.custom: ""
-ms.date: "03/30/2018"
+ms.date: "09/07/2018"
 ms.prod: sql
 ms.prod_service: high-availability
 ms.reviewer: ""
@@ -10,13 +10,13 @@ ms.technology: configuration
 ms.tgt_pltfrm: ""
 ms.topic: conceptual
 f1_keywords: 
-  - "SQL13.SWB.SSBMSGTYPEPROPERTIES.GENERAL.F1"
-  - "SQL13.SWB.SSBCONTRACTPROPERTIES.GENERAL.F1"
-  - "SQL13.SWB.SSBQUEUEPROPERTIES.GENERAL.F1"
-  - "SQL13.SWB.SSBREMSVCBINDPROPERTIES.GENERAL.F1"
-  - "SQL13.SWB.SSBROUTEPROPERTIES.GENERAL.F1"
-  - "SQL13.SWB.SSBPRIORITYPROPERTIES.GENERAL.F1"
-  - "SQL13.SWB.SSBSERVICEPROPERTIES.GENERAL.F1"
+  - SQL13.SWB.SSBMSGTYPEPROPERTIES.GENERAL.F1
+  - SQL13.SWB.SSBCONTRACTPROPERTIES.GENERAL.F1
+  - SQL13.SWB.SSBQUEUEPROPERTIES.GENERAL.F1
+  - SQL13.SWB.SSBREMSVCBINDPROPERTIES.GENERAL.F1
+  - SQL13.SWB.SSBROUTEPROPERTIES.GENERAL.F1
+  - SQL13.SWB.SSBPRIORITYPROPERTIES.GENERAL.F1
+  - SQL13.SWB.SSBSERVICEPROPERTIES.GENERAL.F1
 helpviewer_keywords: 
   - "Broker See Service Broker"
   - "SQL Server Service Broker"
@@ -34,8 +34,6 @@ monikerRange: "=azuresqldb-mi-current||>=sql-server-2016||=sqlallproducts-allver
   [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] [!INCLUDE[ssSB](../../includes/sssb-md.md)] provides native support for messaging and queuing applications in the [!INCLUDE[ssDEnoversion](../../includes/ssdenoversion-md.md)]. This makes it easier for developers to create sophisticated applications that use the [!INCLUDE[ssDE](../../includes/ssde-md.md)] components to communicate between disparate databases. Developers can use [!INCLUDE[ssSB](../../includes/sssb-md.md)] to easily build distributed and reliable applications.  
 
  Application developers who use [!INCLUDE[ssSB](../../includes/sssb-md.md)] can distribute data workloads across several databases without programming complex communication and messaging internals. This reduces development and test work because [!INCLUDE[ssSB](../../includes/sssb-md.md)] handles the communication paths in the context of a conversation. It also improves performance. For example, front-end databases supporting Web sites can record information and send process intensive tasks to queue in back-end databases. [!INCLUDE[ssSB](../../includes/sssb-md.md)] ensures that all tasks are managed in the context of transactions to assure reliability and technical consistency.  
-
-[!INCLUDE[ssMIlimitation](../../includes/sql-db-mi-limitation.md)]
 
 ## Where is the documentation for Service Broker?  
  The reference documentation for [!INCLUDE[ssSB](../../includes/sssb-md.md)] is included in the [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)] documentation. This reference documentation includes the following sections:  
@@ -54,6 +52,13 @@ monikerRange: "=azuresqldb-mi-current||>=sql-server-2016||=sqlallproducts-allver
 
 ## What's new in Service Broker  
  No significant changes are introduced in [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)].  The following changes were introduced in [!INCLUDE[ssSQL11](../../includes/sssql11-md.md)].  
+
+### Service broker and Azure SQL Database Managed Instance
+
+- Cross-instance service broker is not supported 
+ - `sys.routes` - Prerequisite: select address from sys.routes. Address must be LOCAL on every route. See [sys.routes](../../relational-databases/system-catalog-views/sys-routes-transact-sql.md).
+ - `CREATE ROUTE` - you cannot use `CREATE ROUTE` with `ADDRESS` other than `LOCAL`. See [CREATE ROUTE](https://docs.microsoft.com/sql/t-sql/statements/create-route-transact-sql).
+ - `ALTER ROUTE` cannot use `ALTER ROUTE` with `ADDRESS` other than `LOCAL`. See [ALTER ROUTE](../../t-sql/statements/alter-route-transact-sql.md).  
 
 ### Messages can be sent to multiple target services (multicast)  
  The syntax of the [SEND (Transact-SQL)](../../t-sql/statements/send-transact-sql.md) statement has been extended to enable multicast by supporting multiple conversation handles.  

docs/includes/tsql-appliesto-ss2008-asdbmi-asdw-pdw-md.md

@@ -0,0 +1 @@
+<Token>**APPLIES TO:** ![yes](media/yes.png)SQL Server (starting with 2008) ![yes](media/yes.png)Azure SQL Database (Managed Instance only) ![yes](media/no.png)Azure SQL Data Warehouse ![yes](media/yes.png)Parallel Data Warehouse </Token>

…l-appliesto-ss2008-asdbmi-xxxx-pwd-md.md …l-appliesto-ss2008-asdbmi-xxxx-pdw-md.mddocs/includes/tsql-appliesto-ss2008-asdbmi-xxxx-pwd-md.md renamed to docs/includes/tsql-appliesto-ss2008-asdbmi-xxxx-pdw-md.md docs/includes/tsql-appliesto-ss2008-asdbmi-xxxx-pwd-md.md renamed to docs/includes/tsql-appliesto-ss2008-asdbmi-xxxx-pdw-md.md

@@ -1,7 +1,7 @@
 ---
 title: "Copy-Only Backups (SQL Server) | Microsoft Docs"
 ms.custom: ""
-ms.date: "03/30/2016"
+ms.date: "09/07/2018"
 ms.prod: sql
 ms.prod_service: backup-restore
 ms.reviewer: ""
@@ -23,8 +23,6 @@ monikerRange: "=azuresqldb-mi-current||>=sql-server-2016||=sqlallproducts-allver
 # Copy-Only Backups (SQL Server)
 [!INCLUDE[appliesto-ss-asdbmi-xxxx-xxx-md](../../includes/appliesto-ss-asdbmi-xxxx-xxx-md.md)]
   A *copy-only backup* is a [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] backup that is independent of the sequence of conventional [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] backups. Usually, taking a backup changes the database and affects how later backups are restored. However, occasionally, it is useful to take a backup for a special purpose without affecting the overall backup and restore procedures for the database. Copy-only backups serve this purpose.  
-
-[!INCLUDE[ssMIlimitation](../../includes/sql-db-mi-limitation.md)]
 
  The types of copy-only backups are as follows:  
 

docs/relational-databases/backup-restore/copy-only-backups-sql-server.md

@@ -1,7 +1,7 @@
 ---
 title: "Targets for Extended Events in SQL Server | Microsoft Docs"
 ms.custom: ""
-ms.date: "04/17/2018"
+ms.date: "09/07/2018"
 ms.prod: sql
 ms.prod_service: "database-engine, sql-database"
 ms.reviewer: ""
@@ -82,7 +82,7 @@ SQL Server extended events can inter-operate with Event Tracing for Windows (ETW
 This ETW target processes *synchronously* the data it receives, whereas most targets process *asynchronously*.
 
 > [!NOTE]
-> Azure SQL Database does not support the ETW target. Nor does Azure SQL Database Managed Instance.
+> Azure SQL Database does not support the `etw_classic_sync_target target`.
 
 <!-- After OPS Versioning is live, the above !NOTE could be converted into a "3colon ZONE".  GeneMi = MightyPen. -->
 
@@ -151,7 +151,7 @@ The **event_file** target writes event session output from buffer to a disk file
 ::: moniker range="= azuresqldb-current || = azuresqldb-mi-current || = sqlallproducts-allversions"
 
 > [!NOTE]
-> Azure SQL Database supports the **event_file** target, but only by using a blob in Azure Storage for the output. SQL Database cannot store event output in a file on your local harddrive.
+> Azure SQL Database only supports storing `xel` files on Azure blob storage. 
 >
 > For an **event_file** code example particular to SQL Database (and to SQL Database Managed Instance), see [Event File target code for extended events in SQL Database](https://docs.microsoft.com/azure/sql-database/sql-database-xevent-code-event-file).
 

docs/relational-databases/extended-events/targets-for-extended-events-in-sql-server.md

@@ -2,7 +2,7 @@
 title: "Adaptive query processing in Microsoft SQL databases | Microsoft Docs | Microsoft Docs"
 description: "Adaptive query processing features to improve query performance in SQL Server (2017 and later), and Azure SQL Database."
 ms.custom: ""
-ms.date: "07/16/2018"
+ms.date: "09/07/2018"
 ms.prod: sql
 ms.prod_service: "database-engine, sql-database"
 ms.reviewer: ""
@@ -105,6 +105,9 @@ A USE HINT query hint takes precedence over a database scoped configuration or t
 ## Row mode memory grant feedback
 **Applies to:** SQL Database as a public preview feature
 
+> [!NOTE]
+> Row mode memory grant feedback is a public preview feature.  
+
 Row mode memory grant feedback expands on the batch mode memory grant feedback feature by adjusting memory grant sizes for both batch and row mode operators.  
 
 To enable the public preview of row mode memory grant feedback in Azure SQL Database, enable database compatibility level 150 for the database you are connected to when executing the query.
@@ -123,7 +126,8 @@ LastRequestedMemory shows the granted memory in Kilobytes (KB) from the prior qu
 | Yes: Adjusting | Memory grant feedback has been applied and may be further adjusted for the next execution. |
 | Yes: Stable | Memory grant feedback has been applied and granted memory is now stable, meaning that what was last granted for the previous execution is what was granted for the current execution. |
 
-The memory grant feedback plan attributes are not currently visible in SQL Server Management Studio graphical query execution plans, but for early testing you can view them using SET STATISTICS XML ON or the query_post_execution_showplan XEvent.  
+> [!NOTE]
+> The public preview row mode memory grant feedback plan attributes are visible in SQL Server Management Studio graphical query execution plans in versions 17.9 and higher. 
 
 ## Batch mode Adaptive Joins
 The batch mode Adaptive Joins feature enables the choice of a [Hash Join or Nested Loops Join](../../relational-databases/performance/joins.md) method to be deferred until **after** the first input has been scanned. The Adaptive Join operator defines a threshold that is used to decide when to switch to a Nested Loops plan. Your plan can therefore dynamically switch to a better join strategy during execution.

docs/relational-databases/performance/adaptive-query-processing.md

@@ -1,7 +1,7 @@
 ---
 title: "sys.routes (Transact-SQL) | Microsoft Docs"
 ms.custom: ""
-ms.date: "03/30/2018"
+ms.date: "09/07/2018"
 ms.prod: sql
 ms.prod_service: "database-engine"
 ms.component: "system-catalog-views"
@@ -31,8 +31,6 @@ monikerRange: "=azuresqldb-mi-current||>=sql-server-2016||=sqlallproducts-allver
 
   This catalog views contains one row per route. Service Broker uses routes to locate the network address for a service.   
 
-[!INCLUDE[ssMIlimitation](../../includes/sql-db-mi-limitation.md)]
-  
 |Column name|Data type|Description|  
 |-----------------|---------------|-----------------|  
 |**name**|**sysname**|Name of the route, unique within the database. Not NULLABLE.|  

docs/relational-databases/system-catalog-views/sys-routes-transact-sql.md

@@ -1,7 +1,7 @@
 ---
 title: "sys.servers (Transact-SQL) | Microsoft Docs"
 ms.custom: ""
-ms.date: "06/10/2016"
+ms.date: "09/07/2018"
 ms.prod: sql
 ms.prod_service: "database-engine"
 ms.component: "system-catalog-views"
@@ -11,10 +11,10 @@ ms.technology: system-objects
 ms.tgt_pltfrm: ""
 ms.topic: "language-reference"
 f1_keywords: 
-  - "servers_TSQL"
-  - "sys.servers_TSQL"
-  - "servers"
-  - "sys.servers"
+  - servers_TSQL
+  - sys.servers_TSQL
+  - servers
+  - sys.servers
 dev_langs: 
   - "TSQL"
 helpviewer_keywords: 
@@ -31,13 +31,11 @@ monikerRange: "=azuresqldb-mi-current||>=sql-server-2016||=sqlallproducts-allver
 
   Contains a row per linked or remote server registered, and a row for the local server that has **server_id** = 0.  
 
-[!INCLUDE[ssMIlimitation](../../includes/sql-db-mi-limitation.md)]  
-  
 |Column name|Data type|Description|  
 |-----------------|---------------|-----------------|  
 |**server_id**|**int**|Local ID of linked server.|  
-|**name**|**sysname**|When **server_id** = 0, this is the server name.<br /><br /> When **server_id** >0 , this is the local name of linked server.|  
-|**product**|**sysname**|Product name of the linked server. "SQL Server" indicates this is another instance of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)].|  
+|**name**|**sysname**|When **server_id** = 0, the returned value is the server name.<br /><br /> When **server_id** > 0, the returned value is the local name of linked server.|  
+|**product**|**sysname**|Product name of the linked server. A value of "SQL Server" indicates another instance of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)].|  
 |**provider**|**sysname**|OLE DB provider name for connecting to linked server.|  
 |**data_source**|**nvarchar(4000)**|OLE DB data source connection property.|  
 |**location**|**nvarchar(4000)**|OLE DB location connection property. NULL if none.|  
@@ -66,13 +64,12 @@ monikerRange: "=azuresqldb-mi-current||>=sql-server-2016||=sqlallproducts-allver
 
  Permissions are not required to view the local server (**server_id** = 0).  
 
- When you create a linked or remote server, [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] creates a default login mapping to the **public** server role. This means that by default, all logins can view all linked and remote servers. To restrict visibility to these servers, remove the default login mapping by executing [sp_droplinkedsrvlogin](../../relational-databases/system-stored-procedures/sp-droplinkedsrvlogin-transact-sql.md) and specifying NULL for the *locallogin* parameter.  
-  
- If the default login mapping is deleted, only users that have been explicitly added as a linked login or remote login can view the linked or remote servers for which they have a login. To view all linked and remote servers after the default login mapping is deleted requires the following permissions:  
+ When you create a linked or remote server, [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] creates a default login mapping to the **public** server role. Default login mapping means that all logins can view all linked and remote servers. To restrict visibility to these servers, remove the default login mapping by executing [sp_droplinkedsrvlogin](../../relational-databases/system-stored-procedures/sp-droplinkedsrvlogin-transact-sql.md) and specifying NULL for the *locallogin* parameter.  
 
--   ALTER ANY LINKED SERVER or ALTER ANY LOGIN ON SERVER  
+ If the default login mapping is deleted, only users that have been explicitly added as a linked login or remote login can view the linked or remote servers for which they have a login.  The following permissions are required to view all linked and remote servers after the default login mapping:  
 
--   Membership in the **setupadmin** or **sysadmin** fixed server roles  
+- `ALTER ANY LINKED SERVER` or `ALTER ANY LOGIN ON SERVER`  
+- Membership in the **setupadmin** or **sysadmin** fixed server roles  
 
 ## See Also  
  [Catalog Views &#40;Transact-SQL&#41;](../../relational-databases/system-catalog-views/catalog-views-transact-sql.md)   

docs/relational-databases/system-catalog-views/sys-servers-transact-sql.md

@@ -1,7 +1,7 @@
 ---
 title: "sp_configure (Transact-SQL) | Microsoft Docs"
 ms.custom: ""
-ms.date: "03/16/2016"
+ms.date: "09/07/2018"
 ms.prod: sql
 ms.prod_service: "database-engine, pdw"
 ms.component: "system-stored-procedures"
@@ -25,12 +25,10 @@ manager: craigg
 monikerRange: ">=aps-pdw-2016||=azuresqldb-mi-current||>=sql-server-2016||=sqlallproducts-allversions||>=sql-server-linux-2017"
 ---
 # sp_configure (Transact-SQL)
-[!INCLUDE[tsql-appliesto-ss2008-xxxx-xxxx-pdw-md](../../includes/tsql-appliesto-ss2008-asdbmi-xxxx-pwd-md.md)]
+[!INCLUDE[tsql-appliesto-ss2008-xxxx-xxxx-pdw-md](../../includes/tsql-appliesto-ss2008-asdbmi-xxxx-pdw-md.md)]
 
   Displays or changes global configuration settings for the current server.
 
-[!INCLUDE[ssMIlimitation](../../includes/sql-db-mi-limitation.md)]
-  
 > [!NOTE]  
 >  For database-level configuration options, see [ALTER DATABASE SCOPED CONFIGURATION (Transact-SQL)](../../t-sql/statements/alter-database-scoped-configuration-transact-sql.md). To configure Soft-NUMA, see [Soft-NUMA (SQL Server)](../../database-engine/configure-windows/soft-numa-sql-server.md).  
   

docs/relational-databases/system-stored-procedures/sp-configure-transact-sql.md

@@ -1,7 +1,7 @@
 ---
 title: "sp_dropserver (Transact-SQL) | Microsoft Docs"
 ms.custom: ""
-ms.date: "03/14/2017"
+ms.date: "09/07/2018"
 ms.prod: sql
 ms.prod_service: "database-engine"
 ms.component: "system-stored-procedures"
@@ -29,24 +29,21 @@ monikerRange: "=azuresqldb-mi-current||>=sql-server-2016||=sqlallproducts-allver
 
   Removes a server from the list of known remote and linked servers on the local instance of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)].  
 
-[!INCLUDE[ssMIlimitation](../../includes/sql-db-mi-limitation.md)]
-
- ![Topic link icon](../../database-engine/configure-windows/media/topic-link.gif "Topic link icon") [Transact-SQL Syntax Conventions](../../t-sql/language-elements/transact-sql-syntax-conventions-transact-sql.md)
+ ![link icon](../../database-engine/configure-windows/media/topic-link.gif "link icon") [Transact-SQL Syntax Conventions](../../t-sql/language-elements/transact-sql-syntax-conventions-transact-sql.md)
 
 ## Syntax  
 
-```  
-  
+```sql  
 sp_dropserver [ @server = ] 'server'   
      [ , [ @droplogins = ] { 'droplogins' | NULL} ]  
 ```  
 
 ## Arguments  
- [ **@server =** ] **'***server***'**  
+ *server*  
  Is the server to be removed. *server* is **sysname**, with no default. *server* must exist.  
 
- [ **@droplogins =** ] **'droplogins'** | NULL  
- Indicates that related remote and linked server logins for *server* must also be removed if **droplogins** is specified. **@droplogins** is **char(10)**, with a default of NULL.  
+ *droplogins*  
+ Indicates that related remote and linked server logins for *server* must also be removed if **droplogins** is specified. **`@droplogins`** is **char(10)**, with a default of NULL.  
 
 ## Return Code Values  
  0 (success) or 1 (failure)