Vast Majority of U.S. Database Admins Still Use Outdated Software

Key Insights from ZDNET

A significant percentage of organizations are operating on outdated database systems.
High costs deter companies from upgrading their database management systems.
Using unsupported software can lead to serious security vulnerabilities.

Many users continue to rely on outdated software, often due to inertia, cost barriers, or simply because it meets their current needs without requiring a change. However, a recent report from Percona, a provider of support for open-source database management systems (DBMS), highlighted that a staggering 97% of database administrators (DBAs) in the United States are still running obsolete DBMS programs, raising concerns about the implications for businesses that rely on these critical systems.

Reasons for the Continued Use of Outdated DBMSs

Percona’s report indicates that one of the primary reasons for the continued use of legacy DBMSs is that upgrading to newer versions involves complex, high-risk migration projects rather than straightforward software updates. Factors such as dependencies on legacy applications, deprecated features, client compatibility, altered defaults, testing requirements, and the need to minimize disruptions to production environments often lead organizations to postpone necessary upgrades, opting for a “better safe than sorry” approach.

Moreover, organizations face significant challenges in maintaining security while relying on end-of-life software. The rapid advancement of AI technologies, which can identify security vulnerabilities more swiftly than organizations can address them, compounds this issue.

Additionally, upgrading databases is rarely as simple as switching versions; it often exposes dependencies throughout the application stack. Legacy applications may depend on features that have been deprecated or removed, necessitating teams to identify and address these dependencies. For instance, MySQL 8.0’s new default authentication method, caching_sha2_password, can create difficulties for older clients and may require specific configuration adjustments.

Organizations must also conduct thorough reviews of their application environments, including operating systems, libraries, and configuration files, since database migrations can impact far more than just the database server.

This added complexity results in higher costs and risks associated with moving to supported releases. Teams are required to perform pre-upgrade checks, validate migrations in staging environments, and carefully schedule production work to minimize disruptions—tasks that demand specialized skills, engineering time, and planned maintenance periods.

Transitioning between major software releases can introduce additional challenges. The upgrade from MySQL 5.7 to 8.0, for example, involved a significant redesign of the data dictionary and the removal of the query cache, illustrating why a simple “just upgrade” approach is often insufficient.

Financial Implications

The survey conducted by Percona underscored that financial constraints remain the most frequently cited barrier to reducing the total cost of ownership and upgrading database systems.

Notably, cloud consumption costs (31%) ranked higher than licensing fees (23%) as the primary reported obstacles. This distinction is crucial since migrating to managed database platforms can reduce operational burdens but may also lead to unpredictable expenses as storage, computing, network traffic, high availability, and data transfer needs fluctuate.

Percona CEO Peter Farkas emphasized that “cloud economics are evolving, AI is introducing new workload patterns, regulations are becoming increasingly complex, and organizations are more aware of where their data and technology are managed.” He noted that organizations best positioned for the future will be those that retain the ability to adapt rather than those trying to predict future developments.

Challenges in Performance and Governance

The report frames database operations as issues of engineering efficiency and resilience rather than merely concerns around query latency:

42% of respondents identified inefficiency or slow throughput as a performance challenge.
41% reported wasted engineering time.
40% indicated downtime as a significant issue.
37% faced challenges with scaling their operations.

Regarding governance, 54% of participants expressed that vendor lock-in complicates their ability to adapt to changing regulatory demands. Many respondents noted fragmented tools or policies, while 46% raised concerns about software supply-chain traceability and a reactive security posture.

The findings connect issues related to legacy software to broader management challenges. Unsupported software complicates vulnerability management and compliance auditing, while fragmented controls and database sprawl make consistent planning for upgrades and migrations significantly more difficult.

AI Readiness and Organizational Barriers

Respondents indicated that the primary obstacles to AI readiness were foundational organizational challenges rather than a lack of database features. Both fragmented data architecture and skills shortages were identified as the top barriers, each accounting for 23% of responses.

This insight serves as a counterpoint to the current trend of adding advanced features like vector search capabilities and agent-oriented functionalities to DBMS offerings. While these enhancements can be beneficial, respondents from Percona indicate that disconnected data environments and insufficient staff expertise pose more immediate roadblocks.

Farkas concluded by stating that “database leaders must prepare for change, not just a singular future version.” He emphasized that control and flexibility should be integral requirements rather than afterthoughts. As the AI revolution’s direction remains uncertain, organizations that leverage the flexibility of open-source DBMS solutions are likely to be the most strategically positioned.