Skip to main content

NAV 2013 R2 - Multi-Tenancy Part 2

Hi all,

Previous Post in this series are -
  - MutiTenant Concept.
  - Implementing Multi -Tenancy Part 1.

In This post we will move to next steps to configure Service and Mounting Databases.

Till Now, We have separated the Application and Data Part.


3. Prepare NST for MutiTenancy.
   - Stop the NST.
   - Set MutiTenant to True.
   - Set the Database Name to Blank.
   - Start the NST.
   - Mount the App Data Created in Step 2.

Delete the content of Powershell and Paste Below Commands.
#Prepare NST for Multilatency
Set-NAVServerInstance MultiTenent -Stop
Set-NAVServerConfiguration -ServerInstance MultiTenent -Keyname Multitenant -KeyValue "True"
Set-NAVServerConfiguration -ServerInstance MultiTenent -Keyname DatabaseName -KeyValue ""
Set-NAVServerInstance MultiTenent -Start
Mount-NAVApplication -DatabaseServer "localhost\NAVDEMO" -DatabaseName Customer_App_Data -ServerInstance MultiTenent

Change the Service Instance and Application Database Name. Run the Command and output will be as shown below.

Let's see what changes have been done on the Service Tier.

Database name changed to application database and MultiTenant Set to True.

If you Try to Connect the Windows Client you will end up with the error message as below.

Why this Error?

Because we haven't Mounted Any Tenants.

so i think we can move to Next Step, Mounting Customer Data as Tenants.

4. Create Tenants.

Delete the content of Powershell and Paste Below Commands.
#Mount Customer Database as Tenant
Mount-NAVTenant -ServerInstance MultiTenent -Id Default -DatabaseName "ABC Company Database NAV 2013 R2" -OverWriteTenantIDInDatabase

Change the Customer Database Name & Tenant name if required (Default is default).
Run the Command and output will be as shown below.

Now if you try to connect to Navision Windows Client you can connect after changing the Server URL

From - ServerName:Port/InstanceName

TO - ServerName:Port/InstanceName/Tenant Name

In My Case it Changed from  localhost:8046/Multitenent

TO localhost:8046/Multitenent/Default

Now we can see all the companies in the Tenant. We have achieved "Partial MultiTenancy".

Commands used in this post can be found in My Sky Drive Folder.

File Name - Command 4 - Prepare NST & Mount Customer Database.ps1

In Next Post we will see how we can Break the Customer data Tenants into Further Tenants.

By Saurav Dhyani


Popular posts from this blog

VIEW SERVER STATE permission on SQL Server?

Hi all, Sometime While trying to Login into a database we face an error message as shown below. --------------------------- Microsoft Dynamics NAV Classic --------------------------- You cannot start Microsoft Dynamics NAV Classic because you do not have the VIEW SERVER STATE permission on SQL Server. Contact your system administrator. --------------------------- OK    ---------------------------

NAV 2013 R2 - Cumulative update 12 Released.

Hi all, Please find below the details of  Cumulative Update 12 released for Microsoft Dynamics NAV 2013 R2. Title - Cumulative Update 12 for Microsoft Dynamics NAV 2013 R2 Build No. - 38053 Release Date - October, 2014 Local Version Included - AU, AT, BE, CH, DE, DK, ES, FI, FR, IS, IT, NA, NL, NO, NZ, SE, UK, RU Download Link Note: Implementing this cumulative update will require a database conversion unless you have already implemented update rollup 5.

NAV 2013 Upgrade Part III - Data Upgrading.

Hi all, As per agenda we need to discuss the data upgrade in NAV 2013. The process is similar to what used to be till NAV 2009 R2 but with some changes. Let's start the process. Remember -  1) You can only upgrade a database to NAV 2013 from NAV 2009 SP1 / R2 SQL Only. 2) The Synchronization of users with SQL Server is no more required.