Database Administrator Staffing for Estates With a Support Date
SQL Server, PostgreSQL, MySQL and Oracle DBAs who have already run the upgrade you’re about to schedule.
Database administrator staffing places vetted DBAs on contract, contract-to-hire or direct hire for SQL Server, PostgreSQL, MySQL, Oracle and cloud-managed databases, and KORE1 averages 17 days to hire while keeping 92% of its placements beyond their first year.
Last updated: September 14, 2026
DBA searches used to start with a resignation. This year a lot of them start with a date on a vendor’s lifecycle page instead. SQL Server 2016 lost extended support on July 14, 2026. MySQL 8.0 reached end of life in April. PostgreSQL 14 gets its final community release on November 12.
The date isn’t the hard part. Nobody left on the team has made the jump. The person who installed that SQL Server instance in 2017 moved on years ago, the Postgres cluster arrived with an acquisition and still runs on defaults, and the MySQL box sits under a billing app nobody touches on a weekday. Three engines, one posting that says DBA.
We staff that seat and we’re blunt about its size. KORE1 has been placing technology people since 2005, and the IT staffing services desk behind this page will sometimes tell you the honest call is a contract DBA for one upgrade window, not a permanent hire. Sometimes it’s both, in that order. Coverage engine by engine sits with our database administration staffing team, Oracle-heavy estates get their own Oracle DBA staffing desk, and PL/SQL work that lives inside the database goes to Oracle developer staffing.
Where Each Engine Version Stands Today
Six engine versions that still turn up in mid-market production, ordered by the day their standard support ends. Day counts run from September 14, 2026, and every date comes from the vendor.
SELECT engine, support_ends, days_from_today, status, staying_costs FROM estate ORDER BY support_ends;
| engine | support_ends | days_from_today | status | staying_costs | |
|---|---|---|---|---|---|
| 1 | PostgreSQL 13 | 2025-11-13 | −305 | Extended, paid | No community fixes. On Amazon RDS, Extended Support bills $0.075 per vCPU-hour, then $0.150 from March 1, 2028. |
| 2 | SQL Server 2016 | 2026-07-14 | −62 | Extended, paid | Extended Security Updates, bought a year at a time. The third and last year ends July 17, 2029. |
| 3 | PostgreSQL 14 | 2026-11-12 | 59 | In support | Final community release. RDS standard support runs to February 28, 2027, then Extended Support billing starts. |
| 4 | SQL Server 2017 | 2027-10-12 | 393 | In support | Extended support ends. Plan the jump to SQL Server 2022 or later while it’s still a project. |
| 5 | PostgreSQL 15 | 2027-11-11 | 423 | In support | The five-year community window closes. RDS standard support runs to February 29, 2028. |
| 6 | Oracle Database 19c | 2029-12-31 | 1,204 | In support | Premier Support ends. Extended Support runs to December 31, 2032. |
Read the negative numbers first. Each one is a database somebody is paying extra to keep, or running without patches and hoping. SQL Server 2016 updates now come a year at a time, so that invoice returns every July until 2029, and a 16-vCPU PostgreSQL 13 instance on RDS runs roughly $10,500 a year in Extended Support alone before the rate doubles.
Then look at the 59. PostgreSQL 14 is still inside the stretch where an upgrade is a project rather than an incident, and that’s exactly when a contract DBA who has run pg_upgrade against a production cluster is worth the most. After November it turns into a patching problem with a deadline attached. Different job. Worse timing. And if the plan is to leave the server behind for RDS or Azure SQL instead of upgrading in place, that’s a scoped cloud migration team with a DBA seat inside it.
One Req, Several Engines
Open the last DBA job description your team wrote. It probably names one engine, lists five more as nice to have, and asks for on-call. Mid-market estates rarely run a single engine now, and a DBA who’s excellent on one is often ordinary on the next. Postings never say so.
Postgres is most of the reason. It topped the database rankings when Stack Overflow surveyed developers in 2025, which says a lot about how the cluster usually got into the building. A product team stood it up. IT inherited it.
- SQL Server. Always On availability groups, the 2016 or 2017 instance under the ERP, and the licensing conversation that rides along with every version jump.
- Postgres wants a different instinct entirely, autovacuum and bloat and connection pooling through PgBouncer, plus logical replication when the business won’t sit through a long outage.
- A managed service somewhere? Amazon RDS, Aurora or Azure SQL Managed Instance take patching off your plate and hand back parameter groups, maintenance windows you didn’t choose, and a bill.
- Sometimes MySQL 8.0, past its April 2026 end of life and still quietly underneath a line-of-business app.
So we write the req around the estate instead of the title. Which engine carries the revenue, which one carries the risk, and which one can honestly wait a year. The answer is usually two. One strong primary engine, plus a second the person has operated in production rather than installed on a laptop. Our DBA job description template is built the same way.
The DBA Seats We Fill Most
Four profiles cover most of the database searches on our desk. They overlap less than the titles suggest.
SQL Server Production DBA
Owns availability groups, backups and patch nights for the instances your ERP and reporting lean on.
PostgreSQL DBA
Tunes autovacuum, clears bloat, and plans major-version upgrades through pg_upgrade or logical replication.
Cloud Database Administrator
Runs RDS, Aurora or Azure SQL, including maintenance windows, parameter groups and the Extended Support line.
Upgrade and Migration DBA
A contract seat with an end date, a tested rollback plan, and zero interest in your pager afterward.
People who write T-SQL and stored procedures rather than run the server sit with our SQL developer staffing desk. Schema and platform design go to data architect staffing, pipelines to data engineer staffing, and the infrastructure under a managed database to our cloud engineer team. Warehouse modeling on Snowflake or Redshift is a different seat again, covered by data warehouse engineer staffing.
Ask Who Wrote the Rollback Plan
Every DBA résumé mentions upgrades. The question that sorts them is short. On the last major-version upgrade you ran, who wrote the rollback plan, and did anybody ever test it?
People who carried one answer with a timeline. They restored a full backup to a copy first and timed pg_upgrade in link mode against it, or they built a logical replica on the new version and cut over in ten minutes because the business refused them four hours. SQL Server people talk about the compatibility level they held back for a week, and the one query that went sideways the morning they raised it.
Candidates who only watched somebody else do it recite the vendor’s steps. Not a red flag by itself. It’s a junior flag, and junior matters when the window opens at one on a Saturday morning.
We have that conversation before you meet anyone, plus a second about the last replication lag or blocking chain that woke them up. Those two questions do more for our 92% twelve-month retention than any keyword filter. The rest of what we ask is in our DBA interview questions, if you’d rather run the screen yourself.
DBA Pay by Level, With Contract Rates
U.S. database administrators averaged $110,090 a year and database architects $144,440 in the May 2025 occupational wage estimates from the Bureau of Labor Statistics. Those are means across every industry and every level. Means hide a lot. A production DBA who carries the pager lands higher.
| Seat | Pay | What moves it |
|---|---|---|
| Mid-level DBA, 3 to 5 years | $90,000 to $115,000 base | One primary engine, some cloud exposure |
| Senior DBA, 5 to 8 years | $120,000 to $145,000 base | High availability design, recovery ownership, a second engine |
| Lead or principal DBA | $135,000 to $175,000 base | Team lead, vendor and license decisions |
| Contract DBA, W-2 | $65 to $110 an hour | Engine, scope, and how unforgiving the window is |
Specialists sit above those bands. Cloud DBAs and Oracle RAC people land closest to the top (the Oracle DBA salary guide covers that slice on its own), and our database administrator salary guide breaks the numbers out by engine and metro. Remote searches tend to pay more than people expect, mostly because the companies willing to hire a DBA they may never meet in person are usually the ones with the messiest estates and the least patience for a learning curve.
Contract Through the Cutover, Then Decide
An upgrade has an end date. An estate doesn’t. Fold both into one permanent hire and what usually arrives is a senior DBA who’s restless by month nine, once the interesting part is over.
- ContractOne window or one migration, three to nine months on a KORE1 W-2. Fits the SQL Server 2016 jump or a Postgres major upgrade.
- Contract-to-hireThe upgrade doubles as a working interview, and if the estate still needs them afterward they convert.
- Direct hireEnough instances and enough on-call that the seat stays full time for years, with one name on the pager.
Usually it’s a sequence, not a choice. Contract through the upgrade, then decide with real evidence. Weighing more than one agency before you start? Our ranking of U.S. tech recruiting firms is a fair place to begin that comparison.
Common Questions
What does a database administrator cost to hire in 2026?
$90,000 to $145,000 covers most mid-level and senior direct-hire DBA salaries in 2026, with leads reaching about $175,000. Contract DBAs on a W-2 run $65 to $110 an hour. Cloud and Oracle specialists land at the upper end of both, and so does anyone expected to carry the pager.
Is a DBA still necessary once our databases run on Amazon RDS or Azure SQL?
Yes, though the job narrows, because managed services take over patching, backups and hardware but leave query performance, schema changes, major-version upgrades, cost and security with your team. The role shrinks. It doesn’t vanish. Somebody still has to move PostgreSQL 14 before RDS Extended Support billing starts on March 1, 2027. For a small estate that can be a part-time contract seat.
How fast can a staffing agency place a DBA?
Seventeen days is the average across KORE1’s IT desks, and contract DBA searches often close sooner. Direct hire runs longer, mostly because of interview loops on the client side. The slowest searches we see are the ones where nobody internal can run the technical screen. That part is fixable.
What should we do now that SQL Server 2016 support has ended?
Pick a path and put a date on it, whether that’s a year of Extended Security Updates, an in-place upgrade to SQL Server 2022 or later, or a move to Azure SQL Managed Instance. Updates buy time, not a plan, and the third and final year ends July 17, 2029. The upgrade itself makes a good contract engagement because it’s intense, it ends, and the rollback plan matters more than the install.
Is a contract DBA or a full-time DBA the better fit?
Honestly, contract when the job finishes on a known day, such as an upgrade or a migration, and full-time when the estate needs a named person on call for years. Plenty of teams do both in order. A contract DBA runs the upgrade, and by the end everyone knows whether the seat is real. If it is, contract-to-hire converts them without a second search.
Can one DBA handle both SQL Server and PostgreSQL?
Some can, though most DBAs are strong on one engine and merely serviceable on the other, so we hire for the engine that carries the revenue and check real production time on the second. The instincts differ. SQL Server people think in availability groups and wait stats, while Postgres people think in vacuum, bloat and connection counts.
What does a DBA staffing agency actually screen for?
Production evidence, meaning a real upgrade, a real restore and a real outage the candidate handled, rather than a list of platforms or certifications. We ask who wrote the rollback plan on their last major-version upgrade and whether anyone tested it. Then we ask about the last replication lag or blocking chain that paged them at night. Certifications are a reasonable floor. They don’t predict who stays calm at 1 a.m.
Start With the Version That Worries You
Tell us which engines you run and which one worries you most. We’ll say whether it’s a contract window, a permanent seat, or both, and send DBAs who have already made that exact jump.
Book a DBA Intake Call →