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 -



STEPS -

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...

Regards,
Saurav Dhyani
saurav-nav.blogspot.in

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.