Skip to content

Commit 67269a1

Browse files
author
Carlos Robles
committed
Adding backtick to line 270
1 parent 4f0b4e6 commit 67269a1

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

articles/dms/known-issues-azure-sql-migration-azure-data-studio.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,7 @@ Known issues and troubleshooting steps associated with the Azure SQL Migration e
3434

3535
- **Message**: `Migration for Database 'DatabaseName' failed with error cannot find server certificate with thumbprint.`
3636

37-
- **Cause**: The source SQL Server instance certificate from a database protected by Transparent Data Encryption (TDE) hasn't been migrated to the target Azure SQL Managed Instance or SQL Server on Azure Virtual Machine before migrating data.
37+
- **Cause**: The source database is protected with Transparent Data Encryption (TDE). You need to migrate the Database Encryption Key (DEK) to the target Azure SQL Managed Instance or SQL Server on Azure Virtual Machine before starting the migration.
3838

3939
- **Recommendation**: Migrate the TDE certificate to the target instance and retry the process. For more information about migrating TDE-enabled databases, see [Tutorial: Migrate TDE-enabled databases (preview) to Azure SQL in Azure Data Studio](/azure/dms/tutorial-transparent-data-encryption-migration-ads).
4040

@@ -94,7 +94,7 @@ Known issues and troubleshooting steps associated with the Azure SQL Migration e
9494

9595
- **Message**: `Failed to test connections using provided Integration Runtime. Error details: 'Remote name could not be resolved.'`
9696

97-
- **Cause**: The Self-Hosted Integration Runtime can't connect to the service back end. This issue is caused by network settings in the firewall.
97+
- **Cause**: DMS cannot connect to Self-Hosted Integration Runtime (SHIR) due to network settings in the firewall.
9898

9999
- **Recommendation**: There's a Domain Name System (DNS) issue. Contact your network team to fix the issue. For more information, see [Troubleshoot Self-Hosted Integration Runtime](../data-factory/self-hosted-integration-runtime-troubleshoot-guide.md).
100100

@@ -253,14 +253,14 @@ WHERE STEP in (3,4,6);
253253

254254
## Error code: Ext_RestoreSettingsError
255255

256-
- **Message**: Unable to read blobs in storage container, exception: The remote server returned an error: (403) Forbidden.;The remote server returned an error: (403) Forbidden
256+
- **Message**: Unable to read blobs in storage container, exception: The remote server returned an error: (403) Forbidden. The remote server returned an error: (403) Forbidden
257257

258258
- **Cause**: Target is unable to connect to blob storage.
259259

260-
- **Recommendation**: Confirm that target network settings allow access to blob storage. For example, if migrating to SQL VM, ensure that outbound connections on VM are not being blocked.
260+
- **Recommendation**: Confirm that target network settings allow access to blob storage. For example, if migrating to SQL VM, ensure that outbound connections on VM aren't being blocked.
261261

262262

263-
- **Message**: Failed to create restore job.;Unable to read blobs in storage container, exception: The remote name could not be resolved.
263+
- **Message**: Failed to create restore job. Unable to read blobs in storage container, exception: The remote name could not be resolved.
264264

265265
- **Cause**: Target is unable to connect to blob storage.
266266

0 commit comments

Comments
 (0)