Skip to content

Commit 3b83339

Browse files
committed
[BULK] Replace datamigration.microsoft.com with /data-migration/
Addresses an issue with an SSL error
1 parent 2fefcc1 commit 3b83339

19 files changed

+21
-21
lines changed

Diff for: articles/cosmos-db/mongodb/tutorial-mongotools-cosmos-db.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -175,4 +175,4 @@ After you migrate the data stored in MongoDB database to Azure Cosmos DB’s API
175175

176176
## Next steps
177177

178-
* Review migration guidance for additional scenarios in the Microsoft [Database Migration Guide](https://datamigration.microsoft.com/).
178+
* Review migration guidance for additional scenarios in the Microsoft [Database Migration Guide](/data-migration/).

Diff for: articles/dms/how-to-migrate-ssis-packages-managed-instance.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -147,4 +147,4 @@ After an instance of the service is created, locate it within the Azure portal,
147147

148148
## Next steps
149149

150-
* Review the migration guidance in the Microsoft [Database Migration Guide](https://datamigration.microsoft.com/).
150+
* Review the migration guidance in the Microsoft [Database Migration Guide](/data-migration/).

Diff for: articles/dms/how-to-migrate-ssis-packages.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -110,4 +110,4 @@ If the deployment of your project succeeds without failure, you can select any p
110110

111111
## Next steps
112112

113-
* Review the migration guidance in the Microsoft [Database Migration Guide](https://datamigration.microsoft.com/).
113+
* Review the migration guidance in the Microsoft [Database Migration Guide](/data-migration/).

Diff for: articles/dms/how-to-monitor-migration-activity.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -137,4 +137,4 @@ The following table describes the fields shown in table level migration progress
137137
> CDC values of Insert, Update and Delete and Total Applied may decrease when database is cutover or migration is restarted.
138138
139139
## Next steps
140-
- Review the migration guidance in the Microsoft [Database Migration Guide](https://datamigration.microsoft.com/).
140+
- Review the migration guidance in the Microsoft [Database Migration Guide](/data-migration/).

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

+1-1
Original file line numberDiff line numberDiff line change
@@ -344,4 +344,4 @@ Remove-AzDms -ResourceGroupName myResourceGroup -ServiceName MyDMS
344344

345345
Find out more about Azure Database Migration Service in the article [What is the Azure Database Migration Service?](./dms-overview.md).
346346

347-
For information about additional migrating scenarios (source/target pairs), see the Microsoft [Database Migration Guide](https://datamigration.microsoft.com/).
347+
For information about additional migrating scenarios (source/target pairs), see the Microsoft [Database Migration Guide](/data-migration/).

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

+1-1
Original file line numberDiff line numberDiff line change
@@ -348,7 +348,7 @@ Remove-AzDms -ResourceGroupName myResourceGroup -ServiceName MyDMS
348348

349349
## Additional resources
350350

351-
For information about additional migrating scenarios (source/target pairs), see the Microsoft [Database Migration Guide](https://datamigration.microsoft.com/).
351+
For information about additional migrating scenarios (source/target pairs), see the Microsoft [Database Migration Guide](/data-migration/).
352352

353353
## Next steps
354354

Diff for: articles/dms/howto-sql-server-to-azure-sql-powershell.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -252,4 +252,4 @@ Remove-AzDms -ResourceGroupName myResourceGroup -ServiceName MyDMS
252252

253253
## Next step
254254

255-
* Review the migration guidance in the Microsoft [Database Migration Guide](https://datamigration.microsoft.com/).
255+
* Review the migration guidance in the Microsoft [Database Migration Guide](/data-migration/).

Diff for: articles/dms/resource-custom-roles-sql-database-ads.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -107,4 +107,4 @@ To assign a role to a user or an app ID:
107107

108108
## Next steps
109109

110-
- Review the [migration guidance for your scenario](https://datamigration.microsoft.com/).
110+
- Review the [migration guidance for your scenario](/data-migration/).

Diff for: articles/dms/resource-custom-roles-sql-db-managed-instance-ads.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -119,4 +119,4 @@ To assign a role to users/APP ID, open the Azure portal, perform the following s
119119

120120
## Next steps
121121

122-
* Review the migration guidance for your scenario in the Microsoft [Database Migration Guide](https://datamigration.microsoft.com/).
122+
* Review the migration guidance for your scenario in the Microsoft [Database Migration Guide](/data-migration/).

Diff for: articles/dms/resource-custom-roles-sql-db-managed-instance.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -145,4 +145,4 @@ To assign a role to users/APP ID, open the Azure portal, perform the following s
145145

146146
## Next steps
147147

148-
* Review the migration guidance for your scenario in the Microsoft [Database Migration Guide](https://datamigration.microsoft.com/).
148+
* Review the migration guidance for your scenario in the Microsoft [Database Migration Guide](/data-migration/).

Diff for: articles/dms/resource-custom-roles-sql-db-virtual-machine-ads.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -116,4 +116,4 @@ To assign a role to users/APP ID, open the Azure portal, perform the following s
116116

117117
## Next steps
118118

119-
* Review the migration guidance for your scenario in the Microsoft [Database Migration Guide](https://datamigration.microsoft.com/).
119+
* Review the migration guidance for your scenario in the Microsoft [Database Migration Guide](/data-migration/).

Diff for: articles/dms/tutorial-mongodb-cosmos-db-online.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -265,9 +265,9 @@ After you migrate the data stored in MongoDB database to Azure Cosmos DB for Mon
265265
266266
* [Azure Cosmos DB service information](https://azure.microsoft.com/services/cosmos-db/)
267267
* Trying to do capacity planning for a migration to Azure Cosmos DB?
268-
* If all you know is the number of vcores and servers in your existing database cluster, read about [estimating request units using vCores or vCPUs](../cosmos-db/convert-vcore-to-request-unit.md)
268+
* If all you know is the number of vCores and servers in your existing database cluster, read about [estimating request units using vCores or vCPUs](../cosmos-db/convert-vcore-to-request-unit.md)
269269
* If you know typical request rates for your current database workload, read about [estimating request units using Azure Cosmos DB capacity planner](../cosmos-db/mongodb/estimate-ru-capacity-planner.md)
270270
271271
## Next steps
272272
273-
* Review migration guidance for additional scenarios in the Microsoft [Database Migration Guide](https://datamigration.microsoft.com/).
273+
* Review migration guidance for additional scenarios in the Microsoft [Database Migration Guide](/data-migration/).

Diff for: articles/dms/tutorial-mongodb-cosmos-db.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -235,9 +235,9 @@ After you migrate the data stored in MongoDB database to the Azure Cosmos DB for
235235
## Additional resources
236236
237237
* Trying to do capacity planning for a migration to Azure Cosmos DB?
238-
* If all you know is the number of vcores and servers in your existing database cluster, read about [estimating request units using vCores or vCPUs](../cosmos-db/convert-vcore-to-request-unit.md)
238+
* If all you know is the number of vCores and servers in your existing database cluster, read about [estimating request units using vCores or vCPUs](../cosmos-db/convert-vcore-to-request-unit.md)
239239
* If you know typical request rates for your current database workload, read about [estimating request units using Azure Cosmos DB capacity planner](../cosmos-db/mongodb/estimate-ru-capacity-planner.md)
240240
241241
## Next steps
242242
243-
Review migration guidance for additional scenarios in the [Azure Database Migration Guide](https://datamigration.microsoft.com/).
243+
Review migration guidance for additional scenarios in the [Azure Database Migration Guide](/data-migration/).

Diff for: articles/mysql/TOC.yml

+1-1
Original file line numberDiff line numberDiff line change
@@ -812,4 +812,4 @@
812812
- name: Partners
813813
href: single-server/partners-migration-mysql.md
814814
- name: Database Migration Guide
815-
href: https://datamigration.microsoft.com/
815+
href: /data-migration/

Diff for: articles/mysql/index.yml

+1-1
Original file line numberDiff line numberDiff line change
@@ -119,7 +119,7 @@ landingContent:
119119
- text: Migrate using Data Migration Service
120120
url: single-server/how-to-migrate-online.md
121121
- text: Azure Data migration guide
122-
url: https://datamigration.microsoft.com/scenario/mysql-to-azuremysql?step=1
122+
url: migrate/mysql-on-premises-azure-db/01-mysql-migration-guide-intro.md
123123
- text: Troubleshoot migration errors
124124
url: single-server/how-to-troubleshoot-common-errors.md
125125

Diff for: articles/mysql/migrate/mysql-on-premises-azure-db/08-data-migration.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -124,7 +124,7 @@ If the upgrade checker reports no issues, it's safe to do an in-place upgrade by
124124

125125
## WWI scenario
126126

127-
After successfully migrating the MySQL instance to 8.0, the WWI migration team realized the original [Database Migration Service (DMS)](https://datamigration.microsoft.com/scenario/mysql-to-azuremysql?step=1) migration path could no longer be used as the DMS tool currently only supports 5.6 and 5.7. DMS required network access. The WWI migration team wasn't ready to handle their complex network issues. These environmental issues narrowed their migration tool choice to MySQL Workbench.
127+
After successfully migrating the MySQL instance to 8.0, the WWI migration team realized the original [Database Migration Service (DMS)](01-mysql-migration-guide-intro.md) migration path could no longer be used as the DMS tool currently only supports 5.6 and 5.7. DMS required network access. The WWI migration team wasn't ready to handle their complex network issues. These environmental issues narrowed their migration tool choice to MySQL Workbench.
128128

129129
## Database objects
130130

Diff for: articles/mysql/single-server/concept-performance-best-practices.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -92,7 +92,7 @@ Vertically split load by functionally sharding the database - moving separate ap
9292
## Data import configurations
9393

9494
- You can temporarily scale your instance to higher SKU size before starting a data import operation and then scale it down when the import is successful.
95-
- You can import your data with minimal downtime by using [Azure Database Migration Service (DMS)](https://datamigration.microsoft.com/) for online or offline migrations.
95+
- You can import your data with minimal downtime by using [Azure Database Migration Service (DMS)](../migrate/mysql-on-premises-azure-db/01-mysql-migration-guide-intro.md) for online or offline migrations.
9696

9797
## Azure Database for MySQL memory recommendations
9898

Diff for: articles/mysql/single-server/concepts-migrate-import-export.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ This article explains two common approaches to importing and exporting data to a
1919

2020
For detailed and comprehensive migration guidance, see the [migration guide resources](https://github.com/Azure/azure-mysql/tree/master/MigrationGuide).
2121

22-
For other migration scenarios, see the [Database Migration Guide](https://datamigration.microsoft.com/).
22+
For other migration scenarios, see the [Database Migration Guide](/data-migration/).
2323

2424
## Prerequisites
2525

Diff for: articles/postgresql/TOC.yml

+1-1
Original file line numberDiff line numberDiff line change
@@ -749,4 +749,4 @@
749749
- name: Partners
750750
href: partners-migration-postgresql.md
751751
- name: Database Migration Guide
752-
href: https://datamigration.microsoft.com/
752+
href: /data-migration/

0 commit comments

Comments
 (0)