Merge pull request #217508 from kavitham10/addMoreContentToTroubleshootingGuide

Add more content to troubleshooting guide

Author: prmerger-automator[bot]

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

@@ -81,10 +81,35 @@ Known issues and limitations associated with the Azure SQL Migration extension f
 
 - **Recommendation**: See [Configure Azure Storage firewalls and virtual networks](/azure/storage/common/storage-network-security) for more information on Azure Storage firewall setup.  
 
+- **Message**: `Migration for Database <Database Name> failed with error 'There are backups from multiple databases in the container folder. Please make sure the container folder has backups from a single database.`
+
+- **Cause**: Backups of multiple databases are in the same container folder.
+
+- **Recommendation**: If migrating multiple databases to **Azure SQL Managed Instance** using the same Azure Blob Storage container, you must place backup files for different databases in separate folders inside the container. See [Migrate databases from SQL Server to SQL Managed Instance by using Log Replay Service (Preview)](/azure/azure-sql/managed-instance/log-replay-service-migrate#limitations) for more information.
+
+
     > [!NOTE]
     > For more information on general troubleshooting steps for Azure SQL Managed Instance errors, see [Known issues with Azure SQL Managed Instance](/azure/azure-sql/managed-instance/doc-changes-updates-known-issues)
 
 ### Error code: 2012 - TestConnectionFailed
+- **Message**: `Failed to test connections using provided Integration Runtime. Error details: 'Remote name could not be resolved.'`
+
+- **Cause**: The Self-Hosted Integration Runtime can't connect to the service back end. This issue is usually caused by network settings in the firewall.
+
+- **Recommendation**: There's a Domain Name System (DNS) issue. Contact your network team to fix the issue. See [Troubleshoot Self-Hosted Integration Runtime](../data-factory/self-hosted-integration-runtime-troubleshoot-guide.md) for more information.
+
+- **Message**: `Failed to test connections using provided Integration Runtime. 'Cannot connect to <File share>. Detail Message: The system could not find the environment option that was entered`
+
+- **Cause**: The Self-Hosted Integration Runtime can't connect to the network file share where the database backups are placed.
+
+- **Recommendation**: Make sure your network file share name is entered correctly.
+
+- **Message**: `Failed to test connections using provided Integration Runtime. The file name does not conform to the naming rules by the data store. Illegal characters in path.`
+
+- **Cause**: The Self-Hosted Integration Runtime can't connect to the network file share where the database backups are placed.
+
+- **Recommendation**: Make sure your network file share name is entered correctly.
+
 - **Message**: `Failed to test connections using provided Integration Runtime.`
 
 - **Cause**: Connection to the Self-Hosted Integration Runtime has failed.
@@ -127,7 +152,7 @@ Known issues and limitations associated with the Azure SQL Migration extension f
 ### Error code: 2039 - MigrationRetryNotAllowed
 - **Message**: `Migration isn't in a retriable state. Migration must be in state WaitForRetry. Current state: <State>, Target server: <Target Server>, Target database: <Target database>.`
 
-**Cause**: A retry request was received when the migration wasn't in a state allowing retrying.
+- **Cause**: A retry request was received when the migration wasn't in a state allowing retrying.
 
 - **Recommendation**: No action required migration is ongoing or completed.  
 
@@ -188,6 +213,9 @@ The Azure SQL Database offline migration (Preview) utilizes Azure Data Factory (
 - Azure SQL Database table names with double byte characters currently aren't supported for migration.  Mitigation is to rename tables before migration; they can be changed back to their original names after successful migration.
 - Tables with large blob columns may fail to migrate due to timeout.
 - Database names with SQL Server reserved words aren't valid.
+- Database names with double-byte character set (DBCS) are currently not supported.
+- Table names that include semicolons are currently not supported.
+- Computed columns do not get migrated.
 
 ## Azure SQL Managed Instance and SQL Server on Azure Virtual Machine known issues and limitations
 - If migrating multiple databases to **Azure SQL Managed Instance** using the same Azure Blob Storage container, you must place backup files for different databases in separate folders inside the container.