01
No full-time DBA
Someone owns the server, but SQL Server is only part of their job.
SQL Server DBA support
MihalyKertesz
Monthly SQL Server DBA support for companies that run SQL Server.
I help with performance issues, backups, SQL Agent jobs, monitoring, upgrades, restore testing, and planned changes through regular monthly DBA support.
Monthly DBA support
Production SQL Server
Remote work
Performance / recovery / upgrades
Monthly support
How monthly DBA support works
Support usually starts with a small fit check. If the work matches, we agree a monthly rhythm for review, troubleshooting, planned changes, and the priority list.
Best when you want regular senior SQL Server help, not a one-off opinion.
SQL Server consultantMonthly DBA supportInstance reviewsSlow server, upgrade risk, weak monitoringFindings in priority orderRemote work availableProduction SQL Server operations
Remote SQL Server DBA supportFix the right thing firstReview before the next release windowBackups, jobs, monitoring, upgrades
Monthly review
Backups, jobs, monitoring, storage growth, and error logs.
Problem work
Waits, blocking, deadlocks, slow queries, and failed jobs.
Planned changes
Upgrades, patches, migrations, compatibility checks, and rollback planning.
Priority list
What to fix now, what can wait, and what needs more detail.
Book monthly DBA support when
SQL Server matters, but nobody has enough time to keep checking it properly.
Monthly support fits best when the server is important, the work is recurring, and the next risk should not wait for an incident.
02
Older SQL Server setup
The system works, but the notes, version, jobs, or maintenance need a proper look.
03
Weak monitoring
Problems show up late, or alerts do not say enough to decide what to fix.
04
Backup/Restore validation
Backups exist, but nobody is comfortable saying what would happen during recovery.
05
Recurring performance issues
Slow queries, blocking, waits, or failed jobs keep coming back.
06
Upgrade or audit coming up
You need compatibility checks, rollback planning, or a calmer review before the window.
07
High availability needs review
Always On, failover, quorum, alerts, or runbooks need checking before they are trusted.
My services
Monthly DBA support is the main service. These are the usual ways companies start.
Why companies ask me to look at SQL Server
Most SQL Server work needs calm production experience, not another ticket queue.
I help separate urgent risk from cleanup work and write down the next sensible steps.
01
Live SQL Server environments
The work is about live SQL Server environments: jobs, backups, monitoring, releases, restore checks, and operational risk.
02
Performance, recovery, upgrades, and daily operations
The usual work is not one isolated query. It is the server, the process around it, and the priority order.
03
Direct work with the person reviewing the server
You talk to the person asking the questions, checking the details, and writing the next-step list.
Typical work
The exact work changes by server, but the pattern is usually the same: find the risk, fix the order, and write down what happens next.
Blocking reviewRestore-test gapFailed SQL Agent jobsUpgrade readinessMonitoring cleanup
Before a call
Start with a short message
You do not need to send logs, exports, credentials, or sensitive system data in the first message. Describe the situation and I will tell you whether I can help.
First message
Company context, SQL Server situation, urgency, and support type.
Fit check
Monthly support, troubleshooting, or a defined review.
Next step
A call or the safe details to share next.
01
First message
Company context, SQL Server situation, urgency, and support type.
A short description is enough for the first pass. Say what you run, what is happening, and whether you want monthly support or a scoped review.
02
Fit check
I tell you whether the work matches monthly DBA support.
The work may fit monthly DBA support, troubleshooting, or a defined review. If it does not fit, I will say that plainly.
03
Next step
If it fits, we agree the next safe step.
That may be a call, a scoped review, or the safe details to share next. System access and sensitive data can wait.
Send a short message. I will tell you whether I can help.
Useful pages if you want more detail.
Use these if you want examples, technical references, product work, or background before reaching out.
Examples
Case studies and audit scope
Anonymized examples, audit checks, and sample output before you send a message.
Open page
Reference
SQL Server updates tracker
Microsoft-sourced SQL Server builds, CUs, GDRs, and support dates in one place.
Open page
Project work
Passary
A local-first password manager project. Useful if you want broader engineering context.
Open page
Profile
Whoami
Role history, enterprise background, and the non-mysterious version of who you are contacting.
Open page
Responsible for a SQL Server and want a second senior pair of eyes?
Send a short message. No access needed first.