Merge branch 'master' of https://github.com/MicrosoftDocs/sql-docs-pr into 20180508_Replication_ManagedInstance

Author: MikeRayMSFT

docs/analysis-services/instances/TOC.md

@@ -1,5 +1,6 @@
 # [Instance Management](analysis-services-instance-management.md)  
 # [Install](../../analysis-services/instances/install-windows/install-analysis-services.md)
+# [Verify Analysis Services cumulative update build version](analysis-services-component-version.md)
 # [Post-install Configuration](post-install-configuration-analysis-services.md)  
 ## [Configure the Windows Firewall](configure-the-windows-firewall-to-allow-analysis-services-access.md)  
 ## [Configure the service account](configure-service-accounts-analysis-services.md)  

docs/analysis-services/instances/analysis-services-component-version.md

@@ -0,0 +1,35 @@
+---
+title: "Verify SQL Server Analysis Services cumulative update build version | Microsoft Docs"
+ms.date: 07/11/2018
+ms.prod: sql
+ms.technology: analysis-services
+ms.custom:
+ms.topic: conceptual
+ms.author: owend
+ms.reviewer: owend
+author: minewiskan
+manager: kfile
+---
+
+# Verify Analysis Services cumulative update build version
+
+Beginning with SQL Server 2017, the Analysis Services build version number and SQL Server Database Engine build version number do not match. While both Analysis Services and the Database Engine use the same installer, the build systems each use are separate.
+
+ In some cases, it may be necessary to verify if a Cumulative Update (CU) build package has been applied and Analysis Services components have been updated. You can verify by comparing the build version numbers of Analysis Services component files installed on your computer with the  build version numbers for a particular CU.
+
+## Verify component file version
+
+To verify component file version, 
+
+1. Go to [SQL Server 2017 build versions](https://support.microsoft.com/help/4047329). 
+2. In **SQL Server 2017 cumulative update (CU) builds**, click the **Knowledge Base Number** for the build you want to verify.
+3. In the **Cumulative Update (#) for SQL Server 2017** article, in the **Cumulative Update package information** section, expand **Cumulative update package file information**.
+4. In the **SQL Server 2017 Analysis Services** table, check the File version for the **msmdsrv.exe** component file. If the CU has been applied, the file version number should match the msmdsrv.exe file installed on your computer.
+
+## See also  
+
+[Install SQL Server Servicing Updates](../../database-engine/install-windows/install-sql-server-servicing-updates.md)  
+
+[Update Center for Microsoft SQL Server](https://msdn.microsoft.com/library/ff803383.aspx)
+  
+  

docs/connect/odbc/linux-mac/release-notes.md

@@ -23,8 +23,6 @@ Ubuntu 18.04
 
 **Features Added**:
 
-UTF8 server encoding
-
 Data Classification for Azure SQL Database and SQL Server
 
 SQLBrowseConnect

docs/connect/odbc/windows/release-notes.md

@@ -24,8 +24,6 @@ manager: kenvh
 
 **Features Added**:
 
-UTF8 server encoding
-
 Data Classification for Azure SQL Database and SQL Server
 
 [Bug fixes](../bug-fixes.md)

docs/includes/ss-linux-cluster-availability-group-create-prereq.md

@@ -79,15 +79,6 @@ GO
 
 For more information about this XE session, see [AlwaysOn extended events](http://msdn.microsoft.com/library/dn135324.aspx).
 
-## Create a database mirroring endpoint user
-
-The following Transact-SQL script creates a login named `dbm_login` and a user named `dbm_user`. Update the script with a strong password. To create the database mirroring endpoint user, run the following command on all SQL Server instances:
-
-```SQL
-CREATE LOGIN dbm_login WITH PASSWORD = '**<1Sample_Strong_Password!@#>**';
-CREATE USER dbm_user FOR LOGIN dbm_login;
-```
-
 ## Create a certificate
 
 The SQL Server service on Linux uses certificates to authenticate communication between the mirroring endpoints. 
@@ -123,12 +114,11 @@ chown mssql:mssql dbm_certificate.*
 
 ## Create the certificate on secondary servers
 
-The following Transact-SQL script creates a master key and a certificate from the backup that you created on the primary SQL Server replica. The command also authorizes the user to access the certificate. Update the script with strong passwords. The decryption password is the same password that you used to create the .pvk file in a previous step. To create the certificate, run the following script on all secondary servers:
+The following Transact-SQL script creates a master key and a certificate from the backup that you created on the primary SQL Server replica. Update the script with strong passwords. The decryption password is the same password that you used to create the .pvk file in a previous step. To create the certificate, run the following script on all secondary servers:
 
 ```SQL
 CREATE MASTER KEY ENCRYPTION BY PASSWORD = '**<Master_Key_Password>**';
-CREATE CERTIFICATE dbm_certificate   
-    AUTHORIZATION dbm_user
+CREATE CERTIFICATE dbm_certificate
     FROM FILE = '/var/opt/mssql/data/dbm_certificate.cer'
     WITH PRIVATE KEY (
     FILE = '/var/opt/mssql/data/dbm_certificate.pvk',
@@ -140,7 +130,7 @@ CREATE CERTIFICATE dbm_certificate
 
 Database mirroring endpoints use the Transmission Control Protocol (TCP) to send and receive messages between the server instances that participate in database mirroring sessions or host availability replicas. The database mirroring endpoint listens on a unique TCP port number. 
 
-The following Transact-SQL script creates a listening endpoint named `Hadr_endpoint` for the availability group. It starts the endpoint and gives connection permission to the user that you created. Before you run the script, replace the values between `**< ... >**`. Optionally you can include an IP address `LISTENER_IP = (0.0.0.0)`. The listener IP address must be an IPv4 address. You can also use `0.0.0.0`. 
+The following Transact-SQL script creates a listening endpoint named `Hadr_endpoint` for the availability group. It starts the endpoint and gives connection permission to the certificate that you created. Before you run the script, replace the values between `**< ... >**`. Optionally you can include an IP address `LISTENER_IP = (0.0.0.0)`. The listener IP address must be an IPv4 address. You can also use `0.0.0.0`. 
 
 Update the following Transact-SQL script for your environment on all SQL Server instances: 
 
@@ -153,7 +143,6 @@ CREATE ENDPOINT [Hadr_endpoint]
 		ENCRYPTION = REQUIRED ALGORITHM AES
 		);
 ALTER ENDPOINT [Hadr_endpoint] STATE = STARTED;
-GRANT CONNECT ON ENDPOINT::[Hadr_endpoint] TO [dbm_login];
 ```
 
 >[!NOTE]
@@ -168,7 +157,6 @@ CREATE ENDPOINT [Hadr_endpoint]
 		ENCRYPTION = REQUIRED ALGORITHM AES
 		);
 ALTER ENDPOINT [Hadr_endpoint] STATE = STARTED;
-GRANT CONNECT ON ENDPOINT::[Hadr_endpoint] TO [dbm_login];
 ```
 
 The TCP port on the firewall must be open for the listener port.

docs/integration-services/ssis-how-to-create-an-etl-package.md

@@ -1,7 +1,7 @@
 ---
 title: "SSIS How to Create an ETL Package | Microsoft Docs"
 ms.custom: ""
-ms.date: "04/17/2018"
+ms.date: "07/11/2018"
 ms.prod: sql
 ms.prod_service: "integration-services"
 ms.reviewer: ""
@@ -34,22 +34,24 @@ When you install the sample data that the tutorial uses, you also install the co
 
 ## What is SQL Server Integration Services (SSIS)?
 
-[!INCLUDE[msCoName](../includes/msconame-md.md)][!INCLUDE[ssNoVersion](../includes/ssnoversion-md.md)] [!INCLUDE[ssISnoversion](../includes/ssisnoversion-md.md)] (SSIS) is a platform for building high-performance data integration solutions, including extraction, transformation, and load (ETL) packages for data warehousing. SSIS includes graphical tools and wizards for building and debugging packages; tasks for performing workflow functions such as FTP operations, executing SQL statements, and sending e-mail messages; data sources and destinations for extracting and loading data; transformations for cleaning, aggregating, merging, and copying data; a management service, the [!INCLUDE[ssISnoversion](../includes/ssisnoversion-md.md)] service for administering package execution and storage; and application programming interfaces (APIs) for programming the [!INCLUDE[ssISnoversion](../includes/ssisnoversion-md.md)] object model.  
+[!INCLUDE[msCoName](../includes/msconame-md.md)][!INCLUDE[ssNoVersion](../includes/ssnoversion-md.md)] [!INCLUDE[ssISnoversion](../includes/ssisnoversion-md.md)] (SSIS) is a platform for building high-performance data integration solutions, including extraction, transformation, and load (ETL) packages for data warehousing. SSIS includes graphical tools and wizards for building and debugging packages; tasks for performing workflow functions such as FTP operations, executing SQL statements, and sending e-mail messages; data sources and destinations for extracting and loading data; transformations for cleaning, aggregating, merging, and copying data; a management database, `SSISDB`, for administering package execution and storage; and application programming interfaces (APIs) for programming the [!INCLUDE[ssISnoversion](../includes/ssisnoversion-md.md)] object model.  
 
 ## What You Learn  
 The best way to become acquainted with the new tools, controls, and features available in [!INCLUDE[msCoName](../includes/msconame-md.md)] [!INCLUDE[ssNoVersion](../includes/ssnoversion-md.md)] [!INCLUDE[ssISnoversion](../includes/ssisnoversion-md.md)] is to use them. This tutorial walks you through [!INCLUDE[ssIS](../includes/ssis-md.md)] Designer to create a simple ETL package that includes looping, configurations, error flow logic, and logging.  
 
-## Requirements  
+## Prerequisites  
 This tutorial is intended for users familiar with fundamental database operations, but who have limited exposure to the new features available in [!INCLUDE[ssNoVersion](../includes/ssnoversion-md.md)] [!INCLUDE[ssISnoversion](../includes/ssisnoversion-md.md)].  
 
-> [!IMPORTANT]
-> Recently the sample files required to run this tutorial were no longer available online at their previous location. We apologize for the inconvenience. We have made the files available at a new location, and we have updated the download links in this article.
-
-To use this tutorial, your system must have the following components installed:  
+To run this tutorial, you have to have the following components installed:  
 
--   [!INCLUDE[ssNoVersion](../includes/ssnoversion-md.md)] with the **AdventureWorksDW2012** database. To download the **AdventureWorksDW2012** database, download `AdventureWorksDW2012.bak` from [AdventureWorks sample databases](https://github.com/Microsoft/sql-server-samples/releases/tag/adventureworks) and restore the backup.  
+-   [!INCLUDE[ssNoVersion](../includes/ssnoversion-md.md)] and [!INCLUDE[ssISnoversion](../includes/ssisnoversion-md.md)]. To install SQL Server and SSIS, see [Install Integration Services](install-windows/install-integration-services.md).
+
+-   The **AdventureWorksDW2012** sample database. To download the **AdventureWorksDW2012** database, download `AdventureWorksDW2012.bak` from [AdventureWorks sample databases](https://github.com/Microsoft/sql-server-samples/releases/tag/adventureworks) and restore the backup.  
+
+-   The **sample data** files. The sample data is included with the [!INCLUDE[ssIS](../includes/ssis-md.md)] lesson packages. To download the sample data and the lesson packages as a Zip file, see [SQL Server Integration Services Tutorial - Create a Simple ETL Package](https://www.microsoft.com/download/details.aspx?id=56827).
 
--   Sample data. The sample data is included with the [!INCLUDE[ssIS](../includes/ssis-md.md)] lesson packages. To download the sample data and the lesson packages as a Zip file, see [SQL Server Integration Services Tutorial - Create a Simple ETL Package](https://www.microsoft.com/download/details.aspx?id=56827).  
+    - Most of the files in the Zip file are read-only to prevent unintended changes. To write output to a file or to change it, you may have to turn off the read-only attribute in the file properties.
+    - The sample packages assume that the data files are located in the folder `C:\Program Files\Microsoft SQL Server\100\Samples\Integration Services\Tutorial\Creating a Simple ETL Package`. If you unzip the download to another location, you may have to update the file path in multiple places in the sample packages.
 
 ## Lessons in This Tutorial  
 [Lesson 1: Create a Project and Basic Package with SSIS](../integration-services/lesson-1-create-a-project-and-basic-package-with-ssis.md)  

docs/linux/sql-server-linux-availability-group-cluster-ubuntu.md

@@ -122,6 +122,7 @@ The following command creates a three-node cluster. Before you run the script, r
    sudo pcs cluster auth <node1> <node2> <node3> -u hacluster -p <password for hacluster>
    sudo pcs cluster setup --name <clusterName> <node1> <node2…> <node3>
    sudo pcs cluster start --all
+   sudo pcs cluster enable --all
    ```
 
    >[!NOTE]

docs/linux/sql-server-linux-configure-mssql-conf.md

@@ -54,7 +54,7 @@ ms.assetid: 06798dff-65c7-43e0-9ab3-ffb23374b322
 
 ## <a id="agent"></a> Enable SQL Server Agent
 
-The **sqlagent.enabled** setting enables [SQL Server Agent](sql-server-linux-run-sql-server-agent-job.md). By default, SQL Server Agent is disabled. If **sqlagent.enabled** is not present in the mssql.conf settings file, then SQL Server internally assumes that SQL Server Agent is enabled.
+The **sqlagent.enabled** setting enables [SQL Server Agent](sql-server-linux-run-sql-server-agent-job.md). By default, SQL Server Agent is disabled. If **sqlagent.enabled** is not present in the mssql.conf settings file, then SQL Server internally assumes that SQL Server Agent is disabled.
 
 To change this settings, use the following steps:
 

docs/relational-databases/in-memory-oltp/altering-memory-optimized-tables.md

@@ -1,4 +1,4 @@
----
+---
 title: "Altering Memory-Optimized Tables | Microsoft Docs"
 ms.custom: ""
 ms.date: "06/19/2017"
@@ -26,44 +26,11 @@ monikerRange: "= azuresqldb-current || >= sql-server-2016 || = sqlallproducts-al
 
 The ALTER TABLE syntax is used for making changes to the table schema, as well as for adding, deleting, and rebuilding indexes. Indexes are considered part of the table definition:  
 
--   The syntax ALTER TABLE … ADD/DROP/ALTER INDEX is supported only for memory-optimized tables.  
+-   The syntax ALTER TABLE ... ADD/DROP/ALTER INDEX is supported only for memory-optimized tables.  
 
 -   Without using an ALTER TABLE statement, the statements CREATE INDEX and DROP INDEX and ALTER INDEX are *not* supported for indexes on memory-optimized tables.  
 
- The following is the syntax for the ADD and DROP and ALTER INDEX clauses on the ALTER TABLE statement.  
-  
-```
-| ADD   
-     {   
-        <column_definition>  
-      | <table_constraint>  
-      | <table_index>    
-     } [ ,...n ]  
-  
-| DROP   
-     {  
-         [ CONSTRAINT ]   
-         {   
-              constraint_name   
-         } [ ,...n ]  
-         | COLUMN   
-         {  
-              column_name   
-         } [ ,...n ]  
-         | INDEX   
-         {  
-              index_name   
-         } [ ,...n ]  
-     } [ ,...n ]  
-  
-| ALTER INDEX index_name  
-     {   
-         REBUILD WITH ( <rebuild_index_option> )     
-     }  
-}  
-```  
-  
- The following types of alterations are supported.  
+The following types of alterations are supported:  
 
 -   Changing the bucket count