Merge pull request #277548 from Saisang/sai-includescleanup-dms

[GREAT DIVIDE] Includes clean up dms

Author: v-dirichards

articles/dms/dms-overview.md

@@ -23,9 +23,9 @@ With Azure Database Migration Service currently we offer two versions:
 
 **Database Migration Service (classic)** via Azure portal, PowerShell and Azure CLI is an older version of the Azure Database Migration Service. It offers database modernization to Azure and support scenarios like – SQL Server, PostgreSQL, MySQL, and MongoDB.
 
-[!INCLUDE [Azure Database Migration Service (classic) - SQL scenarios retirement announcement](../../includes/deprecation-announcement-dms-classic-sql.md)]
+[!INCLUDE [Azure Database Migration Service (classic) - SQL scenarios retirement announcement](./includes/deprecation-announcement-dms-classic-sql.md)]
 
-[!INCLUDE [database-migration-service-ads](../../includes/database-migration-service-ads.md)]
+[!INCLUDE [database-migration-service-ads](./includes/database-migration-service-ads.md)]
 
 ## Compare versions
 

articles/dms/howto-sql-server-to-azure-sql-managed-instance-powershell-offline.md

@@ -26,7 +26,7 @@ In this article, you learn how to:
 > * Create a migration project in an instance of Azure Database Migration Service.
 > * Run the migration offline.
 
-[!INCLUDE [online-offline](../../includes/database-migration-service-offline-online.md)]
+[!INCLUDE [online-offline](./includes/database-migration-service-offline-online.md)]
 
 This article provides steps for an offline migration, but it's also possible to migrate [online](howto-sql-server-to-azure-sql-managed-instance-powershell-online.md).
 

articles/dms/howto-sql-server-to-azure-sql-managed-instance-powershell-online.md

@@ -25,7 +25,7 @@ In this article, you learn how to:
 > * Create a migration project in an instance of Azure Database Migration Service.
 > * Run the migration online.
 
-[!INCLUDE [online-offline](../../includes/database-migration-service-offline-online.md)]
+[!INCLUDE [online-offline](./includes/database-migration-service-offline-online.md)]
 
 This article provides steps for an online migration, but it's also possible to migrate [offline](howto-sql-server-to-azure-sql-managed-instance-powershell-offline.md).
 

includes/database-migration-service-ads.md renamed to articles/dms/includes/database-migration-service-ads.md

@@ -21,8 +21,8 @@ Check the following step-by-step tutorials for more information about each speci
 
 | Migration scenario | Migration mode
 |---------|---------|
-SQL Server to Azure SQL Managed Instance| [Online](../articles/dms/tutorial-sql-server-managed-instance-online-ads.md) / [Offline](../articles/dms/tutorial-sql-server-managed-instance-offline-ads.md)
-SQL Server to SQL Server on Azure Virtual Machine|[Online](../articles/dms/tutorial-sql-server-to-virtual-machine-online-ads.md) / [Offline](../articles/dms/tutorial-sql-server-to-virtual-machine-offline-ads.md)
-SQL Server to Azure SQL Database | [Offline](../articles/dms/tutorial-sql-server-azure-sql-database-offline.md)
+SQL Server to Azure SQL Managed Instance| [Online](../tutorial-sql-server-managed-instance-online-ads.md) / [Offline](../tutorial-sql-server-managed-instance-offline-ads.md)
+SQL Server to SQL Server on Azure Virtual Machine|[Online](../tutorial-sql-server-to-virtual-machine-online-ads.md) / [Offline](../tutorial-sql-server-to-virtual-machine-offline-ads.md)
+SQL Server to Azure SQL Database | [Offline](../tutorial-sql-server-azure-sql-database-offline.md)
 
-To learn more, see [Migrate databases with Azure SQL Migration extension for Azure Data Studio](../articles/dms/migration-using-azure-data-studio.md).
+To learn more, see [Migrate databases with Azure SQL Migration extension for Azure Data Studio](../migration-using-azure-data-studio.md).

includes/database-migration-service-instance-create.md renamed to articles/dms/includes/database-migration-service-instance-create.md

@@ -9,15 +9,15 @@ ms.author: pehewitt
 
 1. In the Azure portal menu or on the **Home** page, select **Create a resource**. Search for and select **Azure Database Migration Service**.
 
-    ![Azure Marketplace](./media/database-migration-service-instance-create/portal-marketplace.png)
+    ![Azure Marketplace](../media/portal-marketplace.png)
 
 2. On the **Azure Database Migration Service** screen, select **Create**.
 
-    ![Create Azure Database Migration Service instance](./media/database-migration-service-instance-create/dms-create-1.png)
+    ![Create Azure Database Migration Service instance](../media/dms-create-1.png)
 
     Select the appropriate **Source server type** and **Target server type**, and choose the **Database Migration Service (Classic)** option.
 
-    ![Select Database Migration Service (Classic) scenario](./media/database-migration-service-instance-create/dms-classic-create-2.png)
+    ![Select Database Migration Service (Classic) scenario](../media/dms-classic-create-2.png)
 
 3. On the **Create Migration Service** basics screen:
 
@@ -28,18 +28,18 @@ ms.author: pehewitt
      - Choose **Azure** as the service mode.
      - Select a pricing tier. For more information on costs and pricing tiers, see the [pricing page](https://aka.ms/dms-pricing).
 
-    ![Configure Azure Database Migration Service instance basics settings](./media/database-migration-service-instance-create/dms-settings-1.png)
+    ![Configure Azure Database Migration Service instance basics settings](../media/dms-settings-1.png)
 
      - Select **Next: Networking**.
 
 4. On the **Create Migration Service** networking screen:
 
-    - Select an existing virtual network or create a new one. The virtual network provides Azure Database Migration Service with access to the source server and the target instance. For more information about how to create a virtual network in the Azure portal, see the article [Create a virtual network using the Azure portal](../articles/virtual-network/quick-create-portal.md).
+    - Select an existing virtual network or create a new one. The virtual network provides Azure Database Migration Service with access to the source server and the target instance. For more information about how to create a virtual network in the Azure portal, see the article [Create a virtual network using the Azure portal](../../virtual-network/quick-create-portal.md).
 
-    ![Configure Azure Database Migration Service instance networking settings](./media/database-migration-service-instance-create/dms-settings-2.png)
+    ![Configure Azure Database Migration Service instance networking settings](../media/dms-settings-2.png)
 
     - Select **Review + Create** to review the details and then select **Create** to create the service.
 
     - After a few moments, your instance of the Azure Database Migration service is created and ready to use:
 
-    ![Migration service created](./media/database-migration-service-instance-create/dms-service-created.png)
+    ![Migration service created](../media/dms-service-created.png)

includes/database-migration-service-offline-online.md renamed to articles/dms/includes/database-migration-service-offline-online.md

@@ -11,12 +11,12 @@ Register the Microsoft.DataMigration resource provider before you create your fi
 
 1. Sign in to the Azure portal. Search for and select **Subscriptions**.
 
-   ![Show portal subscriptions](./media/database-migration-service-resource-provider-register/portal-select-subscription.png)
+   ![Show portal subscriptions](../media/portal-select-subscription.png)
 
 2. Select the subscription in which you want to create the instance of Azure Database Migration Service, and then select **Resource providers**.
 
-    ![Show resource providers](./media/database-migration-service-resource-provider-register/portal-select-resource-provider.png)
+    ![Show resource providers](../media/portal-select-resource-provider.png)
 
 3. Search for migration, and then select **Register** for **Microsoft.DataMigration**.
 
-    ![Register resource provider](./media/database-migration-service-resource-provider-register/portal-register-resource-provider.png)    
+    ![Register resource provider](../media/portal-register-resource-provider.png)    

includes/database-migration-service-resource-provider-register.md renamed to articles/dms/includes/database-migration-service-resource-provider-register.md

@@ -7,4 +7,4 @@ ms.service: sql-database
 ms.topic: include
 ---
 > [!IMPORTANT]  
-> **[Azure Database Migration Service (classic) - SQL scenarios are on a deprecation path](https://azure.microsoft.com/updates/retirement-azure-database-migration-service-classic-sql-server-scenarios-deprecation/)**. Since **August 1, 2023**, you're no longer able to create new Database Migration Service (classic) resources for SQL Server scenarios from Azure portal. The service will be retired on **March 15, 2026** for all customers. For seamless migrations from multiple database sources to Azure SQL Targets, Microsoft recommend using the latest version of [Azure Database Migration Service](https://aka.ms/dmslatest), which is available as [Azure SQL Migration](/azure-data-studio/extensions/azure-sql-migration-extension) an extension in Azure Data Studio, or via [Azure Portal](https://aka.ms/dmsazureportal), or through [Azure PowerShell and Azure CLI](../articles/dms/migration-dms-powershell-cli.md). For more information, see [Retirement notice: Database Migration Service (classic)](https://aka.ms/dmsclassicportal).
+> **[Azure Database Migration Service (classic) - SQL scenarios are on a deprecation path](https://azure.microsoft.com/updates/retirement-azure-database-migration-service-classic-sql-server-scenarios-deprecation/)**. Since **August 1, 2023**, you're no longer able to create new Database Migration Service (classic) resources for SQL Server scenarios from Azure portal. The service will be retired on **March 15, 2026** for all customers. For seamless migrations from multiple database sources to Azure SQL Targets, Microsoft recommend using the latest version of [Azure Database Migration Service](https://aka.ms/dmslatest), which is available as [Azure SQL Migration](/azure-data-studio/extensions/azure-sql-migration-extension) an extension in Azure Data Studio, or via [Azure Portal](https://aka.ms/dmsazureportal), or through [Azure PowerShell and Azure CLI](../migration-dms-powershell-cli.md). For more information, see [Retirement notice: Database Migration Service (classic)](https://aka.ms/dmsclassicportal).

includes/deprecation-announcement-dms-classic-sql.md renamed to articles/dms/includes/deprecation-announcement-dms-classic-sql.md

@@ -14,7 +14,7 @@ ms.date: 09/30/2022
   - Reader role for the Azure resource group that contains the target instance of Azure SQL Database
   - Owner or Contributor role for the Azure subscription (required if you create a new instance of Azure Database Migration Service)
 
-  As an alternative to using one of these built-in roles, you can [assign a custom role](../articles/dms/resource-custom-roles-sql-database-ads.md).
+  As an alternative to using one of these built-in roles, you can [assign a custom role](../resource-custom-roles-sql-database-ads.md).
 
   > [!IMPORTANT]
   > An Azure account is required only when you configure the migration steps. An Azure account isn't required for the assessment or to view Azure recommendations in the migration wizard in Azure Data Studio.
@@ -25,4 +25,4 @@ ms.date: 09/30/2022
 
 - Migrate the database schema from source to target by using the [SQL Server dacpac extension](/azure-data-studio/extensions/sql-server-dacpac-extension) or the [SQL Database Projects extension](/azure-data-studio/extensions/sql-database-project-extension) in Azure Data Studio.
 
-- If you're using Azure Database Migration Service for the first time, make sure that the Microsoft.DataMigration [resource provider is registered in your subscription](../articles/dms/quickstart-create-data-migration-service-portal.md#register-the-resource-provider).
+- If you're using Azure Database Migration Service for the first time, make sure that the Microsoft.DataMigration [resource provider is registered in your subscription](../quickstart-create-data-migration-service-portal.md#register-the-resource-provider).

includes/dms-ads-sqldb-prereq.md renamed to articles/dms/includes/dms-ads-sqldb-prereq.md

@@ -14,7 +14,7 @@ ms.date: 09/30/2022
   - Reader role for the Azure resource groups that contain the target instance of Azure SQL Managed Instance or your Azure Storage account
   - Owner or Contributor role for the Azure subscription (required if you create a new Database Migration Service instance)
 
-  As an alternative to using one of these built-in roles, you can [assign a custom role](../articles/dms/resource-custom-roles-sql-database-ads.md).
+  As an alternative to using one of these built-in roles, you can [assign a custom role](../resource-custom-roles-sql-database-ads.md).
 
   > [!IMPORTANT]
   > An Azure account is required only when you configure the migration steps. An Azure account isn't required for the assessment or to view Azure recommendations in the migration wizard in Azure Data Studio.
@@ -28,7 +28,7 @@ ms.date: 09/30/2022
   > [!IMPORTANT]
   >
   > - The Azure SQL Migration extension for Azure Data Studio doesn't take database backups, or neither initiate any database backups on your behalf. Instead, the service uses existing database backup files for the migration.
-  > - If your database backup files are in an SMB network share, [create an Azure storage account](../articles/storage/common/storage-account-create.md) that Database Migration Service can use to upload database backup files to and to migrate databases. Make sure you create the Azure storage account in the same region where you create your instance of Database Migration Service.
+  > - If your database backup files are in an SMB network share, [create an Azure storage account](../../storage/common/storage-account-create.md) that Database Migration Service can use to upload database backup files to and to migrate databases. Make sure you create the Azure storage account in the same region where you create your instance of Database Migration Service.
   > - You can write each backup to either a separate backup file or to multiple backup files. Appending multiple backups such as full and transaction logs into a single backup media isn't supported.
   > - You can provide compressed backups to reduce the likelihood of experiencing potential issues associated with migrating large backups.
 
@@ -39,7 +39,7 @@ ms.date: 09/30/2022
     > [!TIP]
     > If your database contains sensitive data that's protected by [Always Encrypted](/sql/relational-databases/security/encryption/configure-always-encrypted-using-sql-server-management-studio), the migration process automatically migrates your Always Encrypted keys to your target managed instance.
 
-- If your database backups are on a network file share, provide a computer on which you can install a [self-hosted integration runtime](../articles/data-factory/create-self-hosted-integration-runtime.md) to access and migrate database backups. The migration wizard gives you the download link and authentication keys to download and install your self-hosted integration runtime.
+- If your database backups are on a network file share, provide a computer on which you can install a [self-hosted integration runtime](../../data-factory/create-self-hosted-integration-runtime.md) to access and migrate database backups. The migration wizard gives you the download link and authentication keys to download and install your self-hosted integration runtime.
 
    In preparation for the migration, ensure that the computer on which you install the self-hosted integration runtime has the following outbound firewall rules and domain names enabled:
 
@@ -54,6 +54,6 @@ ms.date: 09/30/2022
 
 - If you use a self-hosted integration runtime, make sure that the computer on which the runtime is installed can connect to the source SQL Server instance and the network file share where backup files are located.
 
-- Enable outbound port 445 to allow access to the network file share. For more information, see [recommendations for using a self-hosted integration runtime](../articles/dms/migration-using-azure-data-studio.md#recommendations-for-using-a-self-hosted-integration-runtime-for-database-migrations).
+- Enable outbound port 445 to allow access to the network file share. For more information, see [recommendations for using a self-hosted integration runtime](../migration-using-azure-data-studio.md#recommendations-for-using-a-self-hosted-integration-runtime-for-database-migrations).
 
-- If you're using Database Migration Service for the first time, make sure that the Microsoft.DataMigration resource provider is registered in your subscription. You can complete the steps to [register the resource provider](../articles/dms/quickstart-create-data-migration-service-portal.md#register-the-resource-provider).
+- If you're using Database Migration Service for the first time, make sure that the Microsoft.DataMigration resource provider is registered in your subscription. You can complete the steps to [register the resource provider](../quickstart-create-data-migration-service-portal.md#register-the-resource-provider).