97% of US database systems still run obsolete software
A Percona report highlights the security, cost and complexity pressures keeping outdated database software in service.
A new Percona report says 97% of database administrators in the United States are running obsolete software, but the finding is less about neglect than the risks and expense of changing production systems.
TechRadar reports that unsupported database management software is creating security concerns while organisations weigh the cost, complexity and operational danger of migration. Percona’s State of Open Source Database Management Report is the underlying source for the figures.
Why upgrades keep slipping
The report says database upgrades often require cross-stack migrations rather than a simple installer update. Engineering time, testing, infrastructure changes and cloud changes all add to the bill, while a poorly planned migration can create more immediate operational risk than staying on an unsupported release.
Among the barriers cited, cloud costs were the biggest concern for 31% of respondents, followed by licensing costs at 23%, tool sprawl at 17% and vendor lock-in at 12%. MySQL 5.7 users were highlighted as an example of teams facing major architectural change when moving to version 8.0.
The security trade-off
The awkward reality is that both choices carry risk. Old database software may expose valuable information to known security problems, yet rushing a migration can cause downtime, latency or compatibility failures. Percona’s respondents identified inefficiency, downtime and latency as current drawbacks at 42%, 40% and 35% respectively.
The practical answer is planning: map dependencies, test migrations and work out the total cost before unsupported software becomes an emergency. The report does not suggest that every organisation can upgrade overnight, only that postponement is not a strategy.
Our opinion
The 97% figure is alarming, but the explanation is more useful than the shock value. Database infrastructure is buried beneath applications, subscriptions and business processes, so “just upgrade” is rarely serious advice. The better lesson is to treat migration as a long-running engineering programme, with security and rollback plans in place before the deadline arrives.