Is Your Business Central On-Premise Server Slowing You Down?

Why Microsoft's Minimum Specs Are a Trap

Microsoft's official documentation lists the lowest possible hardware that will allow Business Central to install and technically run. Think of it like the minimum octane rating for your car: it will start, but you would not tow a trailer uphill on it.

The moment your implementation includes industry-specific add-ons, extra extensions, or a modified application layer — which is extremely common in food, manufacturing, distribution, and other verticals — those minimums are no longer relevant. Your system needs more memory, faster processors, and better disk performance just to keep up with day-to-day operations, let alone peak periods like month-end or year-end.

The Real-World Cost of Under-Specced Servers

Slow performance is not just an IT annoyance. It is a business cost. When warehouse staff wait ten seconds for every page to load, that adds up to hours of lost productivity every week. When finance cannot close the books on time because reports take forever to run, deadlines slip and leadership loses confidence in the numbers.

Worse, an underpowered server environment tends to degrade over time. As your data grows and you add users or extensions, performance drops further. By the time someone finally investigates, the company may have been losing productivity for months or even years.

What a Properly Sized Environment Actually Looks Like

Business Central runs on a three-tier architecture: a web server layer, an application server layer, and a database layer. For companies with around 25 users or fewer, a proven approach is to place the application server and web server together on one machine, and the SQL database on a separate, dedicated machine.

The application and web server should have at least 32 GB of memory and modern multi-core processors. The database server needs even more — 64 GB of memory or higher — along with fast SAS or SSD drives configured for redundancy. These are not extravagant numbers. They are the baseline for a system that will perform well today and still have headroom as your business grows.

It is also important to use SQL Server Standard edition, not SQL Server Express, for any production environment. Express has hard limits on database size and available memory that will eventually choke a live business system. Express is fine for testing, but it has no place running your real operations.

Dedicated Servers, Virtual Machines, or Cloud Hosting?

Once you decide on an on-premise deployment, you still have choices. You can run on a physical server in your own office, on virtual machines managed in-house using platforms like Hyper-V, or on virtual machines hosted by a cloud provider such as Microsoft Azure.

Each option has trade-offs in cost, control, and complexity. A physical server in your office gives you full control but requires on-site IT expertise and physical security. Virtual machines — whether self-hosted or cloud-hosted — offer more flexibility and easier disaster recovery, but they need to be sized correctly. A virtual machine with too few resources assigned to it will perform just as poorly as an undersized physical server.

The right choice depends on your IT capabilities, your budget, and how much risk you are comfortable managing yourself. What matters most is that whichever path you choose, the hardware specifications match the actual demands of your business — not just the minimums on a Microsoft documentation page.

Planning for the Future, Not Just Today

The biggest mistake companies make is sizing their servers for the number of users and the data volume they have right now. Business Central environments grow. You will add users, install new extensions, and accumulate years of transaction history.

A well-planned deployment accounts for at least two to three years of growth. Investing a little more in memory, processing power, and disk performance at deployment time is dramatically cheaper than re-platforming a year later when everything grinds to a halt.