Service
Health audit
For environments that still run, but need a broader review before the next upgrade, incident, or handover.
Services / SQL Server consulting
I help with SQL Server production issues that need technical review, practical decisions, and clear next steps.
This is for performance trouble, upgrade risk, recovery questions, unclear setup problems, or several of these at the same time.
How the work usually starts
Send the SQL Server version, topology, urgency, and the evidence already available: waits, plans, backup history, job output, monitoring, or error logs.
Input
Symptoms, recent change, current deadline.
Review
Performance, recovery, upgrade, monitoring, or ownership risk.
Output
Findings, action order, and what can wait.
Services
Choose a specific service when the work is mainly performance, recovery, upgrades, or a health audit.
Service
For environments that still run, but need a broader review before the next upgrade, incident, or handover.
Service
For blocking, waits, deadlocks, or broad slowness when the team needs a clearer diagnosis.
Service
For version changes where compatibility, rehearsal, rollback, or validation need a stronger review.
Service
For restore paths, failover assumptions, and disaster recovery plans that need testing or review.
When to book
Book SQL Server consulting when the work crosses several areas. The system may be slow, the upgrade plan may need review, and the recovery process may still be untested.
If the need is clearly performance, recovery readiness, or upgrade support, the narrower service pages are faster. If several problems overlap, start with a broader review.
For teams that own a SQL Server environment they did not build and need a clear review of what is already in place.
For blocking, waits, deadlocks, slow periods, or workload changes where the cause is still not clear.
For upgrades, migrations, rollouts, or infrastructure moves that still need rehearsal, rollback planning, or validation.
For environments where backups exist but restore testing, failover behavior, or recovery timing is not proven.
Coverage
I can review the SQL Server areas around the reported issue, including performance, recovery, upgrades, monitoring, and day-to-day operations.
Performance
Review waits, blocking chains, deadlocks, plan changes, indexing problems, statistics, and workload timing before changing production settings.
Health
Check backups, restore confidence, maintenance jobs, tempdb, configuration, ownership, alerting, documentation, and recent review gaps.
Change
Review version targets, compatibility level, deprecated behavior, rehearsal quality, rollback path, downtime, and validation before the change window.
Recovery
Review restore order, RPO and RTO assumptions, failover behavior, Always On or clustering context, backup chain quality, and recovery runbooks.
Operations
Review SQL Agent jobs, error logs, alert thresholds, failed maintenance, growth trends, security drift, and the signals the team already collects.
Capacity
Review whether the current instance, storage, memory, CPU, edition, licensing, and topology still fit the workload and expected change.
Process
We start with the problem and the SQL Server environment around it, then review the evidence, agree the next actions, and decide what should wait.
What to send
Version, topology, symptoms, evidence.
What I check
Performance, recovery, upgrade, monitoring.
What you get
Findings, recommendations, action order.
Step
Send the SQL Server version, topology, current symptom, planned change, and any evidence you already have: waits, plans, backup history, job output, monitoring, or error logs.
Step
I check the parts that match the problem: performance, recovery, upgrade readiness, monitoring, capacity, security, configuration, or unclear ownership risk.
Step
The review separates urgent production risk from cleanup work, then puts the next actions in a practical order.
Step
You get the findings, recommended changes, the evidence behind them, and the items that should wait.
Remote DBA and consulting
I can help with focused SQL Server consulting for a decision, review, migration, performance problem, or recovery concern.
If ongoing DBA support is the better fit, the review should make that clear.
Working style and pricing
I review the environment, test risky assumptions, and leave the team with a clearer order of work. Remote delivery works for most SQL Server consulting because the work depends on evidence and context.
My hourly rate starts at 140 EUR. Larger scopes can be quoted separately when the problem is already well defined. The first message does not need a polished brief.
Guides and proof
These guides cover SQL Server consulting topics that often need more detail than a service card can provide.
Guide
For environments with weak documentation, unclear ownership, or too many unknowns around backups, jobs, configuration, and support.
Open guide
Guide
For work that can be reviewed and handled remotely: performance checks, upgrade planning, recovery review, and production troubleshooting.
Open guide
Guide
For teams comparing a direct consultant with a larger vendor, especially when speed, access, and technical ownership matter.
Open guide
Guide
For performance problems where waits, blocking, plan changes, and workload timing need to be reviewed together.
Open guide
Related page
My background, roles, and the kind of production SQL Server work I have handled.
Related page
Anonymized examples of SQL Server audits, upgrades, monitoring gaps, recovery reviews, and production cleanup work.
Related page
Common SQL Server symptoms and the checks that usually help narrow them down.
When to bring in SQL Server help
I usually get involved when a SQL Server issue affects production, blocks a planned change, or needs a second review before someone changes settings.
That can mean checking wait stats, blocking, backup history, restore testing, SQL Agent jobs, upgrade notes, server configuration, or monitoring data.
The output should be clear enough to act on: what to fix now, what to check next, and what can wait.
Send a short summary: version, environment, urgency, and the main problem or planned change.
FAQ
The work usually covers performance issues, upgrade risk, recovery confidence, unclear ownership, supportability questions, and the broader operational picture around a production SQL Server environment.
Yes. Remote delivery is the default for most review-led SQL Server work when the team can share enough context, access, and evidence.
Yes. That includes readiness review, rehearsal, rollback planning, validation, and a technical check of the proposed change.
Yes. That includes blocking, waits, deadlocks, broad slowness, unstable workload behavior, and the investigation needed to narrow the real bottleneck.
No. Any team running SQL Server in production can need help with unclear ownership, untested recovery, performance problems, or change risk.
Version, environment type, urgency, whether production is already affected, and a short description of the main issue or planned change are enough.