You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
## Restore an existing dedicated SQL pool (formerly SQL DW) to a different tenant through PowerShell
153
+
This is similar guidance to restoring an existing dedicated SQL pool, however the below instructions show that [Get-AzSqlDatabase](/powershell/module/az.sql/Get-AzSqlDatabase?toc=/azure/synapse-analytics/sql-data-warehouse/toc.json&bc=/azure/synapse-analytics/sql-data-warehouse/breadcrumb/toc.json) PowerShell cmdlet should be performed in the originating tenant while 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) PowerShell cmdlet should be performed in the destination tenant.
154
+
155
+
Note that the user performing the restore must have proper permissions in both the source and target tenants. At the destination tenant, the user must have a 'GUEST' account with either the 'Owner' or 'Contributor' access permissions to which the dedicated SQL pool (formerly SQL DW) will be restored to.
156
+
157
+
The Powershell script for cross tenant restore works the in the same way as cross-subscription restore when the user is given 'GUEST' access to the destination tenant. As a best practice it is advised to also use the destination Tenant ID along with the destination subscription ID.
158
+
159
+
1. Open a PowerShell terminal.
160
+
2. Update Az.Sql Module to 3.8.0 (or greater) if needed
161
+
3. Connect to your Azure account and list all the subscriptions associated with your account along with its Tenant ID.
162
+
4. Select the subscription that contains the SQL pool to be restored.
163
+
5. List the restore points for the dedicated SQL pool.
164
+
6. Pick the desired restore point using the RestorePointCreationDate.
165
+
7. Create a ‘Guest’ account with either ‘Owner’ or ‘Contributor’ permissions.
166
+
8. Select the destination subscription along with the corresponding Tenant ID to which the SQL pool should be restored.
167
+
9. Restore the dedicated SQL pool to the desired restore point using Restore-AzSqlDatabase PowerShell cmdlet.
168
+
10. Verify that the restored dedicated SQL pool (formerly SQL DW) is online.
0 commit comments