Skip to content

Commit 9f60571

Browse files
20220513 0835 updated screenshot, alt text for compliance
1 parent f496438 commit 9f60571

File tree

2 files changed

+4
-4
lines changed

2 files changed

+4
-4
lines changed

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

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -164,12 +164,12 @@ Get-AzSubscription
164164
Select-AzSubscription -SubscriptionName $SourceSubscriptionName
165165
166166
# list all restore points
167-
Get-AzSynapseSqlPoolRestorePoint -ResourceGroupName $ResourceGroupName -WorkspaceName $SourceWorkspaceName -Name $SourceSQLPoolName
167+
Get-AzSynapseSqlPoolRestorePoint -ResourceGroupName $SourceResourceGroupName -WorkspaceName $SourceWorkspaceName -Name $SourceSQLPoolName
168168
# Pick desired restore point using RestorePointCreationDate "xx/xx/xxxx xx:xx:xx xx"
169169
$PointInTime="<RestorePointCreationDate>"
170170
171171
# Get the specific SQL pool to restore
172-
$SQLPool = Get-AzSynapseSqlPool -ResourceGroupName $ResourceGroupName -WorkspaceName $SourceWorkspaceName -Name $SourceSQLPoolName
172+
$SQLPool = Get-AzSynapseSqlPool -ResourceGroupName $SourceResourceGroupName -WorkspaceName $SourceWorkspaceName -Name $SourceSQLPoolName
173173
# Transform Synapse SQL pool resource ID to SQL database ID because currently the restore command only accepts the SQL database ID format.
174174
$DatabaseID = $SQLPool.Id -replace "Microsoft.Synapse", "Microsoft.Sql" `
175175
-replace "workspaces", "servers" `
@@ -200,9 +200,9 @@ $RestoredDatabase.status
200200

201201
## Troubleshooting
202202
A restore operation can result in a deployment failure based on a "RequestTimeout" exception.
203-
![Screenshot of timeout exception.](../media/sql-pools/restore-sql-pool-troubleshooting-01.png)
203+
![Screenshot from resource group deployments dialog of a timeout exception.](../media/sql-pools/restore-sql-pool-troubleshooting-01.png)
204204
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".
205-
![Screenshot of SQL pool restoring.](../media/sql-pools/restore-sql-pool-troubleshooting-02.png)
205+
![Screenshot of SQL pool dialog with the status that shows restoring.](../media/sql-pools/restore-sql-pool-troubleshooting-02.png)
206206

207207
## Next Steps
208208

374 Bytes
Loading

0 commit comments

Comments
 (0)