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

Author: MikeRayMSFT

docs/database-engine/availability-groups/windows/upgrading-always-on-availability-group-replica-instances.md

@@ -39,7 +39,7 @@ ms.workload: "On Demand"
 -   [Hardware and Software Requirements for Installing SQL Server 2016](../../../sql-server/install/hardware-and-software-requirements-for-installing-sql-server.md):  Review the software requirements for installing [!INCLUDE[ssCurrent](../../../includes/sscurrent-md.md)]. If additional software is required, install it on each node before you begin the upgrade process to minimize any downtime.  
 
 > [!NOTE]  
->  Mixing versions of SQL Server in the same AG is not supported. To migrate to a new version using availablity groups, the only supported method is a distributed availability group which is in SQL Server 2016 Enterprise Edition or later.
+>  Mixing versions of SQL Server in the same AG is not supported outside of a rolling upgrade which upgrades the replicas in place. This means a higher version of SQL Server cannot be added as a new replica to an existing AG. For example, a SQL Server 2017 replica cannot be added to an existing SQL Server 2016 AG. To migrate to a new version of SQL Server using availablity groups, the only supported method is a distributed availability group which is in SQL Server 2016 Enterprise Edition or later.
 
 ## Rolling Upgrade Best Practices for Always On Availability Groups  
  The following best practices should be observed when performing server upgrades or updates in order to minimize downtime and data loss for your availability groups:  

docs/integration-services/data-flow/odbc-flow-components.md

@@ -22,7 +22,7 @@ ms.workload: "Inactive"
 # ODBC Flow Components
   This topic describes the concepts necessary for creating an ODBC data flow using [!INCLUDE[ssISCurrent](../../includes/ssiscurrent-md.md)]  
 
- The Connector for Open Database Connectivity (ODBC) by Attunity for [!INCLUDE[ssISCurrent](../../includes/ssiscurrent-md.md)] helps SSIS developers easily create packages that load and unload data from ODBC-supported databases.  
+ The Connector for Open Database Connectivity (ODBC) for [!INCLUDE[ssISCurrent](../../includes/ssiscurrent-md.md)] helps SSIS developers easily create packages that load and unload data from ODBC-supported databases.  
 
  The ODBC Connector is designed to achieve optimal performance when loading data into or unloading data from an ODBC-supported database in the context of [!INCLUDE[ssISCurrent](../../includes/ssiscurrent-md.md)].  
 

docs/integration-services/data-flow/odbc-source.md

@@ -51,7 +51,7 @@ ms.workload: "Inactive"
  Depending on the error behavior setting, the ODBC source supports returning errors (data conversion, truncation) that occur during the extraction process in the error output. For more information, see [ODBC Destination Editor (Connection Manager Page)](../../integration-services/data-flow/odbc-destination-editor-connection-manager-page.md).  
 
 ## Data Type Support  
- For information about the data types supported by the ODBC source, see Connector for Open Database Connectivity (ODBC) by Attunity.  
+ For information about the data types supported by the ODBC source, see Connector for Open Database Connectivity (ODBC).  
 
 ## Extract Options  
  The ODBC source operates in either **Batch** or **Row-by-Row** mode. The mode used is determined by the **FetchMethod** property. The following list describes the modes.  

docs/integration-services/extending-packages-scripting/task/connecting-to-data-sources-in-the-script-task.md

@@ -58,14 +58,14 @@ ms.workload: "On Demand"
     Public Sub Main()
 
         Dim myADONETConnection As SqlClient.SqlConnection =
-        DirectCast(Dts.Connections("Test ADO.NET Connection").AcquireConnection(Dts.Transaction),
-            SqlClient.SqlConnection)
+            DirectCast(Dts.Connections("Test ADO.NET Connection").AcquireConnection(Dts.Transaction),
+                SqlClient.SqlConnection)
         MsgBox(myADONETConnection.ConnectionString,
             MsgBoxStyle.Information, "ADO.NET Connection")
 
         Dim myFlatFileConnection As String =
-        DirectCast(Dts.Connections("Test Flat File Connection").AcquireConnection(Dts.Transaction),
-            String)
+            DirectCast(Dts.Connections("Test Flat File Connection").AcquireConnection(Dts.Transaction),
+                String)
         MsgBox(myFlatFileConnection, MsgBoxStyle.Information, "Flat File Connection")
 
         Dts.TaskResult = ScriptResults.Success

docs/integration-services/integration-services-features-supported-by-the-editions-of-sql-server.md

@@ -59,7 +59,7 @@ The SQL Server Evaluation edition is available for a 180-day trial period.
 |-------------|----------------|--------------|---------|------------------------------------|------------------------|  
 |Built-in data source connectors|Yes|Yes|||| 
 |Built in tasks and transformations|Yes|Yes||||  
-|ODBC source and destination by Attunity|Yes|Yes|||| 
+|ODBC source and destination |Yes|Yes|||| 
 |Azure data source connectors and tasks|Yes|Yes||||  
 |Hadoop/HDFS connectors and tasks|Yes|Yes||||  
 |Basic data profiling tools|Yes|Yes|||| 

docs/integration-services/lift-shift/ssis-azure-connect-with-windows-auth.md

@@ -1,5 +1,5 @@
 ---
-title: "Connect to on-premises data sources and Azure file shares with Windows Authentication | Microsoft Docs"
+title: "Connect to data sources and file shares with Windows Authentication | Microsoft Docs"
 ms.date: "11/27/2017"
 ms.topic: "article"
 ms.prod: "sql-non-specified"

docs/integration-services/lift-shift/ssis-azure-lift-shift-ssis-packages-overview.md

@@ -64,7 +64,7 @@ For more info about prerequisites in Azure, see [Lift and shift SQL Server Integ
 
 ## SSIS features on Azure
 
-When you provision an instance of SQL Database to host SSISDB, the Azure Feature Pack for SSIS and the Access Redistributable are also installed. These components provide connectivity to **Excel and Access** files and to various **Azure** data sources, in addition to the data sources supported by the built-in components. You can't install **third-party components** for SSIS (including third-party components from Microsoft, such as the Attunity and SAP BI components) at this time.
+When you provision an instance of SQL Database to host SSISDB, the Azure Feature Pack for SSIS and the Access Redistributable are also installed. These components provide connectivity to **Excel and Access** files and to various **Azure** data sources, in addition to the data sources supported by the built-in components. You can't install **third-party components** for SSIS at this time (including third-party components from Microsoft, such as the Oracle and Teradata components by Attunity and the SAP BI components).
 
 The **name of the SQL Database** that hosts SSISDB becomes the first part of the four-part name to use when you deploy and manage packages from SSDT and SSMS - `<sql_database_name>.database.windows.net`.
 

docs/integration-services/system-stored-procedures/catalog-create-execution-ssisdb-database.md

@@ -58,8 +58,14 @@ catalog.create_execution [@folder_name = folder_name
  [@runinscaleout =] *runinscaleout*  
  Indicate whether the execution is in Scale Out. Use the value of 1 to execute the package in Scale Out. Use the value of 0 to execute the package without Scale Out. This parameter is optional. If not specified, its value is set to DEFAULT_EXECUTION_MODE in [SSISDB].[catalog].[catalog_properties]. The *runinscaleout* is **bit**. 
 
- [@useanyworker =] *useanyworker*  
-  Indicate whether any Scale Out Worker is allowed to do the execution. Use the value of 1 to execute the package with any Scale Out Worker. Use the value of 0 to indicate that not all Scale Out Workers are allowed to execute the package. This parameter is optional. If not specified, its value is set to 1. The *useanyworker* is **bit**. 
+[@useanyworker =] *useanyworker*  
+Indicate whether any Scale Out Worker is allowed to do the execution.
+
+-   Use the value of 1 to execute the package with any Scale Out Worker. When you set `@useanyworker` to true, any worker whose maximum task count (as specified in the worker configuration file) is not yet reached is available to run the package.
+
+-   Use the value of 0 to indicate that not all Scale Out Workers are allowed to execute the package. When you set `@useanyworker` to false, you have to specify the workers that are allowed to run the package by using Scale Out Manager or by calling the stored procedure `[catalog].[add_execution_worker]`.
+
+This parameter is optional. If not specified, its value is set to 1. The *useanyworker* is **bit**. 
 
  [@execution_id =] *execution_id*  
  Returns the unique identifier for an instance of execution. The *execution_id* is **bigint**.  

docs/linux/sql-server-linux-create-availability-group.md

@@ -21,6 +21,8 @@ ms.workload: "On Demand"
 [!INCLUDE[tsql-appliesto-sslinux-only](../includes/tsql-appliesto-sslinux-only.md)]
 
 This tutorial covers how to create and configure an availability group (AG) for [!INCLUDE[ssnoversion-md](../includes/ssnoversion-md.md)] on Linux. Unlike [!INCLUDE[sssql15-md](../includes/sssql15-md.md)] and earlier on Windows, you can enable AGs with or without creating the underlying Pacemaker cluster first. Integration with the cluster, if needed, is not done until later.
+
+The tutorial includes the following tasks:
 
 > [!div class="checklist"]
 > * Enable availability groups.
@@ -589,12 +591,10 @@ The AG resource that is created is a special kind of resource called a clone. Th
     sudo pcs resource create <NameForAGResource> ocf:mssql:ag ag_name=<AGName> --master meta notify=true
     ```
 
->[NOTE]
->On RHEL 7.4, you may encounter a warning with the use of --master. To avoid this, use the following syntax:
-    ```bash
-    sudo pcs resource create <NameForAGResource> ocf:mssql:ag ag_name=<AGName> master notify=true
-    ```
-
+    >[!NOTE]
+    >On RHEL 7.4, you may encounter a warning with the use of --master. To avoid this, use
+    >`sudo pcs resource create <NameForAGResource> ocf:mssql:ag ag_name=<AGName> master notify=true`
+   
     **SUSE Linux Enterprise Server (SLES)**
 
     ```bash
@@ -644,8 +644,7 @@ The AG resource that is created is a special kind of resource called a clone. Th
     ```bash
     sudo pcs constraint colocation add <NameForIPResource> <NameForAGResource>-master INFINITY with-rsc-role=Master
     ```
-   
-    
+
     **SLES**
 
     ```bash
@@ -687,5 +686,5 @@ In this tutorial, you learned how to create and configure an availability group
 For most AG administration tasks, including upgrades and failing over, see:
 
 > [!div class="nextstepaction"]
-> [Operate HA availability group for SQL Server on Linux](sql-server-linux-availability-group-failover-ha.md).
+> [Operate HA availability group for SQL Server on Linux](sql-server-linux-availability-group-failover-ha.md)
 

docs/linux/sql-server-linux-shared-disk-cluster-red-hat-7-configure.md

@@ -175,7 +175,7 @@ On the NFS Server do the following:
 
 Do the following steps on all cluster nodes.
 
-1.	From the NFS server, install `nfs-utils`
+1.	Install `nfs-utils`
 
    ```bash
    sudo yum -y install nfs-utils
@@ -209,7 +209,7 @@ For additional information about using NFS, see the following resources:
 1.  **On the primary node only**, save the database files to a temporary location.The following script, creates a new temporary directory, copies the database files to the new directory, and removes the old database files. As SQL Server runs as local user mssql, you need to make sure that after data transfer to the mounted share, local user has read-write access to the share. 
 
    ``` 
-   $ su mssql
+   $ sudo su mssql
    $ mkdir /var/opt/mssql/tmp
    $ cp /var/opt/mssql/data/* /var/opt/mssql/tmp
    $ rm /var/opt/mssql/data/*
@@ -235,9 +235,9 @@ For additional information about using NFS, see the following resources:
 1.  Copy the database and log files that you saved to `/var/opt/mssql/tmp` to the newly mounted share `/var/opt/mssql/data`. This only needs to be done **on the primary node**. Make sure that you give read write permissions to 'mssql' local user.
 
    ``` 
-   $ chown mssql /var/opt/mssql/data
-   $ chgrp mssql /var/opt/mssql/data
-   $ su mssql
+   $ sudo chown mssql /var/opt/mssql/data
+   $ sudo chgrp mssql /var/opt/mssql/data
+   $ sudo su mssql
    $ cp /var/opt/mssql/tmp/* /var/opt/mssql/data/
    $ rm /var/opt/mssql/tmp/*
    $ exit
@@ -260,8 +260,8 @@ At this point both instances of SQL Server are configured to run with the databa
 
    ```bash
    sudo touch /var/opt/mssql/secrets/passwd
-   sudo echo '<loginName>' >> /var/opt/mssql/secrets/passwd
-   sudo echo '<loginPassword>' >> /var/opt/mssql/secrets/passwd
+   echo '<loginName>' | sudo tee -a /var/opt/mssql/secrets/passwd
+   echo '<loginPassword>' | sudo tee -a /var/opt/mssql/secrets/passwd
    sudo chown root:root /var/opt/mssql/secrets/passwd 
    sudo chmod 600 /var/opt/mssql/secrets/passwd    
    ```