Skip to main content

NAV 2013 R2 - Mutlitenant Concept

Hi all,

With Release of NAV 2013 R2 a New Concept have been coined by Microsoft i.e Multi-tenant.

In this post we will try to understand the concept of Multi tenant and in next post we will see how we can actually implement it with the help of a demo database.



Below lines are from MSDN (view of Microsoft on Multi tenant) -
"Microsoft Dynamics NAV 2013 R2 supports deployments where several different companies access a centrally maintained Microsoft Dynamics NAV application. By using this multitenancy support, you can add new customers to your solution easily, and you can roll out updates quickly with limited downtime for your customers."
"In a multitenant deployment, information about the Microsoft Dynamics NAV application is stored in a separate application database. Your customers’ data is stored in separate business databases, each of which is a tenant in your deployment. By separating application from data, you can deploy the same solution to many customers with centralized maintenance of the application and isolation of each tenant. The application database contains the tables that define an application, such as the Object table and other system tables."

What is Single - Tenant Model?



In Single Tenant Model used till now, Application and Data Reside in Single Database.

To understand it simply i would say that data and Objects resides in a single database (physical & Logical)

What is Multi - Tenant Model?

In a Muti - Tenant Model introduced in NAV 2013 R2 we have an option to Move to Multi Tenant where we break the old database into Two Parts.


Part 1 Application (Objects only & Data Comman to All Companies  Some System Tables)

Part 2 Data (Contain Data Specific to Companies & some System Tables)


Part 2 Can again be break into parts called as Tenant. You can have 1..n Tenant based on your requirement.

System tables in the tenant and application databases -



What benefit I Personally assume using this -

1) Only application Databases is accessible via developer environment. (Security to my database).

2) Databases are now separated based on company requirement. (Increased Performance - Faster Read & Write)

3) Based on Tenant Data, Databases can be stored in separate Disk.

4) Application Objects are shared with all tenant databases.



5) Tenants are separate identity and are not linked to Application Database.



In next set of Posts we will see how we can achieve partial & complete multi Tenant using a Sample Database.

Regards,
Saurav Dhyani

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.