SQL — Systems
SQL Server DBA
Tuning, maintenance and rescue on Microsoft SQL Server. Slow queries, locks, backups, indexes — your database responds again.
A slow database wears people down: every ERP screen that takes ten seconds is hours lost per month, multiplied by every person in the company.
What I do
- Performance tuning: slow queries found and optimized, missing or redundant indexes, statistics, execution plans.
- Rescue: locks and deadlocks, corrupted databases, runaway transaction logs, exhausted space, emergency restores.
- Backup and restore: strategies that fit the data (full/differential/log), with documented test restores.
- Preventive maintenance: integrity checks, index rebuilds, growth monitoring.
- Migrations and upgrades: supported versions, instance moves, consolidations.
The method: measure before touching
Every intervention starts from numbers — waits, reads, durations — and ends with the same numbers measured again. “It feels faster” becomes a documented comparison (a query going from 2.4 seconds to 38 milliseconds speaks for itself).
Frequently asked questions
Our ERP is slow and the vendor says "it's the server". Can you verify that?
The most common scenario. I analyze queries, indexes, waits and configuration and show you with numbers where the problem is — sometimes the database, sometimes the application, sometimes the hardware. Then the right thing gets fixed.
Can you work without stopping production?
Almost always. Most tuning work (indexes, statistics, configuration) happens live or in agreed windows of a few minutes.
Do you offer periodic preventive checks?
Yes. A periodic check-up on integrity, backups, indexes and growth prevents most emergencies. It's the cheapest way to run a database.