Skip to main content

Where My License Is Saved in SQL Database?

Hi all,

I received a Query from One of my Blog Reader -

a) From Where I can change or save License in the database?

b) When I save License where does it actually get stored?

In the article we will be discussing above points, so if you don't know the answers of above questions do read ahead.


So let's start with First Question i.e. -

From Where I can change or save License in the database?

In NAV Database we have two options from where we can change or save database.

1. From Tools - License Information. (Known to All).


2. From Alter Database, Integration Tab.


So Now as we know from where i can Save / Upload / Change License in Navision Database, lets see where it actually get Saved.

2. When i save License where does it actually get stored?

When i Upload a License From Tools - License Information - Upload, the License get stored in SQL Server and is applicable to all database in the server which docent have License Saved in Database.

The License actually get stored in Master Database, Table - $ndo$srvproperty, as shown below -


When i Save License in Database from Alter Database options it get stored in Table - $ndo$dbproperty within the database as shown below -


The Priority will be of the License that is Saved within the Database. If there is No License in Database then the License file uploaded on Server is considered.

Below is the summary of all the Licence related actions that we have -


Hope you understand it and it clear your doubts about License.

Stay Tuned for More.

Regards,
Saurav Dhyani
www.sauravdhyani.com

Comments

  1. Hey Saurav,

    Absolutely loved your explanation about the NAV Licenses. Thank you!!!
    I have only one question here. Would you know which Table Column in SQL stores that "Save license in database" field?

    ReplyDelete
    Replies
    1. There is only on column in table called "license".

      Delete

Post a Comment

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.