Merge pull request MicrosoftDocs#5996 from MicrosoftDocs/master

Publishing master to live for CU7 release

Author: rothja

docs/linux/sql-server-linux-overview.md

@@ -4,7 +4,7 @@ description: This article describes how SQL Server runs on Linux and provides in
 author: rothja 
 ms.author: jroth 
 manager: craigg
-ms.date: 04/17/2018
+ms.date: 05/24/2018
 ms.topic: article
 ms.prod: sql
 ms.component: ""

docs/linux/sql-server-linux-release-notes.md

@@ -4,7 +4,7 @@ description: This article contains the release notes and supported features for
 author: rothja 
 ms.author: jroth 
 manager: craigg
-ms.date: 04/20/2018
+ms.date: 05/24/2018
 ms.topic: article
 ms.prod: sql
 ms.component: ""
@@ -41,6 +41,7 @@ The following table lists the release history for SQL Server 2017.
 
 | Release | Version | Release date |
 |-----|-----|-----|
+| [CU7](#CU7) | 14.0.3026.27 | 5-2018 |
 | [CU6](#CU6) | 14.0.3025.34 | 4-2018 |
 | [CU5](#CU5) | 14.0.3023.8 | 3-2018 |
 | [CU4](#CU4) | 14.0.3022.28 | 2-2018 |
@@ -60,6 +61,20 @@ If you are updating existing SQL Server packages, run the appropriate update com
 - [Install SQL Server Integration Services](sql-server-linux-setup-ssis.md)
 - [Enable SQL Server Agent](sql-server-linux-setup-sql-agent.md)
 
+## <a id="CU7"></a> CU7 (May 2018)
+
+This is the Cumulative Update 7 (CU7) release of SQL Server 2017. The SQL Server engine version for this release is 14.0.3026.27. For information about the fixes and improvements in this release, see [https://support.microsoft.com/en-us/help/4229789](https://support.microsoft.com/en-us/help/4229789).
+
+### Package details
+
+For manual or offline package installations, you can download the RPM and Debian packages with the information in the following table:
+
+| Package | Package version | Downloads |
+|-----|-----|-----|
+| Red Hat RPM package | 14.0.3026.27-2 | [Engine RPM package](https://packages.microsoft.com/rhel/7/mssql-server-2017/mssql-server-14.0.3026.27-2.x86_64.rpm)</br>[High Availability RPM package](https://packages.microsoft.com/rhel/7/mssql-server-2017/mssql-server-ha-14.0.3026.27-2.x86_64.rpm)</br>[Full-text Search RPM package](https://packages.microsoft.com/rhel/7/mssql-server-2017/mssql-server-fts-14.0.3026.27-2.x86_64.rpm)</br>[SSIS package](https://packages.microsoft.com/rhel/7/mssql-server-2017/mssql-server-is-14.0.1000.169-1.x86_64.rpm) | 
+| SLES RPM package | 14.0.3026.27-2 | [mssql-server Engine RPM package](https://packages.microsoft.com/sles/12/mssql-server-2017/mssql-server-14.0.3026.27-2.x86_64.rpm)</br>[High Availability RPM package](https://packages.microsoft.com/sles/12/mssql-server-2017/mssql-server-ha-14.0.3026.27-2.x86_64.rpm)</br>[Full-text Search RPM package](https://packages.microsoft.com/sles/12/mssql-server-2017/mssql-server-fts-14.0.3026.27-2.x86_64.rpm) | 
+| Ubuntu 16.04 Debian package | 14.0.3026.27-2 | [Engine Debian package](https://packages.microsoft.com/ubuntu/16.04/mssql-server-2017/pool/main/m/mssql-server/mssql-server_14.0.3026.27-2_amd64.deb)</br>[High Availability Debian package](https://packages.microsoft.com/ubuntu/16.04/mssql-server-2017/pool/main/m/mssql-server-ha/mssql-server-ha_14.0.3026.27-2_amd64.deb)</br>[Full-text Search Debian package](https://packages.microsoft.com/ubuntu/16.04/mssql-server-2017/pool/main/m/mssql-server-fts/mssql-server-fts_14.0.3026.27-2_amd64.deb)<br/>[SSIS package](https://packages.microsoft.com/ubuntu/16.04/mssql-server-2017/pool/main/m/mssql-server-is/mssql-server-is_14.0.1000.169-1_amd64.deb) |
+
 ## <a id="CU6"></a> CU6 (April 2018)
 
 This is the Cumulative Update 6 (CU6) release of SQL Server 2017. The SQL Server engine version for this release is 14.0.3025.34. For information about the fixes and improvements in this release, see [https://support.microsoft.com/help/4101464](https://support.microsoft.com/help/4101464).

docs/relational-databases/performance-monitor/sql-server-memory-manager-object.md

@@ -35,7 +35,7 @@ manager: craigg
 |----------------------------------------|-----------------|  
 |**Connection Memory (KB)**|Specifies the total amount of dynamic memory the server is using for maintaining connections.|  
 |**Database Cache Memory (KB)**|Specifies the amount of memory the server is currently using for the database pages cache.|  
-|**External benefit of memory**|The external value of memory, in ms per page per ms, multiplied by 10 billion and truncated to an integer.| 
+|**External benefit of memory**| An internal estimation of the performance benefit from adding memory to a specific cache. It is used by the engine to balance memory usage between cache and is useful to support when troubleshooting cases with unexpected cache growth. The value is presented as an integer based on an internal calculation. | 
 |**Free Memory (KB)**|Specifies the amount of committed memory currently not used by the server.|  
 |**Granted Workspace Memory (KB)**|Specifies the total amount of memory currently granted to executing processes, such as hash, sort, bulk copy, and index creation operations.|  
 |**Lock Blocks**|Specifies the current number of lock blocks in use on the server (refreshed periodically). A lock block represents an individual locked resource, such as a table, page, or row.|  

docs/relational-databases/replication/configure-distribution-availability-group.md

@@ -1,7 +1,7 @@
 ---
 title: "Configure SQL Server distribution database in availability group | Microsoft Docs"
 ms.custom: ""
-ms.date: "04/19/2018"
+ms.date: "05/23/2018"
 ms.prod: sql
 ms.reviewer: ""
 ms.suite: "sql"
@@ -71,7 +71,6 @@ After a distribution database in the AG is configured based on the steps describ
 - Make changes to distributor or distribution database properties in all replicas participating in distribution database AG.
 - Make replication jobs changes through msdb stored procedures or SQL Server Management Studio in all replicas participating in distribution database AG.
 - Configuring distributor on the publisher needs to be done with scripts. The replication wizard cannot be used. Replication wizards and property sheets for other purposes are supported.
-- Replication monitor and other replication UI that connects using the AG listener name, are not supported as of SQL Server 2017 CU 6. To administer replication agents associated with the distribution database in an AG, use job property and job history.
 - Configuring the AG for distribution databases can only be done through scripts.
 - Setting up distribution databases in an AG needs to be a new replication configuration. Switching an existing distribution database to an AG is not supported. Also once a distribution database is taken out an AG, it can no longer function as a valid distribution database and should be dropped.
 

docs/sql-operations-studio/release-notes.md

@@ -28,7 +28,7 @@ The *May Public Preview* is focused on stabilization and bug fixes. This build c
 
 - Announcing Redgate SQL Search extension available in Extension Manager.
 - Community Localization available for 10 languages: German, Spanish, French, Italian, Japanese, Korean, Portuguese, Russian, Simplified Chinese and Traditional Chinese.
-- GDPR-compliant build has reduced telemetry collection, improved opt-out experience and in-product links to Privacy Statement.
+- Reduced telemetry collection, improved opt-out experience and in-product links to Privacy Statement.
 - Extension Manager has improved Marketplace experience to easily discover community extensions.
 - SQL Agent extension Jobs and Job History view improvement.
 - Updates for whoisactive and Server Reports extensions.

docs/t-sql/statements/create-login-transact-sql.md

@@ -313,7 +313,7 @@ In SQL Database, login data required to authenticate a connection and server-lev
 Only the server-level principal login (created by the provisioning process) or members of the `loginmanager` database role in the master database can create new logins. For more information, see [Server-Level Roles](https://docs.microsoft.com/en-us/azure/sql-database/sql-database-manage-logins#groups-and-roles) and [ALTER SERVER ROLE](../../t-sql/statements/alter-server-role-transact-sql.md).https://docs.microsoft.com/en-us/azure/sql-database/sql-database-manage-logins#additional-server-level-administrative-roles.
 
 ## Logins
-- Must have **ALTER ANY LOGIN** permission on the server or membership in the **securityadmin** fixed server role. Only AAD account with **ALTER ANY LOGIN** permission on the server or membership in the securityadmin  permission can execute this command
+- Must have **ALTER ANY LOGIN** permission on the server or membership in the **securityadmin** fixed server role. Only Azure Active Directory (Azure AD) account with **ALTER ANY LOGIN** permission on the server or membership in the securityadmin  permission can execute this command
 - Must be a member of Azure AD within the same directory used for Azure SQL logical server
 
 ## After creating a login