Skip to content
digitapulia.com
Fixed-price engagements

SQL Server performance check

At the end of the month our ERP grinds to a halt.
What we do
We measure the slow queries, the indexes and the configuration of your SQL Server.
How we do it
First we talk to the people who suffer the slowness: which operations become slow, at what times and on which days of the month. Then we measure on your server, at those same moments, which queries take longest and how often they repeat, what the server is left waiting for, which indexes are missing or surplus and how it is configured. We sort the causes by their effect, starting with the ones that cost the most time. The low-risk fixes we apply with your team; the others we leave ready and explained, to be applied when your team decides.
What you receive
The list of causes, sorted by their effect, and the fixes applied or ready to apply.
What changes for you
Month-end close can stop being the moment when no one can work with the system: you know why it was slowing down, what has been fixed and what is left, and the next performance problem starts from a list, not from a blind search.
What we need from you
Access to your SQL Server with permission to read its state and performance, without permission to query the tables; someone who knows the ERP; someone on your team with permission to apply the fixes; and the chance to measure on the days when the problem appears.
Who it is for
IT
How you buy it
At a fixed price: the price is written down before we start and we give it to you when you ask.

Example use cases

These are examples: they do not describe a real client.

  • A beverage distributor in Spain with a subsidiary in Ecuador, whose ERP slows down at month-end close

    The situation

    In the last days of every month, accounting closes the books of both companies, the warehouse prepares the month-end orders and the sales reports all run at once. The ERP takes so long to save an order that the warehouse goes back to writing orders down on paper, and someone has to type them in the next day.

    What we do

    We measure the server during the close. The main cause is a sales report that reads the whole orders table every time someone opens it, and makes everyone else wait in the meantime. We add to the orders table the index that report needs and check it with the company's technical team in a test environment before applying it. The second cause, a memory setting meant for a smaller server, we leave ready to be applied over a weekend.

  • A construction equipment rental company in Italy with an office in Spain, which invoices all its rentals at month-end

    The situation

    At the end of the month, the system prepares the invoices for all of the month's rentals in one go. The process starts in the afternoon and sometimes has not finished by the next morning, when the offices in Italy and Spain need the system to work. No one knows whether the problem is the server, the database or the program itself.

    What we do

    We measure the invoicing process from start to finish. Almost all the time goes on a query that repeats once for every rental instead of reading them all together, and on indexes no one uses but the server updates with every invoice. We hand the company the causes in order: the surplus indexes, after checking that no process needs them, we remove with its technical team, and the fix for the query we leave written down for whoever maintains the program.

Frequently asked questions

Do we need a new server?

Not before measuring. First we see where the time goes: if the cause is a query, an index or the configuration, it is fixed without changing server. If the server really is too small, the list says so and explains why.

Does the system stop while it is being measured?

No. We measure with the system in use, reading what SQL Server itself records, without stopping anyone. Fixes that need a moment with no one using the system are agreed with you.

Who applies the fixes?

The low-risk ones, we apply with your team. The ones that touch the program or need a moment with no one using the system we leave ready and explained, and your team decides when they are applied.