Skip to main content

#msdyn365bc - How Do I Create an Empty Database?

Hi Readers,

This article based on a question that I have. 

In Dynamics NAV World you can create a new database in Dynamics NAV Development Environment and import objects in database.

With Business Central Era all base Microsoft objects are now part of Base and System App's.

In this article, we will discuss about steps to create a new database, with Business Central on-prem.

You can use Administration Shell or use PowerShell ISE as Administrator.

If you are using PowerShell ISE, You will need to import Business Central Module to get commands loaded. 

Sample Import Command - (BC18) 

Import-Module 'C:\Program Files\Microsoft Dynamics 365 Business Central\180\Service\NavAdminTool.ps1'

1. Create a New Database.

Use Command New-NAVApplicationDatabase, This command needs Database Name, Database Server Name and Database Location.

** Database Location - Is the Path where database files will get stored.


2. Connect Database to Service Instance.

Create a New Service or Change an Existing Business Central Service.

Update Database Server and Database Name in Service.



3. Import License in Database and Restart Service.

To Import License file You can use PowerShell cmdlet, Import-NAVServerLicense.

To Restart Server Instance, use PowerShell cmdlet, Restart-NAVServerInstance.


4. Synchronize NAV Tenant.

To Synchronize Tenant you can use PowerShell cmdlet, Sync-NAVTenant with parameter Service Name.

5. The First Application (Extension) to Publish is System Application.

This Extension have all system objects. To Add a New Extension three commands are required - 

  • Publish-NAVApp, Sync-NAVApp & Install-NAVApp 
** You can find extension file in the product DVD.



6. Try Connecting Client.

When you try to connect to client, you will be see below error message. This means we will require to add a new company.



7.  Create New Company.

To Create a New Company use PowerShell cmdlet New-NAVCompany. 

** This command will require two parameters is Company Name and Service Name.



8.  Try Connecting Client.

Now client will be accessible but as there are no application object in database we will not be able to access any object.




9.  The Second Application (Extension) to Publish is Base Application.

This Extension have all Microsoft objects. To Add a New Extension three commands are required - 

  • Publish-NAVApp, Sync-NAVApp & Install-NAVApp 
** You can find extension file in the product DVD inside Application Folder.



10.  The Another Import Extension for Developers You need to Install Application Extension.

This Extension have all Microsoft objects. To Add a New Extension three commands are required - 

  • Publish-NAVApp, Sync-NAVApp & Install-NAVApp 
** You can find extension file in the product DVD inside Application Folder.



11.  Try Connecting Client.

Now client will be accessible with all base Microsoft objects.



Let me know your views on this article.

Regards,
Saurav Dhyani

www.sauravdhyani.com 

Comments

Popular posts from this blog

BC 21 and Higher - PowerShell Cmdlet (Replacement of Business Central Administration).

Hi Readers, As discussed in last article about deprecating of Business Central Administration, there are few common actions that we use in administration till Business Central 20. For our on-prem customers, we will still require doing activities. As Microsoft suggest we need to start using PowerShell cmdlet.    Let's see how to do those via PowerShell, or Administration Shell. I will be keep adding commands as you comment to this article.

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 - 

MSDYN365BC - Data Upgrade To Microsoft Dynamics 365 Business Central on premises.

Hi Readers, We have already talked about the number of steps for upgrading to Business Central on Premises from different NAV versions. After that article, I received multiple requests for an article which list down steps for Data Migration. In this article, we will discuss steps of data migration to MSDYN365BC (on-Prem) from NAV 2017. For this article, I am considering a Cronus Demo Database without any customization. For an actual upgrade project, we will have to complete object merge using compare and Merge process. After the Merge Process, the next step is data migration. Let's discuss those steps. Direct Upgrade to Microsoft Dynamics 365 Business Central (on-Prem) is from following versions - 1. NAV 2015. 2. NAV 2016. 3. NAV 2017. 4. NAV 2018.