Need help with an active problem
Performance review
Blocking, waits, deadlocks, or broad slowness that is already costing real time.
Database engineer / SQL Server consulting
MihalyKertesz
Practical SQL Server help for teams dealing with performance problems, upgrades, recovery risk, and inherited database environments.
Reviews, troubleshooting, planned change, and the cleanup work that usually gets delayed until something starts to hurt.
How the work usually starts
Most of this starts with one review of the environment, the pressure around it, and what changed recently.
That usually means symptoms, recent changes, deadlines, backup assumptions, and the ownership gaps around them. The goal is a fix order before more time goes into the wrong problem.
SQL Server consultantInstance reviewsSlow system, risky upgrade, unclear ownershipFix, findings, next stepsAvailableEnterprise SQL Server support
SQL Server consultantFix instead of more problemsReview before the next release windowUpgrade, recovery, and monitoring gaps
Typical input
Slow system, risky upgrade, unclear ownership.
What you get
Findings, fix order, and a cleaner answer on what should happen next.
Availability
Review work, troubleshooting, and planned change support.
Common work
Use these when the problem is already clear.
Performance, upgrade, and recovery tend to be the three cases where teams already know what kind of help they need.
Planned change
Upgrade support
Version changes, compatibility risk, rehearsal, rollback, and calmer upgrade windows.
Recovery confidence
Recovery readiness
Backup coverage that sounds fine until someone asks for restore proof and real timing.
Before a call
A few things that usually matter.
Most SQL work starts with the same practical questions. The point is to reduce ambiguity early, not turn it into a long intake ritual.
Input
Symptoms, recent change, current deadline.
Focus
Stabilize first, then clean up what made it fragile.
Output
Findings, fix order, and what should happen next.
When the issue is still broad
Start with a review, not a random fix list.
+
When the issue is still broad
Start with a review, not a random fix list.
If nobody is fully sure whether the real problem is performance, upgrade risk, restore confidence, maintenance drift, or ownership gaps, the fastest useful move is a proper review.
What I usually need
A working picture of the environment and the pressure around it.
+
What I usually need
A working picture of the environment and the pressure around it.
Typical starting material is simple: version, current symptoms, known deadlines, monitoring gaps, backup assumptions, and whether the team is trying to change something soon.
What you get
Findings, a practical fix order, and less ambiguity.
+
What you get
Findings, a practical fix order, and less ambiguity.
The output should help the next decision, not produce more paperwork. That usually means clearer priorities, less hand-waving, and a shorter route to a stable next step.
Worth opening
Useful pages before you get in touch.
Some are directly about SQL work. Some are there if you want wider background on the product and engineering side.
Case study work
Case studies and audit pages
Examples, audit scope, and sample output if you want a better feel for the work first.
Open page
Useful reference
SQL Server updates tracker
A live page built from Microsoft's update source instead of recycled release-note summaries.
Open page
Project work
Passary
One of the product pages if you want wider engineering background beyond the SQL work.
Open page
Profile
Whoami
Role history, enterprise background, and the wider context behind the consulting work.
Open page