Skip to main content

MSDYN365BC 2019 Wave 2 - Upgrading an Modified C/AL Database - Part 4.

Hi Readers,

Thanks for the great response to this series.

In this article, we will do data migration from Business Central 14 to Business Central 2019 Wave 2(15).

During Upgrade we will use Custom Microsoft Base Application Extension that we developed in the Last Article.

This is part 1 of the upgrade which only contains steps that need to be executed in Business Central 14.

For other Articles in this series Refer Here.

#MSDYN365BC #BC2019Wave2

** Again as I said earlier, This approach is just for Demo. I am not suggesting to use this approach, I am just using this for this demo.

Instead of a long Powershell query that needs manual changes I automated the whole upgrade queries in Two Powershell cmdlets and just by changing parameters can be used in any upgrade from Business Central 2019 Wave 2.

So let's see how we can automate it. 

What Steps we execute in Business Central 14 During Upgrade. We will keep all those steps in 1 Powershell cmdlet.

1. Import Powershell Module.
** We load these modules for loading Business Central Powershell commands.

2. Import Developer License.
** We import Developer License to proceed with upgrades.

3. Disable Task Scheduler.
** Disabling Task scheduler is mandatory so that all running Tasks/Job Queue is stopped.

4. Restart NAV Service.
** Restart NAV Service Tier to apply changes done in service.

5. Un-Install all installed Extensions in the database.
** Uninstall all extension as we cannot upgrade with Extension Installed.

6. Un-Install all Symbols.
** Remove all symbols and we will install new symbols for Business Central 2019 Wave 2.

7. Delete all objects in the database other than tables.
** Deleting all objects other than tables as a mandatory step in any NAV/BC data migration.

8. Stop NAV Service Tier for Business Central 14.
** Last but not least we need to clean up all active sessions to the database.

To use the Below PowerShell cmdlet you need to set the Following Parameters.

  1. DatabaseServer - Name of SQL Server.
  2. DatabaseName - Name of SQL Database.
  3. ServiceName - Name of Service that is mapped to the database.
  4. DeveloperLicenseFile - Developer License File Path and Name.

Run all the command once and we should be done with all 8 steps. Below is the Result window.

In the Next Article, we will discuss Data Upgrade Process Steps that need to be executed in Business Central 15.

You can download Part 1 of Upgrade Query from Github.

File Name - 1. Upgrade BC14 To BC15 - Part 1 [Execute in Business Central 14]

Stay tuned for more.
Hope you find it useful.
Let me know your views as a comment on this article.

Saurav Dhyani


Popular posts from this blog

Welcome - Microsoft Dynamics 365!

Hi All, In this article we will discuss the new introduced member of Dynamics Family. Yes you heard it correctly, one more new member with Name "Microsoft Dynamics 365" . #ProjectMadeira   #Dynamics365

Send Mail with Attachment From Navision.

Hi all, We have seen how to save a report into PDF and how to send mail to a customer. Let's link these two post in one i.e. Mailing statement to a customer into PDF Format. This article is part of the Series. Please Refer  Table of Content here . If you have the old objects set let me brief you what I will be changing - 

NAV 2013 Credential Type - How to Use?

Hi all, Please do these activities when you have time, its a long activity and i would suggest do all activities in one go. So be clam and lets start. For NAV 2013 R2 Refer Here. For NAV 2016 Steps have been Reduced Please Refer Here. I have installed NAV 2013 and its work great with my windows credentials. I was checking the service console (Microsoft Dynamics NAV Administration) in NAV 2013 and found out that Credentials Type have multiple Options.