Merge pull request #209071 from WilliamDAssafMSFT/20220824-disambiguation-sql-dw-synapse-analytics

[BULK] 20220824 clarify dedicated sql pool types in numerous places

Author: jborsecnik

articles/synapse-analytics/backuprestore/restore-sql-pool-from-deleted-workspace.md

@@ -15,7 +15,7 @@ ms.reviewer: wiassaf
 In this article, you learn how to restore a dedicated SQL pool in Azure Synapse Analytics after an accidental drop of a workspace using PowerShell.
 
 > [!NOTE]
-> This guidance is for Synapse Workspace dedicated sql pools only. For standalone dedicated sql pool (formerly SQL DW) please follow guidance [Restore sql pool from deleted server](../sql-data-warehouse/sql-data-warehouse-restore-from-deleted-server.md).
+> This guidance is for dedicated SQL pools in Azure Synapse workspaces only. For standalone dedicated SQL pools (formerly SQL DW), follow guidance [Restore sql pool from deleted server](../sql-data-warehouse/sql-data-warehouse-restore-from-deleted-server.md).
 
 ## Before you begin
 
@@ -51,7 +51,7 @@ Connect-AzAccount
 Set-AzContext -SubscriptionID $SubscriptionID
 
 # Define the approximate point in time the workspace was dropped as DroppedDateTime "yyyy-MM-ddThh:mm:ssZ" (ex. 2022-01-01T16:15:00Z)
-$PointInTime=”<DroppedDateTime>” 
+$PointInTime="<DroppedDateTime>" 
 $DroppedDateTime = Get-Date -Date $PointInTime 
 
 

articles/synapse-analytics/backuprestore/restore-sql-pool.md

@@ -6,7 +6,7 @@ manager: joannapea
 ms.service: synapse-analytics
 ms.topic: how-to
 ms.subservice: sql
-ms.date: 04/11/2022
+ms.date: 08/24/2022
 ms.author: stevehow
 ms.reviewer: joanpo
 ms.custom: seo-lt-2019
@@ -19,32 +19,32 @@ In this article, you learn how to restore an existing dedicated SQL pool in Azur
 ## Restore an existing dedicated SQL pool through the Synapse Studio
 
 1. Sign in to the [Azure portal](https://portal.azure.com/).
-2. Navigate to your Synapse workspace. 
-3. Under Getting Started -> Open Synapse Studio, select **Open**.
+2. Navigate to your Azure Synapse workspace. 
+3. Under **Getting Started** -> **Open Synapse Studio**, select **Open**.
 
     ![ Synapse Studio](../media/sql-pools/open-synapse-studio.png)
 4. On the left hand navigation pane, select **Data**.
 5. Select **Manage pools**. 
-6. Select **+ New** to create a new dedicated SQL pool. 
-7. In the Additional Settings tab, select a Restore Point to restore from. 
+6. Select **+ New** to create a new dedicated SQL pool in the Azure Synapse Analytics workspace.
+7. In the **Additional Settings** tab, select a **Restore Point** to restore from. 
 
     If you want to perform a geo-restore, select the workspace and dedicated SQL pool that you want to recover. 
 
 8. Select either **Automatic Restore Points** or **User-Defined Restore Points**. 
 
     ![Restore points](../media/sql-pools/restore-point.PNG)
 
-    If the dedicated SQL pool doesn't have any automatic restore points, wait a few hours or create a user defined restore point before restoring. For User-Defined Restore Points, select an existing one or create a new one.
+    If the dedicated SQL pool doesn't have any automatic restore points, wait a few hours, or create a user defined restore point before restoring. For User-Defined Restore Points, select an existing one or create a new one.
 
-    If you are restoring a geo-backup, simply select the workspace located in the source region and the dedicated SQL pool you want to restore. 
+    If you are restoring a geo-backup, select the workspace located in the source region and the dedicated SQL pool you want to restore. 
 
 9. Select **Review + Create**.
 
 ## Restore an existing dedicated SQL pool through the Azure portal
 
 1. Sign in to the [Azure portal](https://portal.azure.com/).
 2. Navigate to the dedicated SQL pool that you want to restore from.
-3. At the top of the Overview blade, select **Restore**.
+3. At the top of the **Overview** page, select **Restore**.
 
     ![ Restore Overview](../media/sql-pools/restore-sqlpool-01.png)
 
@@ -58,7 +58,7 @@ In this article, you learn how to restore an existing dedicated SQL pool in Azur
 
 ## Restore an existing dedicated SQL pool through PowerShell
 
-1. Open PowerShell.
+1. Open a PowerShell terminal.
 
 2. Connect to your Azure account and list all the subscriptions associated with your account.
 
@@ -71,7 +71,7 @@ In this article, you learn how to restore an existing dedicated SQL pool in Azur
 6. Restore the dedicated SQL pool to the desired restore point using [Restore-AzSynapseSqlPool](/powershell/module/az.synapse/restore-azsynapsesqlpool?toc=/azure/synapse-analytics/toc.json&bc=/azure/synapse-analytics/breadcrumb/toc.json) PowerShell cmdlet.
 
     1. To restore the dedicated SQL pool to a different workspace, make sure to specify the other workspace name.  This workspace can also be in a different resource group and region.
-    2. To restore to a different subscription, see the [below section](#restore-an-existing-dedicated-sql-pool-to-a-different-subscription-through-powershell).
+    2. To restore to a different subscription, see [Restore an existing dedicated SQL pool to a different subscription through PowerShell](#restore-an-existing-dedicated-sql-pool-to-a-different-subscription-through-powershell) later in this article.
 
 7. Verify that the restored dedicated SQL pool is online.
 
@@ -98,8 +98,8 @@ $PointInTime="<RestorePointCreationDate>"
 $SQLPool = Get-AzSynapseSqlPool -ResourceGroupName $ResourceGroupName -WorkspaceName $WorkspaceName -Name $SQLPoolName
 # Transform Synapse SQL pool resource ID to SQL database ID because currently the restore command only accepts the SQL database ID format.
 $DatabaseID = $SQLPool.Id -replace "Microsoft.Synapse", "Microsoft.Sql" `
-	-replace "workspaces", "servers" `
-	-replace "sqlPools", "databases"
+    -replace "workspaces", "servers" `
+    -replace "sqlPools", "databases"
 
 # Restore database from a restore point
 $RestoredDatabase = Restore-AzSynapseSqlPool –FromRestorePoint -RestorePoint $PointInTime -ResourceGroupName $SQLPool.ResourceGroupName `
@@ -115,14 +115,17 @@ $RestoredDatabase.status
 ```
 
 ## Restore an existing dedicated SQL pool to a different subscription through PowerShell
-When performing a cross-subscription restore, a synapse workspace dedicated SQL pool can only restore to a standalone dedicated SQL pool (formerly SQL DW). The PowerShell below is similar to the above however there are three main differences:
+
+When performing a cross-subscription restore, a dedicated SQL pool in an Azure Synapse workspace can only restore directly to a standalone dedicated SQL pool (formerly SQL DW). If it is required to restore a dedicated SQL pool in an Azure Synapse workspace to a workspace in the destination subscription, an additional restore step is required.
+
+The PowerShell below is similar to the above, however there are three main differences:
 - After retrieving the SQL Pool object to be restored, the subscription context needs to be switched to the destination (or target) subscription name. 
 - When performing the restore, use the Az.Sql modules instead of the Az.Synapse modules. 
-- If it is required to restore the dedicated SQL pool to a Synapse workspace in the destination subscription, an additional restore step is required.
+- The below sample code has additional steps for restoring to an Azure Synapse workspace in the destination subscription. Uncomment the PowerShell commands as described in the sample.
 
 Steps:
 
-1. Open PowerShell.
+1. Open a PowerShell terminal.
 
 2. Update Az.Sql Module to 3.8.0 (or greater) if needed
 
@@ -132,7 +135,7 @@ Steps:
 
 5. List the restore points for the dedicated SQL pool.
 
-6. Pick the desired restore point using the RestorePointCreationDate.
+6. Pick the desired restore point using the **RestorePointCreationDate**.
 
 7. Select the destination subscription in which the SQL pool should be restored.
 
@@ -142,8 +145,8 @@ Steps:
 
 10. **If the desired destination is a Synapse Workspace, uncomment the code to perform the additional restore step.**
     1. Create a restore point for the newly created data warehouse.
-    2. Retrieve the last restore point created by using the "Select -Last 1" syntax.
-    3. Perform the restore to the desired Synapse workspace.
+    2. Retrieve the last restore point created by using the `Select -Last 1` syntax.
+    3. Perform the restore to the desired Azure Synapse workspace.
 
 ```powershell
 $SourceSubscriptionName="<YourSubscriptionName>"
@@ -154,7 +157,7 @@ $TargetSubscriptionName="<YourTargetSubscriptionName>"
 $TargetResourceGroupName="<YourTargetResourceGroupName>"
 $TargetServerName="<YourTargetServerNameWithoutURLSuffixSeeNote>"  # Without sql.azuresynapse.net
 $TargetDatabaseName="<YourDatabaseName>"
-#$TargetWorkspaceName="<YourTargetWorkspaceName>" # uncomment if restore to a synapse workspace is required
+#$TargetWorkspaceName="<YourTargetWorkspaceName>" # uncomment if restore to an Azure Synapse workspace is required
 
 # Update Az.Sql module to the latest version (3.8.0 or above)
 # Update-Module -Name Az.Sql -RequiredVersion 3.8.0
@@ -172,8 +175,8 @@ $PointInTime="<RestorePointCreationDate>"
 $SQLPool = Get-AzSynapseSqlPool -ResourceGroupName $SourceResourceGroupName -WorkspaceName $SourceWorkspaceName -Name $SourceSQLPoolName
 # Transform Synapse SQL pool resource ID to SQL database ID because currently the restore command only accepts the SQL database ID format.
 $DatabaseID = $SQLPool.Id -replace "Microsoft.Synapse", "Microsoft.Sql" `
-	-replace "workspaces", "servers" `
-	-replace "sqlPools", "databases"
+    -replace "workspaces", "servers" `
+    -replace "sqlPools", "databases"
 
 # Switch context to the destination subscription
 Select-AzSubscription -SubscriptionName $TargetSubscriptionName
@@ -200,10 +203,14 @@ $RestoredDatabase.status
 
 ## Troubleshooting
 A restore operation can result in a deployment failure based on a "RequestTimeout" exception. 
+
 ![Screenshot from resource group deployments dialog of a timeout exception.](../media/sql-pools/restore-sql-pool-troubleshooting-01.png)  
-This timeout can be ignored. Review the dedicated SQL pool blade in the portal and it may still have status of "Restoring" and eventually will transition to "Online". 
+
+This timeout can be ignored. Review the dedicated SQL pool page in the Azure portal and it may still have status of "Restoring" and eventually will transition to "Online". 
+
 ![Screenshot of SQL pool dialog with the status that shows restoring.](../media/sql-pools/restore-sql-pool-troubleshooting-02.png)  
 
 ## Next Steps
 
 - [Create a restore point](sqlpool-create-restore-point.md)
+- [Restore-AzSqlDatabase](/powershell/module/az.sql/restore-azsqldatabase?toc=/azure/synapse-analytics/sql-data-warehouse/toc.json&bc=/azure/synapse-analytics/sql-data-warehouse/breadcrumb/toc.json)

articles/synapse-analytics/overview-faq.yml

@@ -7,7 +7,7 @@ metadata:
   ms.topic: faq
   ms.subservice: overview
   ms.custom: event-tier1-build-2022
-  ms.date: 05/24/2022
+  ms.date: 08/24/2022
   ms.author: saveenr
   ms.reviewer: sngun, wiassaf
 title: Azure Synapse Analytics frequently asked questions
@@ -53,7 +53,7 @@ sections:
           - Serverless SQL pools - you have monitoring and cost management controls that let you cap spending at a daily, weekly, and monthly level. [See Cost management for serverless SQL pool](./sql/data-processed.md) for more information. 
           
           - Serverless Spark pools - you can restrict who can create Spark pools with Synapse RBAC roles.  
-          
+
       - question: |
           Will Synapse workspace support folder organization of objects and granularity at GA?
         answer: |
@@ -181,6 +181,12 @@ sections:
       
   - name: Dedicated SQL Pools
     questions:
+        
+      - question: |
+          What is the difference between dedicated SQL pools (SQL DW) and dedicated SQL pools in Azure Synapse workspaces?
+        answer: |
+          Dedicated SQL pools (formerly SQL DW) are an Azure Platform-as-a-Service (PaaS) enterprise data warehousing platform. You can query existing dedicated SQL pools (formerly SQL DW) and also create new dedicated SQL pools in your Azure Synapse workspace. Not all features of the dedicated SQL pool in Azure Synapse workspaces apply to a standalone dedicated SQL pool (formerly SQL DW), and vice versa. For more information, see [What's the difference between Azure Synapse dedicated SQL pools (formerly SQL DW) and dedicated SQL pools in an Azure Synapse Analytics workspace?](https://techcommunity.microsoft.com/t5/azure-synapse-analytics-blog/msft-docs-what-s-the-difference-between-synapse-formerly-sql-dw/ba-p/3597772). To enable Azure Synapse workspace features for an existing dedicated SQL pool (formerly SQL DW), refer to [How to enable a workspace for your dedicated SQL pool (formerly SQL DW)](sql-data-warehouse/workspace-connected-create.md). 
+
       - question: |
           What are the functional differences between dedicated SQL pools and serverless pools?
         answer: |

articles/synapse-analytics/sql-data-warehouse/sql-data-warehouse-manage-compute-rest-api.md

@@ -17,7 +17,7 @@ ms.custom: seo-lt-2019, azure-synapse
 REST APIs for managing compute for dedicated SQL pool (formerly SQL DW) in Azure Synapse Analytics.
 
 > [!NOTE]
-> The REST APIs that are described in this article are for standalone dedicated SQL pools (formerly SQL DW) and are not applicable to a dedicated SQL pool that's created in an Azure Synapse Analytics workspace. For information about REST APIs to use specifically for an Azure Synapse Analytics workspace, see [Azure Synapse Analytics workspace REST API](/rest/api/synapse/).
+> The REST APIs that are described in this article are for standalone dedicated SQL pools (formerly SQL DW) and are not applicable to a dedicated SQL pool in an Azure Synapse Analytics workspace. For information about REST APIs to use specifically for an Azure Synapse Analytics workspace, see [Azure Synapse Analytics workspace REST API](/rest/api/synapse/).
 
 ## Scale compute
 

articles/synapse-analytics/sql-data-warehouse/sql-data-warehouse-overview-faq.yml

@@ -6,7 +6,7 @@ metadata:
   ms.service: synapse-analytics
   ms.topic: faq
   ms.subservice: sql-dw 
-  ms.date: 11/04/2019
+  ms.date: 08/24/2022
   ms.author: martinle
   ms.reviewer: wiassaf
 title: Dedicated SQL pool (formerly SQL DW) in Azure Synapse Analytics frequently asked questions
@@ -28,7 +28,12 @@ sections:
       - question: |
           What is a dedicated SQL pool (formerly SQL DW) in Azure Synapse Analytics?
         answer: |
-          Dedicated SQL pool (formerly SQL DW) refers to the enterprise data warehousing features that are generally available with Azure Synapse. For more information, see, [What is Azure Synapse Analytics](sql-data-warehouse-overview-what-is.md).
+          Dedicated SQL pool refers to the standalone platform of enterprise data warehousing features that are generally available with Azure Synapse. For more information, see [What is Azure Synapse Analytics](sql-data-warehouse-overview-what-is.md). A dedicated SQL pool (formerly SQL DW) is a standalone or connected service outside of an Azure Synapse workspace. You can also create dedicated SQL pools in your Azure Synapse workspace.
+          
+      - question: |
+          What is the difference between dedicated SQL pools (SQL DW) and dedicated SQL pools in Azure Synapse workspaces?
+        answer: |
+          Not all features of the dedicated SQL pool in Azure Synapse workspaces apply to a standalone dedicated SQL pool (formerly SQL DW), and vice versa. For more information, see [What's the difference between Azure Synapse dedicated SQL pools (formerly SQL DW) and dedicated SQL pools in an Azure Synapse Analytics workspace?](https://techcommunity.microsoft.com/t5/azure-synapse-analytics-blog/msft-docs-what-s-the-difference-between-synapse-formerly-sql-dw/ba-p/3597772). To enable Azure Synapse workspace features for an existing dedicated SQL pool (formerly SQL DW), refer to [How to enable a workspace for your dedicated SQL pool (formerly SQL DW)](workspace-connected-create.md). 
           
       - question: |
           How do I get started with Azure Synapse?

articles/synapse-analytics/sql-data-warehouse/sql-data-warehouse-overview-what-is.md

@@ -26,8 +26,7 @@ Dedicated SQL pool (formerly SQL DW) represents a collection of analytic resourc
 Once your dedicated SQL pool is created, you can import big data with simple [PolyBase](/sql/relational-databases/polybase/polybase-guide?toc=/azure/synapse-analytics/sql-data-warehouse/toc.json&bc=/azure/synapse-analytics/sql-data-warehouse/breadcrumb/toc.json&view=azure-sqldw-latest&preserve-view=true) T-SQL queries, and then use the power of the distributed query engine to run high-performance analytics. As you integrate and analyze the data, dedicated SQL pool (formerly SQL DW) will become the single version of truth your business can count on for faster and more robust insights.
 
 > [!NOTE]
-> Not all features of the dedicated SQL pool in Azure Synapse workspaces apply to dedicated SQL pool (formerly SQL DW), and vice versa. To enable workspace features for an existing dedicated SQL pool (formerly SQL DW) refer to [How to enable a workspace for your dedicated SQL pool (formerly SQL DW)](workspace-connected-create.md). Explore the [Azure Synapse Analytics documentation](../overview-what-is.md) and [Get Started with Azure Synapse](../get-started.md).
-> 
+> Not all features of the dedicated SQL pool in Azure Synapse workspaces apply to dedicated SQL pool (formerly SQL DW), and vice versa. To enable workspace features for an existing dedicated SQL pool (formerly SQL DW) refer to [How to enable a workspace for your dedicated SQL pool (formerly SQL DW)](workspace-connected-create.md). For more information, see [What's the difference between Azure Synapse dedicated SQL pools (formerly SQL DW) and dedicated SQL pools in an Azure Synapse Analytics workspace?](https://techcommunity.microsoft.com/t5/azure-synapse-analytics-blog/msft-docs-what-s-the-difference-between-synapse-formerly-sql-dw/ba-p/3597772). Explore the [Azure Synapse Analytics documentation](../overview-what-is.md) and [Get Started with Azure Synapse](../get-started.md).
 
 ## Key component of a big data solution
 
@@ -48,8 +47,9 @@ The analysis results can go to worldwide reporting databases or applications. Bu
 - [Load sample data](./load-data-from-azure-blob-storage-using-copy.md).
 - Explore [Videos](https://azure.microsoft.com/documentation/videos/index/?services=sql-data-warehouse)
 - [Get Started with Azure Synapse](../get-started.md)
+- [What's the difference between Azure Synapse dedicated SQL pools (formerly SQL DW) and dedicated SQL pools in an Azure Synapse Analytics workspace?](https://techcommunity.microsoft.com/t5/azure-synapse-analytics-blog/msft-docs-what-s-the-difference-between-synapse-formerly-sql-dw/ba-p/3597772)
 
-Or look at some of these other Azure Synapse resources.
+Or look at some of these other Azure Synapse resources:
 
 - Search [Blogs](https://azure.microsoft.com/blog/tag/azure-sql-data-warehouse/)
 - Submit a [Feature requests](https://feedback.azure.com/d365community/forum/9b9ba8e4-0825-ec11-b6e6-000d3a4f07b8)

articles/synapse-analytics/sql-data-warehouse/sql-data-warehouse-restore-from-deleted-server.md

@@ -5,7 +5,7 @@ author: realAngryAnalytics
 ms.service: synapse-analytics
 ms.topic: how-to
 ms.subservice: sql-dw
-ms.date: 04/01/2022
+ms.date: 08/24/2022
 ms.author: stevehow
 ms.reviewer: wiassaf
 ---
@@ -15,15 +15,15 @@ ms.reviewer: wiassaf
 In this article, you learn how to restore a dedicated SQL pool (formerly SQL DW) in Azure Synapse Analytics after an accidental drop of a server using PowerShell.
 
 > [!NOTE]
-> This guidance is for standalone dedicated sql pools (formerly SQL DW) only. For synapse workspace dedicated sql pools please follow guidance [Restore SQL pool from deleted workspace](../backuprestore/restore-sql-pool-from-deleted-workspace.md).
+> This guidance is for standalone dedicated SQL pools (formerly SQL DW) only. For dedicated SQL pools in an Azure Synapse Analytics workspace, see [Restore SQL pool from deleted workspace](../backuprestore/restore-sql-pool-from-deleted-workspace.md).
 
 ## Before you begin
 
 [!INCLUDE [updated-for-az](../../../includes/updated-for-az.md)]
 
 ## Restore the SQL pool from the deleted server
 
-1. Open PowerShell
+1. Open PowerShell.
 
 2. Connect to your Azure account.
 
@@ -50,7 +50,7 @@ Connect-AzAccount
 Set-AzContext -SubscriptionId $SubscriptionID
 
 # Define the approximate point in time the server was dropped as DroppedDateTime "yyyy-MM-ddThh:mm:ssZ" (ex. 2022-01-01T16:15:00Z)
-$PointInTime=”<DroppedDateTime>” 
+$PointInTime="<DroppedDateTime>" 
 $DroppedDateTime = Get-Date -Date $PointInTime 
 
 # construct the resource ID of the database you wish to recover. The format required Microsoft.Sql. This includes the approximate date time the server was dropped.