Optimizing cloud migration performance
This article outlines practical steps that you can take to enhance the performance of your cloud migration, especially when dealing with large databases. By implementing these measures, you can improve the efficiency and reliability of the migration process while minimizing the risk of data loss or downtime.
Tip
We continually work on improving and optimizing the migration tool for larger database sizes. For example, customers can buy more environments, and they can buy extra storage. For more information, see Managing Capacity. If more assistance is required, contact support as described in Escalating support issues to Microsoft.
Deploy source database to Azure SQL Database
If you're migrating a large amount of data, we recommend deploying your source database to an Azure SQL Database instead of using an on-premises SQL Server. Azure SQL Database eliminates the need to install and maintain a self-hosted integration runtime on-premises and ensures faster data replication. An easy way to deploy to Azure SQL is to use the Deploy Database to Microsoft Azure SQL Database wizard in SQL Server Management Studio.
When using the wizard, consider the service tier of the new Azure SQL database carefully. The lowest configurations may not be adequate for migrating large amounts of data. To choose the right balance between performance and price, consider factors such as the size of your source database, the required level of performance, and your budget. You can tune the service tier later in Azure portal if necessary.
Upscale Azure SQL Database
If you're using Azure SQL Database to migrate your on-premises database, you can monitor CPU and memory utilization in the Azure portal to ensure optimal performance. To monitor utilization, use [Metrics]((/azure/azure-sql/database/monitoring-sql-database-azure-monitor?view=azuresql) for Azure Sql Database in the Azure portal. Metrics shows you real-time performance data for your database, including CPU and memory usage.
If you notice high consumption of CPU and memory, it may be time to upscale your database. Upscaling the database can improve performance by providing more resources for your database to work with. For more information about upscaling, visit Dynamically scale database resources with minimal downtime. Keep in mind that upscaling increases the cost of your database, so weigh the benefits against the cost before making any changes.
By monitoring and upscaling your Azure SQL Database as needed, you can ensure optimal performance and avoid performance issues caused by resource constraints.
You can always downscale whenever data replication isn't running.
Reduce the number of companies migrated
The cloud migration capabilities are optimized to migrate data in batches of up to 250 companies. However, a Business Central on-premises or Dynamics NAV database often includes more companies. In some cases, the database contains several hundred companies. Consider reducing the number of companies that you migrate.
You can specify which companies to include in the migration in the Cloud Migration Setup assisted setup guide and view the migration status of each company in the Cloud Migration Management page.
If you want to add more companies after the first selection of companies, you can add more companies in the Cloud Migration Management page in Business Central online. For more information, see Run the tool multiple times. But use the Capacity section of the Business Central administration center to keep track of how much data you migrate.
Tip
On page 9035 Data Administration, you can find reports that are used to compress or cleanup the data. In earlier Business Central versions, the page may not be present. However, most reports can be found using Search .
Here are our recommendations for how to manage companies during the migration:
Break the migration into batches.
If the companies include large data sets, break the migration into smaller batches.
For example, you're migrating 10 companies, but two companies include 50 GB each plus 30-GB shared data. In this example, we recommend that you migrate each of the large companies individually.
Be mindful of any extensions that might complicate the migration as described in Data from extensions.
Check that the company names are valid. For more information, see Company names in the Troubleshooting article.
When moving many companies, use Cloud Migration APIs.
For more information, go to Cloud Migration API Overview. Find samples in the BC Tech GitHub repo.
Update statistics and reorganize indexes
Update statistics and reorganize indexes on all tables on the source database. For more information, see the documentation for sp_updatestats (Transact-SQL) and Resolve index fragmentation by reorganizing or rebuilding indexes.
Use dedicated SQL Server
Use an SQL Server instance installed with a copy of the source database and is only used for cloud migration.
Skip API data upgrade
You might experience a long running data upgrade because of the API upgrade. In this case, you can skip the API data upgrade on a company basis during the cloud migration process, and then run it afterwards going live on the tenant. The only consequence is that the company will start using APIs a bit later.
There are two ways to skip the API data upgrade during cloud migration. One way is disable it as part of the on-premises upgrade process. The other way is to disable using cloud migration management in the Business Central online environment.
From the online environment
Sign in to Business Cental online.
Search for and open the Cloud Migration Management page.
Select the Manage API Upgrade action to open the API upgrade overview page.
To disable the API data upgrade for a company, do the following steps:
On the API upgrade overview page, select the company in the Company Name column.
The API Data Upgrade List opens in a new browser tab.
On the API Data Upgrade List page, select Disable API Data Upgrades > OK.
You can close the API Data Upgrade List tab after you make the selection.
Repeat the previous step for each company you want to disable the API data upgrade.
To show the changes you've made, refresh (F5) the API upgrade overview page.
If you are running upgrade On-Premise
You can use the following SQL query to skip upgrade for a single company
DECLARE @UpgTag nvarchar(250);
SET @UpgTag = UPPER('MS-469217-DisableAPIDataUpgrade-20230411')
INSERT INTO [dbo].[Upgrade Tags$63ca2fa4-4f03-4f2b-a480-172fef340d3f] (Tag, [Tag Timestamp], [Skipped Upgrade], Company)
VALUES (
UPPER(@UpgTag),
'1753-01-01 00:00:00.000',
1,
UPPER('SetCompanyName')
);
You can use the following SQL query to skip upgrade for all companies
DECLARE @UpgTag nvarchar(250);
SET @UpgTag = UPPER('MS-469217-DisableAPIDataUpgrade-20230411')
INSERT INTO [dbo].[Upgrade Tags$63ca2fa4-4f03-4f2b-a480-172fef340d3f] (Tag, [Tag Timestamp], [Skipped Upgrade], Company)
SELECT
UPPER(@UpgTag),
'SetDate',
1,
UPPER([Name])
FROM
Company
WHERE
UPPER([Name]) NOT IN (
SELECT [Company]
FROM [Upgrade Tags$63ca2fa4-4f03-4f2b-a480-172fef340d3f]
WHERE Tag = UPPER(@UpgTag)
)
Completing API upgrade after going live
Sign in to Business Cental online.
Search for and open the Cloud Migration Management page.
Select the Manage API Upgrade action to open the API upgrade overview page.
To disable the API data upgrade for a company, do the following steps:
On the API upgrade overview page, select the company in the Company Name column.
The API Data Upgrade List opens in a new browser tab.
On the API Data Upgrade List page, select Disable API Data Upgrades > OK.
You can close the API Data Upgrade List tab after you make the selection.
Repeat the previous step for every company where you want to disable the API data upgrade.
To show the changes you've made, refresh (F5) the API upgrade overview page.
Go to the cloud migration management page and invoke the action 'Manage API Upgrade'. On the 'API upgrade overview' page that opens for each company that is marked as upgrade disabled, invoke the link to open the page in that company. Select all records, invoke the action reset and then with all records selected invoke the "Schedule Upgrades" action. Start the job queue entry that opens. Repeat the same steps for each of the companies you have skipped.
You can check the status on the API Upgrade overview page and restart the job queue if it fails, it will continue at the point where it has stopped. It is safe to run the job queue as it will commit and release the locks, it should not cause any performance degradation.
Next steps
Commentaires
Bientôt disponible : Tout au long de 2024, nous allons supprimer progressivement GitHub Issues comme mécanisme de commentaires pour le contenu et le remplacer par un nouveau système de commentaires. Pour plus d’informations, consultez https://aka.ms/ContentUserFeedback.
Envoyer et afficher des commentaires pour