Skip to main content

NAV 2013 R2 - Multi-Tenancy Part 4

Hi all,

Previous Post in this series are -
  - Implementing Multi-Tenancy Part 2.
  - Implementing Multi-Tenancy Part 3.

This post was created due to questions from multiple readers about existence of Default Tenant.
1. Do we need Default Tenant if there are no Companies?
2. Is Default Tenant is Mandatory?

The answer of both the questions is No.

So what we will see in this post is -

1. Move to Default Company in a separate Tenant say Test.
2. Delete the default Tenant.

Currently my SQL SERVER Databases look like as shown below.

What would we would like to achieve after this post is -


1. Initial command remain same as of the previous posts, Prepare Powershell & Importing Modules.

#Prepare PowerShell
Set-ExecutionPolicy unrestricted -Force
Import-Module 'C:\Program Files\Microsoft Dynamics NAV\71\Service\NavAdminTool.ps1'

#Import Module
Import-Module 'D:\Multitenancy\NAVMultitenancySamples.psm1' -Verbose

You need to change these things -
 - Path for Modules.

Run the Command, the Modules are imported.

2. The Commandlet that we will be using for same is HowTo-MoveCompanyToTenant.
So let's Search the command in Command Addon and Provide Parameters as shown.

You can run it directly from the buttons shown below or Copy it. I will copy it and paste it in the Poweshell window & Run it as shown below.

HowTo-MoveCompanyToTenant -CompanyName Default -FromDatabase "ABC Company Database NAV 2013 R2" -NewTenantName Test -OldTenantName default -ServerInstance MultiTenent -DatabaseServer 'localhost\NAVDEMO' -Force -ServiceAccount 'NT AUTHORITY\NETWORK SERVICE' -RemoveCompanyWhenMoved
You need to change parameter as shown above.

So my default company is now moved to Tenant Called Test, Lets have a look on SQL Server.

New Database have been created Named TEST, but "ABC Company Database NAV 2013 R2" database is Still there.

Do we need it?  No.

So lets delete it manually to complete the process.

But Before deleting it, lets see the Tenants exist in the service instance.

We still have the Default tenant we will do need now so let's dismount it. Right click the Tenant and Click dismount.

Now let's delete the Database that is not in use from SQL Server.

Let's open the windows client and check all the Tenants.

This is it, we have migrated from single tenant to a complete MultiTenant Environment.

Stay Tuned for More...

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.