Skip to main content

Resolution to Cloud Migration Error - Enable Change Tracking in DB

Introduction:

While I was trying to upgrade BC14 On-Premise to BC22 Saas, I noticed the following error in Cloud Migration Setup.

Business Central Cloud Migration Error "Change tracking must be enabled in the source database with a recommended retention period of at least three days"

This blog provides a step-by-step guide on how to resolve this issue.

To know how to setup Cloud Migration follow the link - Cloud Migration Setup



Pre-requisites:

  • Understanding of Cloud Migration
  • Business Central v14 On-Premise
  • Business Central Saas Subscription

Books & References:

https://www.olisterr.tech/2022/03/migrating-data-from-business-central-on.html

https://learn.microsoft.com/en-us/sql/relational-databases/track-changes/about-change-tracking-sql-server?view=sql-server-ver16

Demonstration: 

1. Error scenario: While setting up the Cloud migration with BC On-premise to BC Saas, I got the error 
Change tracking must be enabled in the source database with a recommended retention period of at least three days.

I tried clearing logs and restarting the SQL Server but I kept on getting this error consistently.


2. Resolution: Upon a quick Google search it was clear that a configuration in Database had to be changed.
I ran the SQL query as follows

 ALTER DATABASE BC140TEST
SET CHANGE_TRACKING = ON
(CHANGE_RETENTION = 5 DAYS, AUTO_CLEANUP = ON);

GO

However, I was presented with another error from SQL DB.


Knowing that Change Tracking is enabled but probably the retention period is shorter than 3 days.
Hence, I right-clicked on DB > Properties > Change Tracking I found where we can change the configuration.


I changed the Retention period to 3 Days and tried again.
I was able to connect.

Conclusion:

Change tracking is needed to identify the changes that happened in SQL DB.
By default Business Central Cloud Migration requires 3 Days of change tracking enabled.

I hope this helps



Comments

Popular posts from this blog

Something went wrong. An Error occurred - Error Resolution

Introduction: With the installation of NAV 2018 or BC On-premise, I have observed that when creating New Server Instance and New WebServer Instance, you will get the error 'Something went wrong. An Error occurred '. I referred to the community questions below but didn't find my resolution. Hence, I decided to write this blog. Pre-requisites: Microsoft Dynamics Business Central - On-Premise / NAV 2018 Understanding of Business Central Authentication  Books & References: https://community.dynamics.com/nav/f/microsoft-dynamics-nav-forum/261301/nav-2018-web-client-an-error-has-occurred https://community.dynamics.com/business/f/dynamics-365-business-central-forum/421987/error-something-went-wrong-an-error-has-occurred-azure-ad-tenant Demonstration: 1. Creation of NAVServerInstance: In order to create NAVServerInstance, you can either add the Server Instance through Business Central Administration or Powershell command. Add Instance - Business Central Administration Add Insta...

How to resolve 'Edit in Excel' issues

  Introduction: As you know that D365 BC offers Edit in Excel functionality. But manipulating or customizing such a  standard functionality is difficult as there is not much control available. Hence, solving issues is also a difficult task. I will be resolving the issue for this specific issue, however, the debugging steps are similar. Pre- requisites : ODATA V4 Connectivity tool for Webservices Microsoft Dynamics 365 Business Central Books & References: https://community.dynamics.com/business/f/dynamics-365-business-central-forum/448226/issue-with-excel-add-in/ Demonstration: The way Edit in Excel works is that for a given page a Webservice is created adding PageID and Page Name. Hence, there are some Webservice connectivity checks in place to validate. 1. Edit in Excel Custom Action on the page: If you are adding Edit in Excel Action on the page, please ensure that you are providing appropriate PageName and Filter criteria as Webservice is using these parameters Refer Ed...

Installing LS Central - POS on local machine

Introduction: In this blog, I'm attempting to capture the LS Central - POS installation process on Local Machine. This blog has nothing to do LS Central - Server Setup for POS. LS Retail / LS Central - On Premise POS Pre- requisites : LS Central Installed on Server SSL Setup on LS Server (https://www.olisterr.tech/2020/03/how-to-setup-navuserpassword-with-ssl.html) LS - POS Installer Business Central - On Premise Installer Demonstration: Once your LS Retail / LS Central POS is setup on the main server. Just prior to Go-Live, you will actually have to install this POS on multiple systems and connect these POS to the main server with LS Retail / LS Central. 0.Preparation: Prior to actually installing Business Central On-Premise Windows Client, you need to make sure that you're able to ping the target with the correct Port number. For this I made use of PS-Ping tool.  PSPing - IP Address: Port If you're unable to PS-Ping the correct IP with Port number, simply check the Advan...