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
Copy file name to clipboardExpand all lines: articles/dms/faq.yml
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -274,9 +274,9 @@ sections:
274
274
* Temporarily scale up your Azure SQL Database target instance to the Premium tier SKU during the data migration operation to minimize Azure SQL Database throttling that may affect data transfer activities when using lower-level SKUs.
275
275
276
276
For DMS-
277
-
* DMS uses SHIR node as its compute, if you are copying backups from local file share to Azure blob storage OR while performing migration to Target Azure SQL DB. So ensure to monitor the resrouce usage of SHIR node.
277
+
* If you are copying backups from local fileshare to Azure blob storage OR while performing migration to Target Azure SQL DB, DMS uses SHIR node as its compute. So ensure to monitor the resource usage of that SHIR node.
278
278
* Temporarily scale up your Azure SQL Database target instance to the Premium tier SKU during the data migration operation to minimize Azure SQL Database disk throttling that may affect data transfer activities when using lower-level SKUs.
279
-
* For more detailed information, refer [blog](https://techcommunity.microsoft.com/t5/microsoft-data-migration-blog/improving-sql-db-migration-performance-azure-database-migration/ba-p/3968094)
279
+
* For more detailed information, refer [blog](https://techcommunity.microsoft.com/t5/microsoft-data-migration-blog/improving-sql-db-migration-performance-azure-database-migration/ba-p/3968094).
0 commit comments