Performances

With Microsoft Dynamics NAV, performance is the responsibility of the implementor, unless the cause is to be found in the standard application. In this case, Microsoft needs to respond and provide a hotfix or guidance regarding how to resolve it.

As a partner or customer, you might make your own decision to choose whatever hardware resources you want, according to your budget. As a partner or customer, you might change whatever configuration parameter in your Microsoft SQL Server or Microsoft Dynamics NAV Server and/or decide to customize the application in its core to be tailored perfectly and tightly to your business needs and growth pace.

One of the biggest advantages of Microsoft Dynamics NAV, compared to all the other ERP products in the world: It is open to almost every kind of customization and uses an object-based language that’s pretty simple to learn and master.

But, with great power comes great responsibility.

If your hardware resource implementation and/or your configuration settings and/or custom application code changes bring the overall application to slow down, in terms of performance, compared to the baseline, then it is also your duty to investigate, troubleshoot, and mitigate the issue.

You break it, you fix it.

The Microsoft Dynamics 365 Business Central, as all modern SaaS propositions, comes with a fully tested standard application targeted for the SMB load. So, what is the SMB load? There is no rule of thumb but just a raw and simple definition for the SMB territory, from a marketing perspective, which is described like a business application used by 1 up to 250 users. This broad marketing concept does not appropriately match with objective technical considerations. Most probably, the definition could or should potentially be changed in favor of a number of transactions, per unit of time. But also this measure, in some circumstances, could be not enough to let stakeholders decide what hardware to buy and which configuration to apply.

Microsoft Dynamics 365 Business Central comes equipped with a very high technology telemetry implemented at all software and hardware levels. The Microsoft operation service engineers could quickly determine whether there are performance issues, whether these are hardware or software based, whether these affect single or multiple tenants, and in a short time determine the root cause of these and mitigate them, at the required cloud speed.

If the root cause is not isolated but potentially applies to all tenants (for example, a missing database index or a suboptimal code), then this will be ported to the application or infrastructure and in the next iteration, also known as a tenant update, so that all the customers will clearly benefit from this.