Merge pull request #7368 from MicrosoftDocs/master

9/19 AM Publish

Author: v-alje

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:  
 

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.|  

docs/reporting-services/application-integration/integrating-reporting-services-into-applications.md

@@ -1,6 +1,6 @@
 ---
 title: "Integrating Reporting Services into Applications | Microsoft Docs"
-ms.date: 10/19/2017
+ms.date: 09/18/2018
 ms.prod: reporting-services
 ms.prod_service: "reporting-services-native"
 ms.technology: application-integration
@@ -23,26 +23,26 @@ monikerRange: "= sql-server-2016 || = sqlallproducts-allversions"
 > [!NOTE]
 > Starting with SQL Server 2017 Reporting Services, REST API access is available for developing solutions. SOAP API access has been deprecated. For more information, see [Develop with the REST APIs for Reporting Services](../developer/rest-api.md).
   
- There are three options for integrating [!INCLUDE[ssRSnoversion](../../includes/ssrsnoversion-md.md)] into custom applications: the Report Server Web service, also known as the [!INCLUDE[ssRSnoversion](../../includes/ssrsnoversion-md.md)] SOAP API, the ReportViewer controls for [!INCLUDE[msCoName](../../includes/msconame-md.md)] [!INCLUDE[vsprvs](../../includes/vsprvs-md.md)], and URL access. Each option provides a different approach for integrating [!INCLUDE[ssRSnoversion](../../includes/ssrsnoversion-md.md)] into your applications.
+ There are three options for integrating [!INCLUDE[ssRSnoversion](../../includes/ssrsnoversion-md.md)] into custom applications: the Report Server Web service, also known as the [!INCLUDE[ssRSnoversion](../../includes/ssrsnoversion-md.md)] SOAP API, the Report Viewer controls for [!INCLUDE[msCoName](../../includes/msconame-md.md)] [!INCLUDE[vsprvs](../../includes/vsprvs-md.md)], and URL access. Each option provides a different approach for integrating [!INCLUDE[ssRSnoversion](../../includes/ssrsnoversion-md.md)] into your applications.
 
 ## Report server web service
 
  The Report Server Web service is the primary interface for developing against [!INCLUDE[ssRSnoversion](../../includes/ssrsnoversion-md.md)]. Whether you are developing code to manage your report catalog or developing code to render reports to a supported format, the Web service exposes all the necessary methods to integrate [!INCLUDE[ssRSnoversion](../../includes/ssrsnoversion-md.md)] into your applications. An example of one such application is Report Manager, which is included with [!INCLUDE[ssRSnoversion](../../includes/ssrsnoversion-md.md)]; it uses the Web service to manage the report server database.  
 
-## ReportViewer controls for Visual Studio
+## Report Viewer controls for Visual Studio
 
- The ReportViewer controls available for [!INCLUDE[vsprvs](../../includes/vsprvs-md.md)] are used for integrating report viewing into your applications. There are two controls: one for Windows Forms-based applications and one for Web Forms applications. Each control provides the capability for viewing reports that have been deployed to a report server as well as the ability to render reports that exist in an environment where a report server has not been installed.  
+ The Report Viewer controls available for [!INCLUDE[vsprvs](../../includes/vsprvs-md.md)] are used for integrating report viewing into your applications. There are two controls: one for Windows Forms-based applications and one for Web Forms applications. Each control provides the capability for viewing reports that have been deployed to a report server as well as the ability to render reports that exist in an environment where a report server has not been installed.  
 
 ## URL access  
- URL access is another option for integrating report viewing into your applications if the ReportViewer controls are not an option. In addition, URL access is useful for sending links to reports to users via e-mail.  
+ URL access is another option for integrating report viewing into your applications if the Report Viewer controls are not an option. In addition, URL access is useful for sending links to reports to users via e-mail.  
 
 ## In this section
 
  [Integrating Reporting Services Using SOAP](../../reporting-services/application-integration/integrating-reporting-services-using-soap.md)  
  Describes how to integrate [!INCLUDE[ssRSnoversion](../../includes/ssrsnoversion-md.md)] report navigation and management into your existing business applications using the Report Server Web service.  
 
- [Integrating Reporting Services Using the ReportViewer Controls](../../reporting-services/application-integration/integrating-reporting-services-using-reportviewer-controls.md)  
- Describes how to integrate report viewing into your existing applications using the ReportViewer controls.  
+ [Integrating Reporting Services Using the Report Viewer Controls](../../reporting-services/application-integration/integrating-reporting-services-using-reportviewer-controls.md)  
+ Describes how to integrate report viewing into your existing applications using the Report Viewer controls.  
 
  [Integrating Reporting Services Using URL Access](../../reporting-services/application-integration/integrating-reporting-services-using-url-access.md)  
  Describes how to integrate [!INCLUDE[ssRSnoversion](../../includes/ssrsnoversion-md.md)] report navigation into your existing business applications using URL access.  

docs/reporting-services/application-integration/integrating-reporting-services-using-reportviewer-controls-data-collection.md

@@ -1,6 +1,6 @@
 ---
 title: "Data collection in ReportViewer Control 2016 | Microsoft Docs"
-ms.date: 09/06/2016
+ms.date: 09/18/2018
 ms.prod: reporting-services
 ms.prod_service: "reporting-services-native"
 ms.technology: application-integration
@@ -13,20 +13,21 @@ author: markingmyname
 ms.author: maghan
 ---
 # Integrating Reporting Services Using ReportViewer Controls - Data Collection
-By default, the ReportViewer Control collects anonymous usage information in order for Microsoft to better understand how customers are making use of the control. By creating a better understanding of how customers are deploying and using the Viewer Control, future development can be focused on improvements that deliver the most value to customers.
 
-For an explanation of the user data collection and use practices for Microsoft SQL Server 2016 releases and any other products and services, please refer to this [privacy statement]((http://go.microsoft.com/fwlink/?LinkID=868444)).
+Anonymous usage data is collected by the control to better understand how customers make use of the product. Usage data enables future development to be focused on improvements that are most relevant to customers.
 
-## Opting out of telemetry
+An explanation of the data collection and usage practices of Microsoft SQL Server and Report Viewer are available in the [privacy statement]((http://go.microsoft.com/fwlink/?LinkID=868444)).
 
-Telemetry can be disabled programmatically through the “EnableTelemetry”. This can be done by editing the .aspx page hosting the control
+## Opting out of data collection
+
+Collection of usage data can be disabled through the ```EnableTelemetry``` property.
 
 ```
-\<rsweb:ReportViewer ID="ReportViewer1" runat="server" EnableTelemetry="false">
-\</rsweb:ReportViewer>
+<rsweb:ReportViewer ID="ReportViewer1" runat="server" EnableTelemetry="false">
+</rsweb:ReportViewer>
 ```
 
-Or, pragmatically before the control is rendered such as in the hosting page’s Page_Load call.
+Or pragmatically before the control is rendered.
 
 ```
 protected void Page_Load(object sender, EventArgs e)
@@ -36,8 +37,8 @@ protected void Page_Load(object sender, EventArgs e)
 ```
 ## See also
 
-[Using the WebForms ReportViewer Control](../../reporting-services/application-integration/using-the-webforms-reportviewer-control.md)  
-[Integrating Reporting Services Using the ReportViewer Controls](../../reporting-services/application-integration/integrating-reporting-services-using-reportviewer-controls.md) 
+[Using the WebForms Report Viewer Control](../../reporting-services/application-integration/using-the-webforms-reportviewer-control.md)  
+[Integrating Reporting Services Using the Report Viewer Controls](../../reporting-services/application-integration/integrating-reporting-services-using-reportviewer-controls.md)