Merge pull request #30250 from MicrosoftDocs/main

4/1/2024 AM Publish

Author: Albertyang0

.openpublishing.redirection.json

@@ -103,9 +103,9 @@ For more information on high availability in Hyperscale, see [Database High Avai
 
 ## Zone-redundant availability
 
-Zone-redundant availability is based on storing your database to [zone-redundant storage (ZRS)](/azure/storage/common/storage-redundancy#zone-redundant-storage), which copies your data across three Azure availability zones in the primary region. Each availability zone is a separate physical location with independent power, cooling, and networking.
+Zone-redundant availability ensures your data is spread across three Azure availability zones in the primary region. Each availability zone is a separate physical location with independent power, cooling, and networking.
 
-Zone-redundant availability is available to databases in the General Purpose, Premium, Business Critical and Hyperscale service tiers of the vCore purchasing model, and not the Basic and Standard service tiers of the DTU-based purchasing model. Zone-redundant availability ensures Recovery Point Objective (RPO) which indicates the amount of data loss is zero.
+Zone-redundant availability is available to databases in the Premium, Business Critical, General Purpose and Hyperscale service tiers, and not the Basic and Standard service tiers of the DTU-based purchasing model. Each service tier implements zone-redundant availability differently.  See the details for each service tier in the following sections.  All implementations ensure a Recovery Point Objective (RPO) with zero loss of committed data upon failover.
 
 ### <a id="general-purpose-service-tier-zone-redundant-availability"></a> General Purpose service tier
 
@@ -157,7 +157,7 @@ Consider the following when configuring your General Purpose databases with zone
 
 ### <a id="premium-and-business-critical-service-tier-zone-redundant-availability"></a> Premium and Business Critical service tiers
 
-By default, the cluster of nodes for the local storage availability model is created in the same datacenter. With the introduction of [Azure Availability Zones](/azure/availability-zones/az-overview), SQL Database can place different replicas of a Premium or Business Critical database in different availability zones in the same region. To eliminate a single point of failure, the control ring is also duplicated across multiple zones as three gateway rings (GW). The routing to a specific gateway ring is controlled by [Azure Traffic Manager](/azure/traffic-manager/traffic-manager-overview). Because the zone-redundant configuration in the Premium or Business Critical service tiers doesn't create additional database redundancy, you can enable it at no extra cost. By selecting a zone-redundant configuration, you can make your Premium or Business Critical databases and elastic pools resilient to a much larger set of failures, including catastrophic datacenter outages, without any changes to the application logic. You can also convert any existing Premium or Business Critical databases or elastic pools to zone-redundant configuration. 
+When Zone Redundancy is enabled for Premium or Business Critical service tier, the replicas are placed in different availability zones in the same region. To eliminate a single point of failure, the control ring is also duplicated across multiple zones as three gateway rings (GW). The routing to a specific gateway ring is controlled by [Azure Traffic Manager](/azure/traffic-manager/traffic-manager-overview). Because the zone-redundant configuration in the Premium or Business Critical service tiers uses its existing replicas to place in different availablity zones, you can enable it at no extra cost. By selecting a zone-redundant configuration, you can make your Premium or Business Critical databases and elastic pools resilient to a much larger set of failures, including catastrophic datacenter outages, without any changes to the application logic. You can also convert any existing Premium or Business Critical databases or elastic pools to zone-redundant configuration. 
 
 The zone-redundant version of the high availability architecture is illustrated by the following diagram:
 

azure-sql/database/high-availability-sla.md

@@ -4,7 +4,7 @@ description: Learn how to create a database project as part of the local develop
 author: scoriani
 ms.author: scoriani
 ms.reviewer: mathoma
-ms.date: 05/24/2022
+ms.date: 04/01/2024
 ms.service: sql-database
 ms.topic: how-to
 ms.custom: template-how-to, build-2023, build-2023-dataai
@@ -13,31 +13,36 @@ ms.custom: template-how-to, build-2023, build-2023-dataai
 # Create a project for a local Azure SQL Database development environment
 [!INCLUDE[appliesto-sqldb](../includes/appliesto-sqldb.md)]
 
-The Azure SQL Database [local development experience](local-dev-experience-overview.md) empowers application developers and database professionals to design, edit, build/validate, publish, and run database schemas for databases directly on their workstation using an Azure SQL Database containerized environment. As part of this workflow, you will create a SQL Database Project. The SQL Database Project extension allows you to create a new blank project, create a new project from a database, and open previously created projects. 
+The Azure SQL Database [local development experience](local-dev-experience-overview.md) empowers application developers and database professionals to design, edit, build/validate, publish, and run database schemas for databases directly on their workstation using an Azure SQL Database containerized environment. As part of this workflow, you'll create a SQL Database Project. The SQL Database Project extension allows you to create a new blank project, create a new project from a database, and open previously created projects.
 
 ## Prerequisites
 
 Before creating or opening a SQL Database project, follow the steps in [Set up a local development environment for Azure SQL Database](local-dev-experience-set-up-dev-environment.md) to configure your environment.
 
 ## Create a new project
 
-In the **Database Projects** view select the **New Project** button and enter a project name in the text input that appears.  In the **Select a Folder** dialog that appears, choose a directory for the project's folder, .sqlproj file, and other contents to reside in.
+In the **Database Projects** view, select the **New Project** button and enter a project name in the text input that appears. In the **Select a Folder** dialog that appears, choose a directory for the project's folder, `.sqlproj` file, and other contents to reside in.
 
 The empty project is opened and visible in the **Database Projects** view for editing.
 
 ## Create a project from Azure SQL Database
 
-In the **Project** view, select the **Import Project from Database** button and connect to a database in Azure SQL Database.  Once connected, select a database from the list of available databases and set the name of the project.
+In the **Project** view, select the **Import Project from Database** button and connect to a database in Azure SQL Database. Once connected, select a database from the list of available databases and set the name of the project.
 
 Finally, select a target structure of the extraction. The new project opens and contains SQL scripts for the contents of the selected database.
 
 ## Open an existing project
 
-In the **Database Projects** view, select **Open Project** and open an existing *.sqlproj* file from the file picker that appears. Existing projects can originate from Azure Data Studio, Visual Studio Code or [Visual Studio SQL Server Data Tools](/sql/ssdt/sql-server-data-tools).
+In the **Database Projects** view, select **Open Project** and open an existing `.sqlproj` file from the file picker that appears. Existing projects can originate from Azure Data Studio, Visual Studio Code, or [Visual Studio SQL Server Data Tools](/sql/ssdt/sql-server-data-tools).
 
 The existing project opens and its contents are visible in the **Database Projects** view for editing.
 
-## Next steps
+## Next step
+
+> [!div class="nextstepaction"]
+> [Build and Publish a project](/azure-data-studio/extensions/sql-database-project-extension-build)
+
+## Related content
 
 Learn more about the local development experience for Azure SQL Database:
 

azure-sql/database/local-dev-experience-create-database-project.md

@@ -4,7 +4,7 @@ description: How to set up a local development environment for Azure SQL Databas
 author: scoriani
 ms.author: scoriani
 ms.reviewer: mathoma
-ms.date: 05/24/2022
+ms.date: 04/01/2024
 ms.service: sql-database
 ms.topic: how-to
 ---
@@ -16,20 +16,20 @@ This article teaches you to set up the [local development experience for Azure S
 
 ## Prerequisites
 
-Before you configure the local development environment for Azure SQL Database, make sure you have met the following hardware and software requirements:
+Before you configure the local development environment for Azure SQL Database, make sure you meet the following hardware and software requirements:
 
 - Software requirements:
     - Currently supported on Windows 10 or later release, macOS Mojave or later release, and Linux (preferably Ubuntu 18.04 or later release)
-    - [Azure Data Studio](/azure-data-studio/download-azure-data-studio) or [VSCode](https://code.visualstudio.com/Docs)
+    - [Azure Data Studio](/azure-data-studio/download-azure-data-studio) or [Visual Studio Code](https://code.visualstudio.com/Docs)
 - Minimum hardware requirements:
-    - 8 GB RAM
-    - 10 GB available disk space
+    - 8-GB RAM
+    - 10-GB available disk space
 
 ## Install Docker Desktop
 
 The local development environment for Azure SQL Database uses the [Azure SQL Database emulator](local-dev-experience-sql-database-emulator.md), a containerized database with close fidelity to the Azure SQL Database public service. The Azure SQL Database emulator is implemented as a [Docker](https://www.docker.com/) container.
 
-Install [Docker Desktop](https://www.docker.com/products/docker-desktop/). If you are using Windows, set up [Docker Desktop for Windows with WSL 2](/windows/wsl/tutorials/wsl-containers).
+Install [Docker Desktop](https://www.docker.com/products/docker-desktop/). If you're using Windows, set up [Docker Desktop for Windows with WSL 2](/windows/wsl/tutorials/wsl-containers).
 
 Ensure that Docker Desktop is running before using your local development environment for Azure SQL Database.
 
@@ -39,30 +39,32 @@ There are different extensions to install depending on your preferred developmen
 
 | Extension | Visual Studio Code | Azure Data Studio |
 |--|--|--|
-| The [mssql extension for Visual Studio Code](https://marketplace.visualstudio.com/items?itemName=ms-mssql.mssql) | Install the mssql extension. | Installation is not necessary as the extension as the functionality is natively available. |
-| [SQL Database Projects extension (Preview)](https://marketplace.visualstudio.com/items?itemName=ms-mssql.sql-database-projects-vscode) | Installation as not necessary as the SQL Database Projects extension is bundled with the mssql extension and is automatically installed and updated when the mssql extension is installed or updated. | Install the SQL Database Projects extension. |
+| The [mssql extension for Visual Studio Code](https://marketplace.visualstudio.com/items?itemName=ms-mssql.mssql) | Install the `mssql` extension. | Installation isn't necessary. The mssql extension as the functionality is natively available. |
+| [SQL Database Projects extension (Preview)](https://marketplace.visualstudio.com/items?itemName=ms-mssql.sql-database-projects-vscode) | Installation isn't necessary. The SQL Database Projects extension is bundled with the `mssql` extension, and is automatically installed and updated when the `mssql` extension is installed or updated. | Install the SQL Database Projects extension. |
 
 # [Visual Studio Code](#tab/vscode)
 
-If you are using [VSCode](https://code.visualstudio.com/Docs), install the [mssql extension for Visual Studio Code](https://marketplace.visualstudio.com/items?itemName=ms-mssql.mssql). 
+If you're using [Visual Studio Code](https://code.visualstudio.com/Docs), install the [mssql extension for Visual Studio Code](https://marketplace.visualstudio.com/items?itemName=ms-mssql.mssql).
 
-The mssql extension enables you to connect and run queries and test scripts against a database. The database may be running in the Azure SQL Database emulator locally, or it may be a database in the global Azure SQL Database service.
+The `mssql` extension enables you to connect and run queries and test scripts against a database. The database can run in the Azure SQL Database emulator locally, or in the global Azure SQL Database service.
 
 To install the extension:
 
-1. In VSCode, select **View** > **Command Palette**, or press **Ctrl**+**Shift**+**P**, or press **F1** to open the **Command Palette**.
+1. In Visual Studio Code, select **View** > **Command Palette**, or press **Ctrl**+**Shift**+**P**, or press **F1** to open the **Command Palette**.
 
 1. In the **Command Palette**, select **Extensions: Install Extensions** from the dropdown.
 
-1. In the **Extensions** pane, type **mssql**.
+1. In the **Extensions** pane, type `mssql`.
 
 1. Select the **SQL Server (mssql)** extension, and then select **Install**.
 
 1. After the installation completes, select **Reload** to enable the extension.
 
+1. There's no need to run the docker container with a SQL image manually, it is deployed and run when you [Build and Publish a Project](/azure-data-studio/extensions/sql-database-project-extension-build#publish-a-database-project).
+
 # [Azure Data Studio](#tab/ads)
 
-If you are using [Azure Data Studio](/azure-data-studio/download-azure-data-studio), install the [SQL Database Projects extension (Preview)](https://marketplace.visualstudio.com/items?itemName=ms-mssql.sql-database-projects-vscode). The SQL Database Projects extension enables you to capture an existing database schema and/or design new database objects using a declarative database design model. You can commit a database schema to version control. You can also publish a database schema to a database running in the Azure SQL Database emulator, or to a database running in the global Azure SQL Database service. You may publish an entire database, or incremental changes to a database.
+If you're using [Azure Data Studio](/azure-data-studio/download-azure-data-studio), install the [SQL Database Projects extension (Preview)](https://marketplace.visualstudio.com/items?itemName=ms-mssql.sql-database-projects-vscode). The SQL Database Projects extension enables you to capture an existing database schema and/or design new database objects using a declarative database design model. You can commit a database schema to version control. You can also publish a database schema to a database running in the Azure SQL Database emulator, or to a database running in the global Azure SQL Database service. You can publish an entire database, or incremental changes to a database.
 
 To install the SQL Database Projects extension:
 
@@ -76,15 +78,20 @@ To install the SQL Database Projects extension:
 
 1. After the installation completes, select **Reload** to enable the extension.
 
+1. There's no need to run the docker container with a SQL image manually, as it gets deployed and run in the subsequent step: [Build and Publish a Project](/azure-data-studio/extensions/sql-database-project-extension-build#publish-a-database-project).
+
 ---
 
+## Begin using your local development environment
 
+You have now set up your local development environment for Azure SQL Database.
 
-## Begin using your local development environment
+## Next step
 
-You have now set up your local development environment for Azure SQL Database. Next, [Create a database project for a local Azure SQL Database development environment](local-dev-experience-create-database-project.md).
+> [!div class="nextstepaction"]
+> [Create a database project for a local Azure SQL Database development environment](local-dev-experience-create-database-project.md)
 
-## Next steps
+## Related content
 
 Learn more about the local development experience for Azure SQL Database:
 

azure-sql/database/local-dev-experience-set-up-dev-environment.md

@@ -15,7 +15,7 @@ ms.topic: conceptual
 
 [!INCLUDE[big-data-clusters-banner-retirement](../includes/bdc-banner-retirement.md)]
 
-The following sample shows how to build a model with [Spark ML](https://spark.apache.org/docs/latest/ml-guide.html), export the model to [MLeap](http://mleap-docs.combust.ml/), and score the model in SQL Server with its [Java Language Extension](../language-extensions/language-extensions-overview.md). This is done in the context of a SQL Server big data cluster.
+The following sample shows how to build a model with [Spark ML](https://spark.apache.org/docs/latest/ml-guide.html), export the model to [MLeap](https://combust.github.io/mleap-docs/), and score the model in SQL Server with its [Java Language Extension](../language-extensions/language-extensions-overview.md). This is done in the context of a SQL Server big data cluster.
 
 The following diagram illustrates the work performed in this sample:
 

docs/big-data-cluster/spark-create-machine-learning-model.md

@@ -27,7 +27,7 @@ Sparklyr provides an R interface for Apache Spark. Sparklyr is a popular way for
 
 Install and configure **RStudio Desktop** with the following steps:
 
-1. If you are running on a Windows client, [download and install R 3.6.3](https://cran.rstudio.com/bin/windows/base/old/3.6.3). Also, [download and install RTools 3.5](https://cran.r-project.org/bin/windows/Rtools/history.html). Make sure to configure RTools binary folder on your PATH environment variable.
+1. If you are running on a Windows client, [download and install R 3.6.3](https://cran-archive.r-project.org/bin/windows/base/old/). Also, [download and install RTools 3.5](https://cran.r-project.org/bin/windows/Rtools/history.html). Make sure to configure RTools binary folder on your PATH environment variable.
 
     > [!WARNING]
     > R version 4.x and sparklyr versions other that the one specified below are verified not to work as of SQL Server Big Data Clusters CU13.