Factors causing lag in Microsoft Business Central [Navision]

The main factors causing lag in Microsoft Business Central (formerly Navision) include the use of SharePoint or Excel as a data source, which introduces latency due to constant file access, read/write locks, and the lack of efficient indexing. Any direct integration via OData or connectors can significantly slow down operations.

Poorly designed workflows also contribute to performance issues. Workflows that include unnecessary API calls or excessive table queries create bottlenecks, while those processing large amounts of data without optimization can overload the system.

Recursive queries and poor SQL optimization are another major cause. Poorly written AL or C/AL code can generate recursive SQL queries that strain the database server. Additionally, the absence of proper indexing forces the system to read large amounts of data, slowing down operations.

Excessive use of poorly optimized plugins and customizations can also degrade performance. Badly designed plugins may introduce infinite loops, redundant queries, or delays in event execution. Unoptimized extensions often make excessive server calls, increasing response times.

Database indexing and SQL Server issues further contribute to slowdowns. The lack of indexes on frequently queried tables leads to inefficient data retrieval, while transactions that lock tables can delay critical operations. Poor SQL Server configuration, such as improper memory allocation or cache optimization, can also negatively impact performance.

Infrastructure and server configuration play a crucial role as well. Insufficient CPU, RAM, or slow disk performance can create bottlenecks, while misconfigured SQL Server settings can further compound latency issues.

Lastly, slow integrations and web services add to performance degradation. Poorly configured external integrations, especially those making synchronous web service calls, can block processes. REST or SOAP calls that are not optimized can take excessive time to complete each transaction.

The best approach to resolving these issues is a thorough diagnosis, including log analysis, SQL query monitoring, and reviewing integration architecture.