Skip to main content

Use of NAVDEMO Instance in Development Environment


Hi all,

This post is only for the Development Environment where we NAV Technical and Functional Consultants works on Multiple Versions.

Till NAV 2009 R2 there was no issues that we have all the version running without installing even RTC (with some tweaks).

But Let's See what is the issue we faced when NAV 2013 have launched. Below are some facts which I hope you all will agree.



1) We had seen in earlier post how to run multiple RTC (2013/R2/SP1/2009) on same machine.

2) Before RTC Client was launched we had option to save license into the database which will get automatically sets when we open the database.

3) RTC Take License Information from the SQL server. So the license that have been uploaded on server will be used by all RTC Version we will be using.

4) With NAV 2013 License uploaded on SQL Server, we were getting below listed error which working on RTC R2 & SP1.


5) With NAV 2009 R2 License on SQL Server, we were getting below listed error while using NAV 2013.


5) Resolution was Change the license and restart the service when we switch to R2/SP1/2009 to 2013 or vice versa.

Introduction to NAVDEMO Instance -

If we install NAV 2013 a Demo Installation a new instance in SQL Server that is NAVDEMO is created and the NAV 2013 demo database is created under that domain.

We can change to install the database into the Existing SQL Server Instance by selecting the customize option as shown below.


During installation if we leave SQL Server Instance as Blank, then the database get restored on the standard instance of SQL Server.

USE of NAVDEMO Instance in Development Environment -

1) NAVDEMO is a seprate Instance of SQL.

2) The standard Instance is MSSQLSERVER.

My all old Database i.e before NAV 2013 are lying under the standard Instance.
My all NAV 2013 Databases lies under NAVDEMO Instance.

Licence in Standard Instance is of NAV 2009 R2 (Developer License .
*Supported by all NAV Versions expect 2013.

License in NAVDEMO Instance is of NAV 2013 (Developer License).

I never require to change license while starting the service or switching from RTC R2/SP1/2009 to 2013.

I hope the information can be used in developer environment by all.

Please put comment if you like this article.

Regards,
Saurav Dhyani
http://saurav-nav.blogspot.in/

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.