Nikoo Samadi
Poor system performance affects user patience and reduces productivity due to slow pages, lagging posting processes, and delayed reports. As a result, teams become distracted and make more mistakes when response times lag. Therefore, these Business Central performance issues could be impacting your organization.
Although slow performance is rarely a mystery, it remains unclear for many organizations. Common causes include ineffective extensions, poor data design, small environments, or forgotten configuration settings. The challenge, however, is determining where to begin.
To address this, this guide explains how to identify performance symptoms, uncover the underlying causes, and monitor and fix them using built-in tools. Consequently, restoring speed and stability without relying on guesswork becomes a straightforward objective.
Importantly, the steps are the same whether your instance is on-premises or in the cloud: observe, measure, and take action. By following this method, you can address Business Central’s slow performance and maintain system responsiveness as user and data loads grow.
Understanding Business Central Performance
In simple terms, the speed at which the system responds to user actions—such as opening pages, posting transactions, creating reports, performing integrations, or syncing data—is known as Business Central performance. Moreover, performance encompasses delay, speed, and consistency, and therefore cannot be measured by a single metric.
- Latency is the time between a user action and system response (e.g. how many milliseconds it takes to open a list).
- Throughput refers to how many operations the system can handle in parallel (e.g. posting 100 orders in a batch).
- Consistency means performance is predictable over time, not good one hour and terrible the next.
When it comes to Business Central performance problems, slowness can appear as long-running reports, slow posting, page delays, sluggish lookups, or sluggish behavior during periods of high usage. The first step in troubleshooting is to identify these patterns.
Business Central runs on multiple layers:
the client/browser layer, the web/ application service tier, the AL code logic, and the SQL database (or data tier). Performance problems may originate at any layer. For example:
- The browser or network may add latency.
- Extensions or custom AL logic may execute inefficient loops, calculations, or queries.
- The application tier may be under-resourced or improperly configured.
- The SQL database may suffer from missing indexes, fragmentation, or high I/O load.
- Integrations or web services may block user flows if they run synchronously.
To fix performance, you must see where the delay happens. That way you avoid guesses like “it must be the database” when in fact the browser is slow or a poorly written extension is causing delays.
Microsoft’s guidance on how to work with a performance problem emphasizes this layered view: define “slow,” measure with tools, and isolate the bottleneck. Also, the Performance Profiler built into Business Central helps you see which apps or AL objects consume time during a process.
In the next sections, we’ll look at the symptoms you should watch for, then go deeper into common causes, followed by how to troubleshoot, optimize, and prevent future slowness in Business Central performance.
Simplify Your Decision with GEM365
Get in touch with GEM365 to guide you through the process and get consultation for free.
Common Signs of Business Central Performance Issues
If your system shows any of the symptoms below, it’s a strong sign of Business Central performance problems. By keeping an eye out for these signs you can identify problems early on before they cause major problems.
The following are some of the more common and indicative symptoms, along with what they may indicate:
Slow page loading and laggy navigation
When a user opens a page, it takes a few seconds or longer to load. Alternatively, switching between the card and list pages seems to take longer. This is a typical indication of performance problems with Business Central. When rendering is slowed down by extensions, custom logic, or large UI elements, many SaaS users face this.
Caching or setup cost may be at work if a page loads slowly at first but loads quickly later. Community forums document situations where this pattern was produced by upgrading, most likely as a result of changes to caching or extension load order.
Reports and queries taking too long
It can take a while to generate reports or run queries over big datasets. For several seconds, you may see “loading…” or even timeouts. This is an obvious sign of database overload or poor fetching logic.
This further suggests problems with data design or indexing if it happens especially at times like month-end when data volume is high.
Sluggish lookups, searches, or filtering
The system “hangs” or freezes while carrying out a search when users input data into a list or search interface. This lag may result from using wildcard searches on non-indexed fields or across numerous columns.
Also, list or card pages with a lot of FlowFields (computed fields) slow down the page, especially if the values are calculated again each time the page loads.
Delays in posting, saving, or transactions
The system “hangs” or responds unusually slow when users post a batch, commit changes, or submit a sales order. This points to possible weaknesses in the locking, database contention, or transaction logic.
It might also mean that during these operations, custom extension logic (in triggers) is working hard simultaneously.
Resource contention and blocking
Locks may happen if several users attempt to access the same records or tables. It might be necessary for some sessions to wait until others are finished. During simultaneously use, you might notice deadlocks, blocked sessions, or slowdowns.
Also, resource contention can come from frequent tasks or scheduled background jobs running at times which interfere with user activity.
Performance varies by user or location
Slowness is likely to be caused by client or network problems if it only affects specific users, or users in particular offices or regions. For instance:
- One user complains while others don’t
- Access from remote or VPN locations is much slower
- The problem persists only in a particular browser or machine
According to community reports, one user’s connection is slow while another’s within the same residence is fast.
A key factor is network latency; Business Central is built to have client latency (to the data center) of less than 250–300 ms.
These symptoms are significant because they not only irritate users but also reduce productivity, raise the possibility of errors, and can lead to a chain reaction of problems. For instance, retrying actions by users can result in duplicate records; reporting delays can impede decision-making; and slow lookup can result in users working with outdated or inaccurate data.
Additionally, the symptom pattern aids in determining the problem’s layer (client, network, application, database). You can avoid chasing false leads by maintaining that focus.
We’ll examine the typical underlying causes of each of the aforementioned symptoms in the following section. After that, we’ll develop a systematic troubleshooting technique so you can apply fixes wisely rather than heedlessly.
Main Causes of Slow Business Central Performance
Effectively, resolving Business Central performance issues requires understanding the underlying causes. For instance, slowness often falls into predictable categories such as network and client issues, database limitations, extensions and custom code, integrations, and platform or infrastructure constraints.
Network and client-related issues
Slowness may be due to the user-Business Central connection rather than the system itself. Slow page loads for specific users, variations in performance across locations, or lag in remote access are examples of signs.
Common causes:
- High network latency or low bandwidth
- VPN or firewall bottlenecks
- Unsupported or outdated browsers
- Heavy personalization or large browser cache
Fixes: ensure supported browsers, check latency to the data center, optimize VPN configurations, and advise users on efficient browser use.
Data volume and database issues
Slow performance is mostly caused by large tables, inefficient queries, and missing indexes. Slow reports, lengthy posting periods, and lagging lookups are some of the symptoms.
Common causes:
- Unindexed tables or poor indexing strategy
- Large datasets with unoptimized queries
- Excessive use of FlowFields or calculated fields on list pages
- Fragmented indexes or bloated temp tables
Fixes: review and add indexes, archive old data, avoid unnecessary FlowField recalculations, and optimize SQL queries.
Extensions and custom AL code
Although extensions increase functionality, ineffective AL code can cause system lag. Slow page rendering, delayed posting, and uneven performance are some of the symptoms.
Common causes:
- Loops and repeated database calls in triggers like OnAfterGetRecord
- Heavy fact boxes or UI elements on pages
- Synchronous tasks in extensions that could run asynchronously
- Unnecessary recalculations during page load
Fixes: profile the AL code, optimize loops and queries, move heavy logic to background processes, and remove or simplify UI elements.
Web services, APIs, and integrations
If integrations are not carried out carefully, they may prevent regular operations. Slow postings, delayed report generation, or abnormally lengthy batch operations are all warning signs.
Common causes:
- Synchronous API calls that block processes
- Large payloads or unoptimized web service requests
- Multiple integrations running at the same time
- Exposing pages as web service endpoints instead of using queries
Fixes: implement asynchronous integration patterns, limit payload sizes, schedule integrations off-peak, and use queries for external calls rather than pages.
Platform or infrastructure limitations
Your environment itself can be a limiting factor. Symptoms include consistent slowness across all users, or sudden delays at peak times.
Causes in cloud (SaaS) environments:
- Tenant resource throttling
- Execution time limits
- Concurrency constraints
Causes on-premises:
- Insufficient CPU, memory, or disk I/O
- Misconfigured service tiers
- Poor network between database and application tiers
Fixes: monitor and scale cloud resources, check service tier settings, optimize hardware for on-premises, and schedule heavy tasks during off-peak hours.
Fixing and Optimizing Business Central Performance
After identifying the causes of slowdowns, the next step is to apply fixes and optimize the system. The goal is to make Business Central performance faster, consistent, and predictable.
Optimize AL code and extensions
Custom extensions often introduce slowness. Key strategies include:
- Review loops and triggers: Avoid unnecessary loops, especially in OnAfterGetRecord or OnInsert
- Move heavy work to background: Synchronous processes block users. Use scheduled tasks or queues for complex calculations.
- Reduce UI load: Remove or simplify heavy fact boxes, computed fields, or FlowFields that recalc on every page load.
- Profile and refactor: Use the Performance Profiler to identify slow objects or functions, then rewrite inefficient code.
Optimize database and data design
Database issues are a common source of slow performance. Practical steps:
- Add missing indexes: Especially on large tables used frequently in queries.
- Archive old data: Keep operational tables smaller to improve query performance.
- Optimize queries: Rewrite inefficient queries or limit retrieved records.
- Avoid unnecessary recalculations: FlowFields or calculated columns should be used judiciously.
Improve client and network performance
User experience strongly depends on the client and network setup.
- To maintain optimal Business Central performance, start by using supported browsers such as Microsoft Edge or Google Chrome, and ensure they are always up to date.
- Additionally, reduce potential browser cache issues by advising users to clear their cache periodically.
- For remote teams, it’s also important to optimize VPN or network connections to the Business Central service to avoid unnecessary delays.
- Finally, monitor latency regularly — Business Central performs best when client-to-Azure latency stays below 250–300 milliseconds.
Optimize integrations and web services
Slow API calls or integrations often block user actions. Fixes include:
- Use asynchronous integrations: Avoid blocking user actions.
- Limit payload size: Smaller requests execute faster.
- Schedule off-peak jobs: Run large batch operations outside peak hours.
- Use queries instead of pages for web services: Queries are optimized and reduce overhead.
Optimize platform or infrastructure
Depending on deployment type:
- SaaS (cloud): Monitor for tenant throttling or concurrency limits; schedule heavy tasks off-peak.
- On-premises: Ensure CPU, memory, and disk I/O are sufficient; check service tier settings; maintain proper network between database and application tiers.
Test and validate
After applying any fix:
- Rerun the Performance Profiler and measure against your baseline.
- Verify that user actions are faster and reports execute within acceptable times.
- Monitor for side effects to ensure that changes do not introduce new issues.
By applying these strategies, you can ensure that your Business Central performance improves in a measurable and reliable way. Moreover, optimizing AL code, database design, client experience, integrations, and infrastructure together helps prevent recurring slowness and keeps the system consistently responsive.
Preventing Future Business Central Performance Problems
Fixing slow performance is important, but preventing problems is even better. Proactive monitoring and maintenance help ensure Business Central performance remains fast and reliable.
Monitor performance regularly
Regular monitoring lets you detect issues before they affect users:
- Use the Performance Profiler to track page loads, posting times, and report execution.
- Review telemetry and usage patterns to spot recurring bottlenecks.
- Set alerts for long-running operations or high database resource usage.
Maintain database health
Database maintenance is essential for sustained performance:
- Archive old or inactive data to reduce table size.
- Rebuild or reorganize indexes periodically.
- Optimize queries and FlowFields to reduce unnecessary computations.
- Monitor SQL performance metrics, including locks, waits, and I/O usage.
Optimize extensions and customizations
Extensions can add functionality but may also create slowdowns over time:
- Review custom AL code for inefficient loops, triggers, or queries.
- Remove unused extensions or simplify complex UI elements.
- Move heavy operations to background tasks.
- Test new extensions in a sandbox environment before deploying to production.
Plan upgrades and changes carefully
Changes such as new extensions, system updates, or data migrations can affect performance:
- Test all updates in a sandbox before going live.
- Monitor performance immediately after updates.
- Document changes so you can correlate them with any slowdowns.
Train users and IT staff
User habits can also impact performance:
- Educate users on efficient navigation and search practices.
- Avoid opening excessively large lists or reports unnecessarily.
- Ensure IT staff know how to check system health and use built-in tools.
Schedule periodic reviews
Finally, schedule routine performance reviews:
- Check key processes, reports, and extensions.
- Measure page load times, posting, and report execution.
- Identify patterns and optimize before problems grow.
Final Thoughts
Although slow performance in Business Central can be frustrating, it is typically predictable and resolvable. Rather than speculating, you can take targeted action by understanding what Business Central performance entails, identifying common slowness indicators, and determining the underlying causes.
Furthermore, fixes that follow a systematic process of observation, measurement, isolation, and action ensure that the true problems are addressed. For example, faster, more dependable performance can be achieved by optimizing AL code, reviewing extensions, keeping the database up to date, enhancing client and network configurations, and managing integrations.
Equally important, prevention plays a key role. By implementing planned updates, database maintenance, regular monitoring, and user training, consistent speed and responsiveness are maintained over time. Consequently, as your company grows, your team can preserve Business Central’s functionality by combining proactive procedures with troubleshooting.
In addition, taking these actions not only restores productivity but also reduces errors and increases user confidence. As a result, strong Business Central performance supports better decision-making, faster reporting, and more seamless operations.
Table of Contents
Read more
Forbes Reveals the Best Cloud ERP: Here’s Why Business Central Wins
How the Microsoft Power Apps Platform Transforms Manual Processes
Top Power Automate Workflows Every Business Should Use in 2025
