How GeoDataTek Resolved Business Central Performance Issues for 700 Users

Introduction

Microsoft Dynamics 365 Business Central performance degradation is one of the most disruptive challenges enterprise organizations face as they scale. When our team at GeoDataTek began working with a large sports goods manufacturer, we inherited an ERP environment under serious strain — and what we discovered was a textbook case of how unchecked growth can push even a modern ERP platform to its limits.

The client was running the latest on-premises version of Microsoft Dynamics 365 Business Central, supporting over 400 full and limited-user accounts plus more than 300 device-user handhelds. In total, around 700 active users depended on the system daily — and the platform was struggling to keep up.

This case study outlines what we found, what we did, and the measurable results we achieved through a structured, phased performance optimization program.

The Problem: A System Under Serious Strain

As usage grew, performance degradation became painfully obvious across every department. Everyday business routines that should have taken seconds were taking minutes — or failing entirely:

• Warehouse shipping slowed because “Post Shipment” actions froze under load
• Invoice posting and month-end inventory valuation lagged or locked up entirely
• Heavy reports — especially inventory valuation and financial reports — ran for hours and blocked other users from working
• Handheld scan-guns used on the warehouse floor stalled while posting or accessing data during peak hours
• The database carried several years of transactional history, which compounded every performance issue

Departments began pointing fingers — Finance blamed Warehouse, Warehouse blamed Reporting. In reality, the problem was entirely systemic and required a structured technical investigation to resolve properly.

Root Cause Analysis: What We Found

Our technical team spent four to six weeks doing a deep dive into logs, workloads, and usage patterns to pinpoint the actual root causes. The investigation revealed a combination of interconnected issues:

• Table locks caused by heavy posting tasks running during peak business hours
• Unoptimized reports and queries scanning large ledger tables without proper indexing
• Background jobs overlapping with critical user-facing operations — competing for the same database resources
• Missing SQL reindexing and significant database fragmentation built up over years
• Heavy manual dependencies for validations — discounts, freight, and contact lookups — adding unnecessary processing load
• Device and network constraints amplifying the impact of server-side bottlenecks on warehouse handhelds
• Bulk postings during business hours creating resource contention across all user sessions simultaneously

With root causes clearly identified, we launched a structured, phased performance improvement program designed to deliver immediate relief while building toward long-term scalability.

Phase 1 — Immediate Performance Improvements

The first phase focused on quick wins that would provide immediate relief to the most critical pain points:

• Reindexed all major database tables and cleaned up and archived old transactional data
• Scheduled weekly log-archiving and regular database maintenance routines
• Upgraded virtual machine compute power to give the system more headroom under load
• Isolated background automation jobs to prevent them competing with live user operations
• Moved batch posting tasks to off-peak hours to free up daytime resources for user-facing operations
• Automated shipping document (Bill of Lading) postings to reduce manual processing load on warehouse staff

Phase 2 — Ongoing Scaling Optimizations

The second phase addressed deeper structural issues that required more involved changes to workflows, integrations, and system architecture:

• Introduced after-hours “ready-to-post” processing for invoices and batch jobs — removing the peak-hour processing burden entirely
• Migrated web orders from SOAP to faster OData and REST API calls — dramatically improving integration performance
• Optimized heavy reports and removed unnecessary locking behavior in the inventory valuation process
• Reworked device-to-user assignments for warehouse handhelds to improve throughput and reduce stalling under concurrency

Phase 3 — Strategic Architecture and Future Roadmap

The third phase focuses on longer-term architectural changes that will support continued growth beyond the current user base:

• Planning microservices-based integrations for third-party systems to reduce direct database dependencies
• Evaluating separate environments for Warehouse and Finance to isolate load and prevent cross-departmental resource contention
• Streamlining month-end close workflows to reduce the processing window required
• Automating bulk order updates and improving WMS connectivity for warehouse handhelds

Results: Measurable Impact Across the Organization

The results of the optimization program were measurable and immediate across every affected area:

• Table locks dropped by approximately 70% during peak load and heavy operations
• Invoice posting, shipment posting, and month-end reports now run smoothly and reliably without freezing
• Handheld scan-guns respond quickly even during high concurrency periods in the warehouse
• Web inventory updates reflect instantly following the OData migration
• Automation ensures round-the-clock availability without manual bottlenecks slowing operations
• Cross-team efficiency and confidence improved significantly — Finance, Warehouse, and Operations now collaborate without waiting on the system

Why This Matters for Enterprise Business Central Users

Enterprise-scale environments on Microsoft Dynamics 365 Business Central — especially on-premises deployments — frequently run into performance ceilings as transactional volume, user concurrency, connected devices, and historical data grow together. Without active performance tuning and architecture adjustments, even the latest version of Business Central can choke under load.

Performance optimization is never a one-time effort. It requires continuous measurement, proactive infrastructure management, smart scheduling of resource-intensive tasks, better indexing and data hygiene, and genuine collaboration across technical and business teams.

This client’s journey proves that with disciplined optimization and a structured approach, you can transform a struggling ERP environment — even one supporting 700 users and heavy warehouse throughput — into a stable, scalable, and future-ready platform.

Frequently Asked Questions

1. What causes performance issues in Microsoft Dynamics 365 Business Central?

The most common causes of Business Central performance degradation include database table locks from concurrent heavy posting, unoptimized queries scanning large ledger tables, background jobs competing with user-facing operations, database fragmentation from missing SQL reindexing, and accumulated years of transactional history without archiving. In on-premises environments, VM compute limitations and network constraints also play a significant role.

2. How many users can Microsoft Dynamics 365 Business Central support?

Business Central can support large user bases — this case involved 700 active users including full users, limited users, and warehouse handheld devices. However, performance at scale depends heavily on proper infrastructure sizing, database maintenance, background job scheduling, and query optimization. Without these, even smaller user counts can experience significant degradation during peak hours.

3. What is the difference between Business Central on-premises and cloud performance?

Cloud-hosted Business Central (SaaS) benefits from Microsoft-managed infrastructure, automatic scaling, and built-in performance optimizations that on-premises deployments do not receive automatically. On-premises environments give organizations more control but require active management of database maintenance, VM sizing, SQL reindexing, and background job scheduling to maintain performance at scale.

4. How long does a Business Central performance optimization project take?

Based on this engagement, initial root cause analysis took four to six weeks of deep investigation into logs, workloads, and usage patterns. Immediate improvements were implemented in parallel and began showing results within weeks. Ongoing and strategic optimizations continue as part of a longer-term roadmap. The timeline varies depending on environment complexity, user count, and the depth of existing performance issues.

5. What is SQL table locking and how does it affect Business Central?

SQL table locking occurs when a database operation — such as a bulk posting or heavy report — holds a lock on a database table, preventing other users or processes from reading or writing to it simultaneously. In Business Central, this commonly causes shipment posting to freeze, invoices to fail, and reports to block other users from working. In this case, targeted optimization reduced table locks by approximately 70% during peak operations.

6. How can GeoDataTek help with Business Central performance issues?

GeoDataTek provides end-to-end Microsoft Dynamics 365 Business Central performance assessment, optimization, and managed support services. Our team investigates root causes through detailed log and workload analysis, implements both immediate and strategic improvements, and builds a long-term roadmap for sustainable performance at scale. Learn more through our Microsoft Dynamics 365 services and client case studies.

Conclusion

Microsoft Dynamics 365 Business Central performance optimization is not a luxury for enterprise users — it is a operational necessity. As this case study demonstrates, performance issues at scale are rarely caused by a single factor. They are systemic, interconnected, and require a structured investigation and phased approach to resolve effectively.

GeoDataTek’s team helped this client move from a system that was blocking daily operations across Finance, Warehouse, and Operations — to a stable, automated, and scalable ERP platform that 700 users rely on with confidence.

Learn more about how GeoDataTek supports Microsoft Dynamics 365 environments through our Dynamics 365 Finance services, Power BI analytics solutions, and client case studies.

Explore our blogs and resources for more insights on Microsoft Dynamics 365 performance, implementation, and optimization.

Is your Business Central environment showing signs of performance strain? Connect with GeoDataTek today and let our experts assess and optimize your ERP environment before it impacts your operations.