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

Microsoft Dynamics NAV 2016 - How to Configure Phone Client.

Hi All, In this article we will discuss how we can connect Microsoft Dynamics NAV 2016 with New Client Launched i.e. Phone Client. This Article Contain Steps for a Android Phone as I have Only Android Phone. I am doing it having all tiers on my windows 8 machine, steps remain same for multiple servers but issues might be different. What we Need (Other what we discuss in this article) -  The Service Tier should be on Public IP . Some of the Data-card does not Provide you Public IP. check it for sure.

How to Set Up NavUserPassword Authentication in Business Central.

Hi Readers, In this article we will discuss steps to Setup NAVUserPassword in Business Central on-prem. NavUserPassword is an authentication method that's handled by Business Central Server, but isn't based on Windows users or Active Directory. Each user is set up with a username and password that's configured inside Business Central only. The user is prompted for username/password credentials when they start the client. #msdyn365bc, #credentialtype

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.