Skip to main content

How Optimizing Microsoft Dynamics NAV / Business Central Can Save You From Trouble.

Problem Statement:


After my client's implementation in NAV, the system was working smooth and flawlessly. An important issue was that the client couldn't close their books due to the change in Business Processes and even the customization was evolving as per the changing Business Process. This lead to serious slowing down of the system, filtering and finding records was a pain.

When all the options ran out, we default to calling the Microsoft Support for help!
They suggested upgrading the NAV CU versions which was way painful as all the data needed to migrate and again the system would face a downtime which my client couldn't afford!!

Out of nowhere we were suggested reindexing the tables in NAV which were impacted the most as a periodic activity.

Pre-requisites:

  • Microsoft SQL Server Management Studio (SSMS)
  • Microsoft Dynamics NAV
  • Understanding of SQL
  • Understanding of NAV Server Instance 

Reference:

https://docs.microsoft.com/en-us/powershell/module/microsoft.dynamics.nav.management/restart-navserverinstance?view=businesscentral-ps-15
https://blog.sqlauthority.com/2007/01/31/sql-server-reindexing-database-tables-and-update-statistics-on-tables/

Solution:

1. Restart NAV Server instance using PowerShell and Task Scheduler:
Create a PowerShell with the below command.

Restart-NAVServerInstance -ServerInstance <NavServerInstanceName> -Flags


Then add the Powershell to Task scheduler to schedule the Restart of the NAV Server Instance.

Trigger for Task Scheduler
TaskScheduler calling PowerShell Script

2. Restart SQL Server to free-up RAM using PowerShell and Task Scheduler:

SQL Server by design consumes a lot of RAM and does not free it up. You can limit the RAM usage but this doesn't account for higher runtime performance during maximum load.

Create a PowerShell Script to restart SQL Server

Get-Module -Name VMware* -ListAvailable | Import-Module Restart-Service -Force 'MSSQLSERVER' 
Import-Module SQLPS -DisableNameChecking Set-Service SQLBrowser -StartupType Automatic Start-Service "SQLBrowser" 
$instanceName = "localhost" 
$managedComputer = New-Object Microsoft.SqlServer.Management.Smo.Wmi.ManagedComputer 
$sqlServerAgentInstance = $managedComputer.Services['<YOUR SQL SERVER NAME>'] 
$sqlServerAgentInstance.Start()

Again, you add this to TaskScheduler.

3. Re-Index the tables in the SQL DB:
Reindexing the table in SQL DB is a maintenance activity that speeds up the fetching activity for Microsoft Dynamics NAV / Business Central.

Reindexing SQL Script
Creating Script (Stored Procedure ) which runs reindexing for each of the tables in the Database.

Executing Reindexing Stored Procedures

Executing the Stored Procedure for ReIndexing. The Stored Procedure for Reindexing can also be triggered as a Job in SQL.

Conclusion:
Thus using these techniques you can optimize your existing NAV/ Business Central On-Premise. Although Restarting NAV Server Instance and SQL Server help in optimizing NAV for the day to day usage.
A long term and a periodic solution are using Re-Indexing which typically boosts performance from 50% - 60%. I have observed that a page which would take 10-15mins to load, takes around 5 mins to load.


Comments

Popular posts from this blog

Something went wrong. An Error occurred - Error Resolution

Introduction: With the installation of NAV 2018 or BC On-premise, I have observed that when creating New Server Instance and New WebServer Instance, you will get the error 'Something went wrong. An Error occurred '. I referred to the community questions below but didn't find my resolution. Hence, I decided to write this blog. Pre-requisites: Microsoft Dynamics Business Central - On-Premise / NAV 2018 Understanding of Business Central Authentication  Books & References: https://community.dynamics.com/nav/f/microsoft-dynamics-nav-forum/261301/nav-2018-web-client-an-error-has-occurred https://community.dynamics.com/business/f/dynamics-365-business-central-forum/421987/error-something-went-wrong-an-error-has-occurred-azure-ad-tenant Demonstration: 1. Creation of NAVServerInstance: In order to create NAVServerInstance, you can either add the Server Instance through Business Central Administration or Powershell command. Add Instance - Business Central Administration Add Insta

How to resolve 'Edit in Excel' issues

  Introduction: As you know that D365 BC offers Edit in Excel functionality. But manipulating or customizing such a  standard functionality is difficult as there is not much control available. Hence, solving issues is also a difficult task. I will be resolving the issue for this specific issue, however, the debugging steps are similar. Pre- requisites : ODATA V4 Connectivity tool for Webservices Microsoft Dynamics 365 Business Central Books & References: https://community.dynamics.com/business/f/dynamics-365-business-central-forum/448226/issue-with-excel-add-in/ Demonstration: The way Edit in Excel works is that for a given page a Webservice is created adding PageID and Page Name. Hence, there are some Webservice connectivity checks in place to validate. 1. Edit in Excel Custom Action on the page: If you are adding Edit in Excel Action on the page, please ensure that you are providing appropriate PageName and Filter criteria as Webservice is using these parameters Refer Editworkshe

Installing LS Central - POS on local machine

Introduction: In this blog, I'm attempting to capture the LS Central - POS installation process on Local Machine. This blog has nothing to do LS Central - Server Setup for POS. LS Retail / LS Central - On Premise POS Pre- requisites : LS Central Installed on Server SSL Setup on LS Server (https://www.olisterr.tech/2020/03/how-to-setup-navuserpassword-with-ssl.html) LS - POS Installer Business Central - On Premise Installer Demonstration: Once your LS Retail / LS Central POS is setup on the main server. Just prior to Go-Live, you will actually have to install this POS on multiple systems and connect these POS to the main server with LS Retail / LS Central. 0.Preparation: Prior to actually installing Business Central On-Premise Windows Client, you need to make sure that you're able to ping the target with the correct Port number. For this I made use of PS-Ping tool.  PSPing - IP Address: Port If you're unable to PS-Ping the correct IP with Port number, simply check the Advan