Merge branch 'release-dallas' of https://github.com/MicrosoftDocs/sql-docs-pr into cardinality

Author: markingmyname

.openpublishing.redirection.json

@@ -41190,11 +41190,6 @@
       "redirect_url": "/sql/big-data-cluster/view-cluster-status#big-data-clusters-troubleshooting-resources",
       "redirect_document_id": true
     },
-    {
-      "source_path": "docs/big-data-cluster/release-notes-cumulative-update-16.md",
-      "redirect_url": "/sql/big-data-cluster/release-notes-big-data-cluster",
-      "redirect_document_id": false
-    },
     {
       "source_path": "docs/big-data-cluster/configure-cluster.md",
       "redirect_url": "/sql/big-data-cluster/configure-bdc-overview",

azure-sql/database/automated-backups-overview.md

@@ -538,7 +538,7 @@ To view backup and data storage metrics in the Azure portal, follow these steps:
 Backup storage consumption for a Hyperscale database depends on the retention period, choice of region, backup storage redundancy and workload type. Consider some of the following tuning techniques to reduce your backup storage consumption for a Hyperscale database:
 
 - Reduce the [backup retention period](#change-the-short-term-retention-policy-using-the-azure-portal) to the minimum possible for your needs.
-- Avoid doing large write-operations, such as index maintenance, more frequently than you need to. For index maintenance recommendations, see [Optimize index maintenance to improve query performance and reduce resource consumption](/sql/relational-databases/indexes/reorganize-and-rebuild-indexes.md).
+- Avoid doing large write-operations, such as index maintenance, more frequently than you need to. For index maintenance recommendations, see [Optimize index maintenance to improve query performance and reduce resource consumption](/sql/relational-databases/indexes/reorganize-and-rebuild-indexes).
 - For large data-load operations, consider using data compression when appropriate.
 - Use the `tempdb` database instead of permanent tables in your application logic to store temporary results and/or transient data.
 - Use locally-redundant or zone-redundant backup storage when geo-restore capability is unnecessary (for example: dev/test environments). 

azure-sql/database/connect-github-actions-sql-db.md

@@ -7,7 +7,7 @@ ms.service: sql-database
 ms.subservice: connect
 ms.topic: quickstart
 ms.author: jukullam
-ms.date: 05/05/2021
+ms.date: 05/10/2022
 ms.custom: github-actions-azure, mode-other
 ms.reviewer: kendralittle, mathoma
 ---
@@ -18,7 +18,7 @@ Get started with [GitHub Actions](https://docs.github.com/en/actions) by using a
 
 ## Prerequisites
 
-You will need: 
+You will need:
 - An Azure account with an active subscription. [Create an account for free](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
 - A GitHub repository with a dacpac package (`Database.dacpac`). If you don't have a GitHub account, [sign up for free](https://github.com/join).  
 - An Azure SQL Database.
@@ -33,11 +33,13 @@ The file has two sections:
 
 |Section  |Tasks  |
 |---------|---------|
-|**Authentication** | 1. Define a service principal. <br /> 2. Create a GitHub secret. |
+|**Authentication** | 1.1. Generate deployment credentials. |
 |**Deploy** | 1. Deploy the database. |
 
 ## Generate deployment credentials
 
+# [Service principal](#tab/userlevel)
+
 You can create a [service principal](/azure/active-directory/develop/app-objects-and-service-principals) with the [az ad sp create-for-rbac](/cli/azure/ad/sp#az-ad-sp-create-for-rbac) command in the [Azure CLI](/cli/azure/). Run this command with [Azure Cloud Shell](https://shell.azure.com/) in the Azure portal or by selecting the **Try it** button.
 
 Replace the placeholders `server-name` with the name of your SQL server hosted on Azure. Replace the `subscription-id` and `resource-group` with the subscription ID and resource group connected to your SQL server.  
@@ -63,6 +65,27 @@ The output is a JSON object with the role assignment credentials that provide ac
 > [!IMPORTANT]
 > It is always a good practice to grant minimum access. The scope in the previous example is limited to the specific server and not the entire resource group.
 
+# [OpenID Connect](#tab/openid)
+
+You need to provide your application's **Client ID**, **Tenant ID**, and **Subscription ID** to the login action. These values can either be provided directly in the workflow or can be stored in GitHub secrets and referenced in your workflow. Saving the values as GitHub secrets is the more secure option.
+
+1. Open your GitHub repository and go to **Settings**.
+
+1. Select **Settings > Secrets > New secret**.
+
+1. Create secrets for `AZURE_CLIENT_ID`, `AZURE_TENANT_ID`, and `AZURE_SUBSCRIPTION_ID`. Use these values from your Active Directory application for your GitHub secrets:
+
+    |GitHub Secret  | Active Directory Application  |
+    |---------|---------|
+    |AZURE_CLIENT_ID     |      Application (client) ID   |
+    |AZURE_TENANT_ID     |     Directory (tenant) ID    |
+    |AZURE_SUBSCRIPTION_ID     |     Subscription ID    |
+
+1. Save each secret by selecting **Add secret**.
+
+---
+
+
 ## Copy the SQL connection string 
 
 In the Azure portal, go to your Azure SQL Database and open **Settings** > **Connection strings**. Copy the **ADO.NET** connection string. Replace the placeholder values for `your_database` and `your_password`. The connection string will look similar to this output. 
@@ -75,6 +98,8 @@ You'll use the connection string as a GitHub secret.
 
 ## Configure the GitHub secrets
 
+# [Service principal](#tab/userlevel)
+
 1. In [GitHub](https://github.com/), browse your repository.
 
 1. Select **Settings > Secrets > New secret**.
@@ -93,6 +118,25 @@ You'll use the connection string as a GitHub secret.
 
 1. Paste the connection string value into the secret's value field. Give the secret the name `AZURE_SQL_CONNECTION_STRING`.
 
+# [OpenID Connect](#tab/openid)
+
+You need to provide your application's **Client ID**, **Tenant ID**, and **Subscription ID** to the login action. These values can either be provided directly in the workflow or can be stored in GitHub secrets and referenced in your workflow. Saving the values as GitHub secrets is the more secure option.
+
+1. Open your GitHub repository and go to **Settings**.
+
+1. Select **Settings > Secrets > New secret**.
+
+1. Create secrets for `AZURE_CLIENT_ID`, `AZURE_TENANT_ID`, and `AZURE_SUBSCRIPTION_ID`. Use these values from your Active Directory application for your GitHub secrets:
+
+    |GitHub Secret  | Active Directory Application  |
+    |---------|---------|
+    |AZURE_CLIENT_ID     |      Application (client) ID   |
+    |AZURE_TENANT_ID     |     Directory (tenant) ID    |
+    |AZURE_SUBSCRIPTION_ID     |     Subscription ID    |
+
+1. Save each secret by selecting **Add secret**.
+
+---
 
 ## Add your workflow
 
@@ -107,21 +151,23 @@ You'll use the connection string as a GitHub secret.
 
     on:
     push:
-        branches: [ master ]
+        branches: [ main ]
     pull_request:
-        branches: [ master ]
+        branches: [ main ]
     ```
 
-1. Rename your workflow `SQL for GitHub Actions` and add the checkout and login actions. These actions will checkout your site code and authenticate with Azure using the `AZURE_CREDENTIALS` GitHub secret you created earlier. 
+1. Rename your workflow `SQL for GitHub Actions` and add the checkout and login actions. These actions will check out your site code and authenticate with Azure using the `AZURE_CREDENTIALS` GitHub secret you created earlier.
+
+    # [Service principal](#tab/userlevel)
 
     ```yaml
     name: SQL for GitHub Actions
 
     on:
     push:
-        branches: [ master ]
+        branches: [ main ]
     pull_request:
-        branches: [ master ]
+        branches: [ main ]
 
     jobs:
     build:
@@ -133,6 +179,31 @@ You'll use the connection string as a GitHub secret.
             creds: ${{ secrets.AZURE_CREDENTIALS }}
     ```
 
+    # [OpenID Connect](#tab/openid)
+
+    ```yaml
+    name: SQL for GitHub Actions
+
+    on:
+    push:
+        branches: [ main ]
+    pull_request:
+        branches: [ main ]
+
+    jobs:
+    build:
+        runs-on: windows-latest
+        steps:
+        - uses: actions/checkout@v1
+        - uses: azure/login@v1
+        with:
+            client-id: ${{ secrets.AZURE_CLIENT_ID }}
+            tenant-id: ${{ secrets.AZURE_TENANT_ID }}
+            subscription-id: ${{ secrets.AZURE_SUBSCRIPTION_ID }}
+    ```
+  
+  ---
+
 1. Use the Azure SQL Deploy action to connect to your SQL instance. Replace `SQL_SERVER_NAME` with the name of your server. You should have a dacpac package (`Database.dacpac`) at the root level of your repository. 
 
     ```yaml
@@ -141,18 +212,20 @@ You'll use the connection string as a GitHub secret.
         server-name: SQL_SERVER_NAME
         connection-string: ${{ secrets.AZURE_SQL_CONNECTION_STRING }}
         dacpac-package: './Database.dacpac'
-    ``` 
+    ```
 
-1. Complete your workflow by adding an action to logout of Azure. Here is the completed workflow. The file will appear in the `.github/workflows` folder of your repository.
+1. Complete your workflow by adding an action to logout of Azure. Here's the completed workflow. The file will appear in the `.github/workflows` folder of your repository.
+
+    # [Service principal](#tab/userlevel)
 
     ```yaml
     name: SQL for GitHub Actions
 
     on:
     push:
-        branches: [ master ]
+        branches: [ main ]
     pull_request:
-        branches: [ master ]
+        branches: [ main ]
 
 
     jobs:
@@ -176,6 +249,42 @@ You'll use the connection string as a GitHub secret.
          az logout
     ```
 
+    # [OpenID Connect](#tab/openid)
+
+    ```yaml
+    name: SQL for GitHub Actions
+
+    on:
+    push:
+        branches: [ main ]
+    pull_request:
+        branches: [ main ]
+
+
+    jobs:
+    build:
+        runs-on: windows-latest
+        steps:
+        - uses: actions/checkout@v1
+        - uses: azure/login@v1
+        with:
+            client-id: ${{ secrets.AZURE_CLIENT_ID }}
+            tenant-id: ${{ secrets.AZURE_TENANT_ID }}
+            subscription-id: ${{ secrets.AZURE_SUBSCRIPTION_ID }}
+    - uses: azure/sql-action@v1
+      with:
+        server-name: SQL_SERVER_NAME
+        connection-string: ${{ secrets.AZURE_SQL_CONNECTION_STRING }}
+        dacpac-package: './Database.dacpac'
+
+        # Azure logout 
+    - name: logout
+      run: |
+         az logout
+    ```
+
+    ---
+
 ## Review your deployment
 
 1. Go to **Actions** for your GitHub repository. 

azure-sql/database/connect-query-ruby.md

@@ -1,20 +1,24 @@
 ---
-title: Use Ruby to query
-description: This topic shows you how to use Ruby to create a program that connects to a database and query it using Transact-SQL statements.
-titleSuffix: Azure SQL Database & SQL Managed Instance
+title: Use Ruby with Azure SQL Database or SQL Managed Instance
+description: This quickstart shows you how to use Ruby to create a program that connects to a database and queries it using Transact-SQL statements.
 services: sql-database
 ms.service: sql-database
 ms.subservice: connect
-ms.custom: sqldbrb=2, mode-other
+ms.custom:
+- sqldbrb=2
+- mode-other
+- kr2b-contr-experiment
 ms.devlang: ruby
 ms.topic: quickstart
 author: dzsquared
 ms.author: drskwier
 ms.reviewer: kendralittle, mathoma
-ms.date: 05/29/2020
+ms.date: 05/10/2022
 monikerRange: "=azuresql||=azuresql-db||=azuresql-mi"
 ---
+
 # Quickstart: Use Ruby to query a database in Azure SQL Database or Azure SQL Managed Instance
+
 [!INCLUDE[appliesto-sqldb-sqlmi](../includes/appliesto-sqldb-sqlmi.md)]
 
 This quickstart demonstrates how to use [Ruby](https://www.ruby-lang.org) to connect to a database and query data with Transact-SQL statements.
@@ -25,7 +29,7 @@ To complete this quickstart, you need the following prerequisites:
 
 - A database. You can use one of these quickstarts to create and then configure the database:
 
-  | Action | SQL Database | SQL Managed Instance | SQL Server on Azure VM |
+  | Action | SQL Database | SQL Managed Instance | SQL Server on Azure Virtual Machines |
   |:--- |:--- |:---|:---|
   | Create| [Portal](single-database-create-quickstart.md) | [Portal](../managed-instance/instance-create-quickstart.md) | [Portal](../virtual-machines/windows/sql-vm-create-portal-quickstart.md)
   || [CLI](scripts/create-and-configure-database-cli.md) | [CLI](https://medium.com/azure-sqldb-managed-instance/working-with-sql-managed-instance-using-azure-cli-611795fe0b44) |
@@ -36,7 +40,7 @@ To complete this quickstart, you need the following prerequisites:
   |||Restore or import Adventure Works from a [BACPAC](database-import.md) file from [GitHub](https://github.com/Microsoft/sql-server-samples/tree/master/samples/databases/adventure-works)| Restore or import Adventure Works from a [BACPAC](database-import.md) file from [GitHub](https://github.com/Microsoft/sql-server-samples/tree/master/samples/databases/adventure-works)|
 
   > [!IMPORTANT]
-  > The scripts in this article are written to use the Adventure Works database. With a SQL Managed Instance, you must either import the Adventure Works database into an instance database or modify the scripts in this article to use the Wide World Importers database.
+  > The scripts in this article are written to use the Adventure Works database. With a SQL Managed Instance, either import the Adventure Works database into an instance database or modify the scripts in this article to use the Wide World Importers database.
   
 - Ruby and related software for your operating system:
 
@@ -48,26 +52,23 @@ To complete this quickstart, you need the following prerequisites:
 
 ## Get server connection information
 
-Get the connection information you need to connect to a database in Azure SQL Database. You'll need the fully qualified server name or host name, database name, and login information for the upcoming procedures.
+Get the information you need to connect to a database in Azure SQL Database. You'll need the fully qualified server name or host name, database name, and sign-in information for the upcoming procedures.
 
 1. Sign in to the [Azure portal](https://portal.azure.com/).
 
 2. Navigate to the **SQL databases**  or **SQL Managed Instances** page.
 
-3. On the **Overview** page, review the fully qualified server name next to **Server name** for a database in Azure SQL Database or the fully qualified server name (or IP address) next to **Host** for an Azure SQL Managed Instance or SQL Server on Azure VM. To copy the server name or host name, hover over it and select the **Copy** icon.
+3. On the **Overview** page, review the fully qualified server name next to **Server name** for a database in Azure SQL Database or the fully qualified server name (or IP address) next to **Host** for an Azure SQL Managed Instance or SQL Server on Virtual Machines. To copy the server name or host name, hover over it and select the **Copy** icon.
 
 > [!NOTE]
-> For connection information for SQL Server on Azure VM, see [Connect to a SQL Server instance](../virtual-machines/windows/sql-vm-create-portal-quickstart.md#connect-to-sql-server).
+> For connection information for SQL Server on Azure Virtual Machines, see [Connect to a SQL Server instance](../virtual-machines/windows/sql-vm-create-portal-quickstart.md#connect-to-sql-server).
 
 ## Create code to query your database in Azure SQL Database
 
 1. In a text or code editor, create a new file named *sqltest.rb*.
 
 1. Add the following code. Substitute the values from your database in Azure SQL Database for `<server>`, `<database>`, `<username>`, and `<password>`.
 
-   >[!IMPORTANT]
-   >The code in this example uses the sample AdventureWorksLT data, which you can choose as source when creating your database. If your database has different data, use tables from your own database in the SELECT query. 
-
    ```ruby
    require 'tiny_tds'
    server = '<server>.database.windows.net'
@@ -88,17 +89,21 @@ Get the connection information you need to connect to a database in Azure SQL Da
    end
    ```
 
+   >[!IMPORTANT]
+   >This example uses the sample AdventureWorksLT data, which you can choose as source when creating your database. If your database has different data, use tables from your own database in the SELECT query.
+
 ## Run the code
 
 1. At a command prompt, run the following command:
 
    ```bash
    ruby sqltest.rb
    ```
-   
-1. Verify that the top 20 Category/Product rows from your database are returned. 
+
+1. Verify that the top 20 Category/Product rows from your database are returned.
 
 ## Next steps
+
 - [Design your first database in Azure SQL Database](design-first-database-tutorial.md)
 - [GitHub repository for TinyTDS](https://github.com/rails-sqlserver/tiny_tds)
 - [Report issues or ask questions about TinyTDS](https://github.com/rails-sqlserver/tiny_tds/issues)

azure-sql/database/connectivity-architecture.md

@@ -105,7 +105,7 @@ Periodically, we will retire Gateways using old hardware and migrate the traffic
 | South Africa West    | 102.133.24.0       | 102.133.25.32/29 |
 | South Central US     | 13.66.62.124, 104.214.16.32, 20.45.121.1, 20.49.88.1 | 20.45.121.32/29, 20.49.88.32/29, 20.49.89.32/29, 40.124.64.136/29 |
 | South East Asia      | 104.43.15.0, 40.78.232.3, 13.67.16.193 | 13.67.16.192/29, 23.98.80.192/29, 40.78.232.192/29|
-| Switzerland North    | 51.107.56.0, 51.107.57.0 | 51.107.56.32/29 |
+| Switzerland North    | 51.107.56.0, 51.107.57.0 | 51.107.56.32/29, 51.103.203.192/29, 20.208.19.192/29, 51.107.242.32/27 |
 | Switzerland West     | 51.107.152.0, 51.107.153.0 | 51.107.153.32/29 |
 | UAE Central          | 20.37.72.64        | 20.37.72.96/29, 20.37.73.96/29 |
 | UAE North            | 65.52.248.0        | 40.120.72.32/29, 65.52.248.32/29 |

azure-sql/database/doc-changes-updates-release-notes-whats-new.md

@@ -10,7 +10,7 @@ ms.subservice: service-overview
 ms.custom: sqldbrb=2, references_regions, ignite-fall-2021
 ms.devlang: 
 ms.topic: conceptual
-ms.date: 04/26/2022
+ms.date: 05/24/2022
 ---
 # What's new in Azure SQL Database?
 [!INCLUDE[appliesto-sqldb](../includes/appliesto-sqldb.md)]
@@ -28,6 +28,7 @@ The following table lists the features of Azure SQL Database that are currently
 
 | Feature | Details |
 | ---| --- |
+| [Azure Synapse Link for Azure SQL Database](/azure/synapse-analytics/synapse-link/sql-synapse-link-overview) | Azure Synapse Link for SQL enables near real time analytics over operational data in Azure SQL Database or SQL Server 2022. |
 | [Elastic jobs](elastic-jobs-overview.md) | The elastic jobs feature is the SQL Server Agent replacement for Azure SQL Database as a PaaS offering.  |
 | [Elastic queries](elastic-query-overview.md) | The elastic queries feature allows for cross-database queries in Azure SQL Database. |
 | [Elastic transactions](elastic-transactions-overview.md) | Elastic transactions allow you to execute transactions distributed among cloud databases in Azure SQL Database. |
@@ -59,6 +60,12 @@ The following table lists the features of Azure SQL Database that have transitio
 
 Learn about significant changes to the Azure SQL Database documentation.
 
+### May 2022
+
+| Changes | Details |
+| --- | --- |
+| **Azure Synapse Link for Azure SQL Database** | Azure Synapse Link enables near real-time analytics over operational data in SQL Server 2022 and Azure SQL Database. With a seamless integration between operational stores and Azure Synapse Analytics dedicated SQL pools, Azure Synapse Link enables you to run analytics, business intelligence and machine learning scenarios on your operational data with minimum impact on source databases with a new change feed technology. For more information, see [What is Synapse Link for SQL? (Preview)](/azure/synapse-analytics/synapse-link/sql-synapse-link-overview).
+
 ### April 2022
 
 | Changes | Details |