Skip to content
MTF Srl — Making The Future
← All articles

November 20, 2026 · SAP Business One

SAP Business One running slow: find out why before buying hardware

When SAP Business One slows down, the first instinct is to blame the server. It is almost always something else: a database that has grown without maintenance, reports without filters, customisations nobody has reviewed in years. Measure before you spend.

byAlessandro Cimino · Head of development

Illustration: a wide channel where many gold cubes queue up in front of a narrow constriction; past the gate, where the channel opens again, only two widely spaced cubes get through.

In short

When SAP Business One gets slow, the request that reaches the partner is almost always the same: we need a more powerful server. Sometimes that is true. Far more often the server is the one thing that is not at fault, and money gets spent without fixing anything. This article lists the causes that come up most often, how to tell them apart, and why measuring comes before buying.

”It’s slow” is not a diagnosis

Before hunting for a cause, narrow down the symptom. The questions are obvious, which is exactly why nobody asks them.

QuestionWhy it changes everything
Slow doing what?Opening a document, saving, printing and running a report are four different paths through the system.
For whom?One workstation points to the client or the network. Everyone at once points to the database or the server.
Since when?Always, since an upgrade, since month-end, since a new colleague joined.
At what time?If it slows down every day at the same hour, look for what starts at that hour.

That last row alone solves more cases than you would think: backups, antivirus scans and scheduled jobs running during working hours are among the most common culprits, and moving them costs nothing.

The causes that come up most often

The database grew, the maintenance did not

An ERP in production for years accumulates millions of rows. Without periodic maintenance — indexes, statistics, archiving of old data — operations that were instant at go-live become heavy. It is not a fault: it is the predictable consequence of something nobody planned for.

Reports and queries without filters

A Crystal Reports report reading the entire history instead of the current year, or a query run with no conditions, ties up the database for everyone. The symptom is distinctive: the system is slow while someone is running that report, and back to normal the moment it finishes.

Customisations nobody has reviewed in years

User-defined fields, formatted searches, approval procedures and add-ons: each adds work to every operation. Individually they go unnoticed; layered over years they do not — especially the ones written for a requirement that has since changed or disappeared.

The network and the workstation, not the server

SAP Business One is a thick client: if people work over VPN, in a remote desktop session or on a slow link, the bottleneck is the connection, not the machine. The same goes for a PC short on memory or with a dying disk. A new server changes nothing here, because the problem is at the other end of the cable.

Sizing, when it really is that

It happens, and it is the only item on this list that money solves: not enough memory on SAP HANA, a disk that is too slow, resources shared with other virtual machines. The difference from the other cases is that it can be demonstrated with numbers, before the purchase order is signed.

What not to do first

Buy hardware. It is the most expensive option and the least likely to hit the target. If the cause is a query or a backup running at ten in the morning, a new server buys a marginal improvement and the problem returns unchanged a few months later.

Reboot and hope. A reboot hides the symptom and wipes the evidence of what was going on.

Upgrade “just in case”. An upgrade may fix things, but done without knowing what you are looking for it is one more change to rule out when the problem persists.

The analysis: what we do, and what it costs

Nothing. The analysis is free, and it serves us first of all: it tells us whether there is anything worth doing.

We connect to your environment and look at the state of the database, which operations actually weigh, what runs during working hours and how the active customisations are built. At the end we tell you what the cause is and what fixing it is worth. If you want to go ahead, we carry out the work; if you would rather stop there, the diagnosis is yours all the same.

Frequently asked questions

Does work have to stop during the analysis?

No. The system is examined while it is in use: that is precisely when the things that matter show up.

Does it work if our SAP B1 is managed by another partner?

Yes. We need your consent and the access required to carry out the check.

Does it apply to SAP B1 on SQL as well as SAP HANA?

Yes. What you look at differs, the method does not: narrow the symptom, measure, then decide.

What if the server really is the cause?

We will tell you, with the numbers that prove it. It is the only way to buy the right machine rather than the biggest one.

What MTF does here

MTF is an SAP Silver Partner and has worked on SAP Business One only since 2017. The team that configures the ERP and the team that writes the software are in the same company: that is why an analysis like this does not stop at “the database is big”, but gets to which operation weighs and why, with the data to back it.

From there we start from what you need. We propose the solutions that best fit your requirements and the way you work — not the biggest package, but the one that solves your problem — and we decide together where it makes sense to begin.

Want to see it in your company?

Tailored demo on your process, no generic slides.