20240729 improve script steps and instructions in comments

Author: WilliamDAssafMSFT

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

@@ -1,15 +1,14 @@
 ---
 title: Restore a dedicated SQL pool from a dropped workspace
 description: How-to guide for restoring a dedicated SQL pool from a dropped workspace.
-author: realAngryAnalytics
-ms.author: stevehow
-ms.reviewer: wiassaf
-ms.date: 01/23/2024
+author: WilliamDAssafMSFT
+ms.author: wiassaf
+ms.reviewer: stevehow, ajagadish
+ms.date: 07/29/2024
 ms.service: synapse-analytics
 ms.subservice: sql
 ms.topic: how-to
 ---
-
 # Restore a dedicated SQL pool from a deleted workspace
 
 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.
@@ -23,21 +22,24 @@ In this article, you learn how to restore a dedicated SQL pool in Azure Synapse
 
 ## Restore the SQL pool from the dropped workspace
 
+The following sample script accomplishes these steps:
+
 1. Open PowerShell
 
 1. Connect to your Azure account.
 
 1. Set the context to the subscription that contains the workspace that was dropped.
 
-1. Specify the approximate datetime the workspace was dropped.
-
-1. Construct the resource ID for the database you wish to recover from the dropped workspace.
+1. Determine the datetime the workspace was dropped. This step retrieves the exact date and time the workspace SQL pool was dropped. 
+    - This step assumes that the workspace with the same name resource group and same values is still available. 
+    - If not, recreate the dropped workspace with the same workspace name, resource group name, region, and all the same values from prior dropped workspace. 
+    
+1. Construct the resource ID of the sql pool you wish to recover. The format requires `Microsoft.Sql`. This includes the date and time when the server was dropped.
 
-1. Restore the database from the dropped workspace
+1. Restore the database from the dropped workspace. Restore to the target workspace with the source SQL pool.
 
 1. Verify the status of the recovered database as 'online'.
 
-    
     ```powershell
     $SubscriptionID="<YourSubscriptionID>"
     $ResourceGroupName="<YourResourceGroupName>"
@@ -51,13 +53,12 @@ In this article, you learn how to restore a dedicated SQL pool in Azure Synapse
     Set-AzContext -SubscriptionID $SubscriptionID
     
     # Get the exact date and time the workspace SQL pool was dropped. 
-    # Please note that this assumes that the workspace with the same name resource group and same values is still available.
-    # If not, please recreate the dropped workspace to get the output from the below. You will have to use the same workspace name, resource group name, region and all the same values from prior dropped workspace. 
+    # This assumes that the workspace with the same name resource group and same values is still available.
+    # If not, recreate the dropped workspace with the same workspace name, resource group name, region, and all the same values from prior dropped workspace. 
     # There should only be one selection to select from.
     $DroppedDateTime = Get-AzSynapseDroppedSqlPool -ResourceGroupName $ResourceGroupName -WorkspaceName $WorkspaceName -Name $DatabaseName | Select-Object -ExpandProperty DeletionDate
-
   
-    # construct the resource ID of the sql pool you wish to recover. The format required Microsoft.Sql. This includes the approximate date time the server was dropped.
+    # Construct the resource ID of the sql pool you wish to recover. The format requires Microsoft.Sql. This includes the approximate date time the server was dropped.
     $SourceDatabaseID = "/subscriptions/"+$SubscriptionID+"/resourceGroups/"+$ResourceGroupName+"/providers/Microsoft.Sql/servers/"+$WorkspaceName+"/databases/"+$DatabaseName
     
     # Restore to the target workspace with the source SQL pool.
@@ -68,6 +69,7 @@ In this article, you learn how to restore a dedicated SQL pool in Azure Synapse
     ```
 
 ## <a id="troubleshooting"></a> Troubleshoot
+
 If "An unexpected error occurred while processing the request." message is received, the original database might not have any recovery points available due to the original workspace being short lived. Typically this is when the workspace existed for less than one hour.
 
 ## Related content