Merge branch 'release-ignite-arc-data' of https://github.com/MicrosoftDocs/sql-docs-pr into release-ignite-arc-data

Author: MikeRayMSFT

docs/azdata/reference/reference-azdata-notebook.md

@@ -15,7 +15,7 @@ ms.technology: big-data-cluster
 
 [!INCLUDE[SQL Server 2019](../../includes/applies-to-version/sqlserver2019.md)]
 
-The following article provides reference for the `sql` commands in the `azdata` tool. For more information about other `azdata` commands, see [azdata reference](reference-azdata.md).
+The following article provides reference for the `notebook` commands in the `azdata` tool. For more information about other `azdata` commands, see [azdata reference](reference-azdata.md).
 
 ## Commands
 | Command | Description |

docs/connect/toc.yml

@@ -1 +1 @@
- SQL Data Warehouse 
+Azure Synapse Analytics (SQL Data Warehouse)

docs/includes/sssdw-md.md

@@ -49,6 +49,13 @@ For the **Decimal** data type, the precision and scale are determined by the sou
 > [!IMPORTANT]
 > The OData Source component does not support complex types, such as multiple-choice items, in SharePoint lists.
 
+> [!Note]
+> If the source only allows TLS 1.2 connection, you need to enforce TLS 1.2 on your machine through registry settings. In an elevated command prompt run the following commands:
+>
+> reg add HKLM\SOFTWARE\Microsoft\.NETFramework\v4.0.30319 /v SchUseStrongCrypto /t REG_DWORD /d 1 /reg:64
+>
+> reg add HKLM\SOFTWARE\Microsoft\.NETFramework\v4.0.30319 /v SchUseStrongCrypto /t REG_DWORD /d 1 /reg:32
+
 ## OData Format and Performance
  Most OData services can return results in multiple formats. You can specify the format of the result set by using the `$format` query option. Formats such as JSON and JSON Light are more efficient than ATOM or XML, and may give you better performance when transferring large amounts of data. The following table provides results from sample tests. As you can see, there was a 30-53% performance gain when switching from ATOM to JSON and a 67% performance gain when switching from ATOM to the new JSON light format (available in WCF Data Services 5.1).  
 

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

@@ -5,7 +5,7 @@ ms.custom: seo-lt-2019
 author: MikeRayMSFT
 ms.author: mikeray
 ms.reviewer: vanto
-ms.date: 01/10/2018
+ms.date: 09/01/2020
 ms.topic: tutorial
 ms.prod: sql
 ms.technology: linux
@@ -29,17 +29,17 @@ This tutorial demonstrates how to configure a highly available SQL Server instan
 
 Kubernetes 1.6 and later has support for [storage classes](https://kubernetes.io/docs/concepts/storage/storage-classes/), [persistent volume claims](https://kubernetes.io/docs/concepts/storage/storage-classes/#persistentvolumeclaims), and the [Azure disk volume type](https://github.com/kubernetes/examples/tree/master/staging/volumes/azure_disk). You can create and manage your SQL Server instances natively in Kubernetes. The example in this article shows how to create a [deployment](https://kubernetes.io/docs/concepts/workloads/controllers/deployment/) to achieve a high availability configuration similar to a shared disk failover cluster instance. In this configuration, Kubernetes plays the role of the cluster orchestrator. When a SQL Server instance in a container fails, the orchestrator bootstraps another instance of the container that attaches to the same persistent storage.
 
-![Diagram of Kubernetes SQL Server cluster](media/tutorial-sql-server-containers-kubernetes/kubernetes-sql.png)
+![SQL Server container on Kubernetes cluster](media/tutorial-sql-server-containers-kubernetes/kubernetes-sql.png)
 
 In the preceding diagram, `mssql-server` is a container in a [pod](https://kubernetes.io/docs/concepts/workloads/pods/pod/). Kubernetes orchestrates the resources in the cluster. A [replica set](https://kubernetes.io/docs/concepts/workloads/controllers/replicaset/) ensures that the pod is automatically recovered after a node failure. Applications connect to the service. In this case, the service represents a load balancer that hosts an IP address that stays the same after failure of the `mssql-server`.
 
 In the following diagram, the `mssql-server` container has failed. As the orchestrator, Kubernetes guarantees the correct count of healthy instances in the replica set, and starts a new container according to the configuration. The orchestrator starts a new pod on the same node, and `mssql-server` reconnects to the same persistent storage. The service connects to the re-created `mssql-server`.
 
-![Diagram of Kubernetes SQL Server cluster](media/tutorial-sql-server-containers-kubernetes/kubernetes-sql-after-pod-fail.png)
+![SQL Server pod fail on Kubernetes cluster](media/tutorial-sql-server-containers-kubernetes/kubernetes-sql-after-pod-fail.png)
 
 In the following diagram, the node hosting the `mssql-server` container has failed. The orchestrator starts the new pod on a different node, and `mssql-server` reconnects to the same persistent storage. The service connects to the re-created `mssql-server`.
 
-![Diagram of Kubernetes SQL Server cluster](media/tutorial-sql-server-containers-kubernetes/kubernetes-sql-after-node-fail.png)
+![SQL Server pod recover on Kubernetes cluster](media/tutorial-sql-server-containers-kubernetes/kubernetes-sql-after-node-fail.png)
 
 ## Prerequisites
 
@@ -168,10 +168,12 @@ In this step, create a manifest to describe the container based on the SQL Serve
          labels:
            app: mssql
        spec:
-         terminationGracePeriodSeconds: 10
+         terminationGracePeriodSeconds: 30
+         securityContext:
+           fsGroup: 10001
          containers:
          - name: mssql
-           image: mcr.microsoft.com/mssql/server:2017-latest
+           image: mcr.microsoft.com/mssql/server:2019-latest
            ports:
            - containerPort: 1433
            env:
@@ -221,10 +223,12 @@ In this step, create a manifest to describe the container based on the SQL Serve
      valueFrom:
        secretKeyRef:
          name: mssql
-         key: SA_PASSWORD 
+         key: SA_PASSWORD
      ```
 
-     When Kubernetes deploys the container, it refers to the secret named `mssql` to get the value for the password. 
+    When Kubernetes deploys the container, it refers to the secret named `mssql` to get the value for the password.
+
+   * `securityContext` : A securityContext defines privilege and access control settings for a Pod or Container, in this case it is specified at the pod level, so all containers ( in this case only one) adhere to that security context. In the security context we define the fsGroup with the value 10001 ( which is the GID for mssql group) means, all processes of the container are also part of the supplementary group ID 10001(mssql). The owner for volume /var/opt/mssql and any files created in that volume will be Group ID 10001(mssql group).
 
    >[!NOTE]
    >By using the `LoadBalancer` service type, the SQL Server instance is accessible remotely (via the internet) at port 1433.
@@ -266,7 +270,19 @@ In this step, create a manifest to describe the container based on the SQL Serve
 
    ```azurecli
    az aks browse --resource-group <MyResourceGroup> --name <MyKubernetesClustername>
-   ```  
+   ```
+
+1. You can also verify the container is running as non-root by running the following command:
+
+    ```azurecli
+    kubectl.exe exec <name of SQL POD> -it -- /bin/bash 
+    ```
+
+    and then run 'whoami' you should see the username as mssql. Which is a non-root user.
+
+    ```azurecli
+    whoami
+    ```
 
 ## Connect to the SQL Server instance
 
@@ -279,17 +295,17 @@ You can use the following applications to connect to the SQL Server instance.
 * [SSDT](https://docs.microsoft.com/sql/linux/sql-server-linux-develop-use-ssdt)
 
 * sqlcmd
-   
+
    To connect with `sqlcmd`, run the following command:
 
    ```cmd
    sqlcmd -S <External IP Address> -U sa -P "MyC0m9l&xP@ssw0rd"
    ```
 
    Replace the following values:
-      
-    - `<External IP Address>` with the IP address for the `mssql-deployment` service 
-    - `MyC0m9l&xP@ssw0rd` with your password
+
+  * `<External IP Address>` with the IP address for the `mssql-deployment` service 
+  * `MyC0m9l&xP@ssw0rd` with your password
 
 ## Verify failure and recovery
 
@@ -308,6 +324,7 @@ To verify failure and recovery, you can delete the pod. Do the following steps:
    ```azurecli
    kubectl delete pod mssql-deployment-0
    ```
+
    `mssql-deployment-0` is the value returned from the previous step for pod name. 
 
 Kubernetes automatically re-creates the pod to recover a SQL Server instance, and connect to the persistent storage. Use `kubectl get pods` to verify that a new pod is deployed. Use `kubectl get services` to verify that the IP address for the new container is the same. 
@@ -326,6 +343,4 @@ In this tutorial, you learned how to deploy SQL Server containers to a Kubernete
 ## Next steps
 
 > [!div class="nextstepaction"]
->[Introduction to Kubernetes](https://docs.microsoft.com/azure/aks/intro-kubernetes)
-
-
+>[Introduction to Kubernetes](https://docs.microsoft.com/azure/aks/intro-kubernetes)

docs/linux/tutorial-sql-server-containers-kubernetes.md

@@ -91,7 +91,7 @@ start_time                    end_time
 ```sql
 SELECT *  
 FROM sys.database_connection_stats
-WHERE start_time>='2011-09-25:12:00:00' and end_time<='2011-09-28 12:00:00';  
+WHERE start_time>='2011-09-25 12:00:00' and end_time<='2011-09-28 12:00:00';  
 ```  
 
 ## See Also