Skip to content

Commit 12f954e

Browse files
committed
Updating SQL dedicated pool restore instructions
1 parent 744985b commit 12f954e

File tree

2 files changed

+10
-3
lines changed

2 files changed

+10
-3
lines changed

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

Lines changed: 6 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -34,11 +34,14 @@ In this article, you learn how to restore an existing dedicated SQL pool in Azur
3434

3535
![Restore points](../media/sql-pools/restore-point.PNG)
3636

37-
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.
37+
* 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.
3838

39-
If you are restoring a geo-backup, select the workspace located in the source region and the dedicated SQL pool you want to restore.
39+
* If you want to restore a dedicated SQL pool from a different workspace, select **New dedicated SQL pool** from your current workspace. Under the **Additional settings** tab find the **Use existing data** and select the **Restore point** option. As shown in the above screenshot, you can then select the **Server or workspace** name from which you can restore.
4040

41-
You cannot perform an in-place restore of a SQL pool with the same name as an existing pool. Regardless of the SQL pool being within the same workspace or a different workspace. If you'd like to restore from a user-defined restore point in another workspace, you need to use the "Create new SQL pool" function.
41+
* If you are restoring a geo-backup, select the workspace located in the source region and the dedicated SQL pool you want to restore.
42+
43+
> [!NOTE]
44+
> You cannot perform an in-place restore of a SQL pool with the same name as an existing pool. Regardless of the SQL pool being in the same workspace or a different workspace.
4245
4346
9. Select **Review + Create**.
4447

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

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -22,6 +22,10 @@ In this article, you learn to restore a dedicated SQL pool (formerly SQL DW) usi
2222

2323
**Verify your DTU capacity.** Each dedicated SQL pool (formerly SQL DW) is hosted by a [logical SQL server](/azure/azure-sql/database/logical-servers) (for example, myserver.database.windows.net) which has a default DTU quota. Verify that the server has enough remaining DTU quota for the database being restored. To learn how to calculate DTU needed or to request more DTU, see [Request a DTU quota change](sql-data-warehouse-get-started-create-support-ticket.md).
2424

25+
## SQL pool restore naming conventions
26+
27+
Before restoring a deleted SQL pool, make sure that you haven't created a new pool with the same name as the deleted pool. Because the restore point for the previous SQL pool will be overwritten by the new SQL pool.
28+
2529
## Restore a deleted data warehouse through PowerShell
2630

2731
To restore a deleted dedicated SQL pool (formerly SQL DW), use the [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) cmdlet. If the corresponding server has been deleted as well, you can't restore that data warehouse.

0 commit comments

Comments
 (0)