U.S. Relational Databases Software Market

Oracle said its multicloud database revenue from Amazon, Google and Microsoft grew 1,529% in the quarter to August 2025, in its results of 9 September 2025, and still grew 531% in the quarter to February 2026, its filing of 10 March 2026 shows; American companies are keeping their Oracle databases and moving them into the hyperscaler contracts they already sign. The U.S. relational databases software market covers what American organisations pay for relational database engines: cloud managed relational database services, commercial on-premise licences and support, open source subscriptions and support, and distributed SQL and serverless databases. Douglas Insights sizes it at USD 35.8 billion in 2025, from about 710,000 paying organisations at an average annual spend of USD 50,400, and at USD 93.2 billion in 2035, a revenue CAGR (compound annual growth rate) of 10.04%. The United States is 88.0% of North America in our global Relational Databases Software Market report, the study sits in our enterprise software coverage, and every figure follows the Douglas Insights research methodology.

Which U.S. database deployment model carries the spend: managed cloud services, licences or distributed SQL?

Cloud managed relational database services carry the most U.S. relational databases software spend, 55.0% of 2025, USD 19.7 billion, because new American applications launch on RDS, Aurora and Azure SQL. Distributed SQL and serverless grow fastest, 16.4% a year.

Managed cloud services lead at USD 19.7 billion, a larger share than the 52% worldwide, because U.S. enterprises moved earlier to Amazon Web Services, Microsoft Azure and Google Cloud and because American startups rarely run a database server of their own. The segment grows 12.4% a year to USD 63.3 billion and supplies 76.1% of the value the U.S. relational databases software market adds by 2035, as storage, replicas and premium features run on the meter. Commercial on-premise licences and support, USD 10.7 billion, are the Oracle Database, SQL Server, Db2 and SAP HANA estates in bank, insurer, hospital and federal data centres. They grow only 1.40% a year, kept alive by support fees and by new releases such as SQL Server 2025, which Microsoft made generally available at Ignite in November 2025.

Open source subscriptions and support, USD 2.86 billion, cover enterprise PostgreSQL and MySQL distributions, support and tooling from EDB, Percona, Crunchy Data and Oracle’s MySQL Enterprise; they grow 7.40% a year as open source engines replace licences. Distributed SQL and serverless databases, USD 2.50 billion, include Google Spanner, CockroachDB, YugabyteDB and Aurora DSQL, which AWS made generally available on 27 May 2025; they grow fastest, 16.4% a year, because AI agents and multi-region applications want databases that scale without sizing. Deployment values for 2035 sum to USD 93.0 billion, 0.23% below the headline; the paid support around self-run open source is sized in our Open Source Services Market report.

Why does U.S. relational database spend per organisation rise 7.15% a year?

U.S. relational database spend per organisation rises 7.15% a year, from USD 50,400 in 2025 to about USD 100,500 in 2035, because data growth, migration, resilience and AI workloads add 9.00 points before cost controls take 1.85 points.

The meter replaces the licence. American organisations once paid per processor core plus yearly support; on managed services they pay for compute, storage, input and output, backups and replicas as they use them, so spend tracks data rather than procurement. Paying organisations grow 2.70% a year, from about 710,000 to 927,000, as startups and mid-sized firms buy managed databases instead of hiring administrators.

Data growth in transactional systems: 5.00 points

Data growth adds 5.00 points. Card payments, e-commerce orders, claims and connected devices add rows faster than American firms archive them, and managed services bill for every gigabyte and replica, a Douglas Insights estimate.

Migration and multicloud: 2.00 points

Migration adds 2.00 points. Oracle’s Cloud Database infrastructure revenue rose 35% in the quarter to February 2026, its March 2026 release shows, as Oracle Database@AWS, @Azure and @Google Cloud let U.S. banks move estates without rewriting them.

Resilience and AI agents: 2.00 points

Multi-region resilience adds 0.80 points and AI 1.20 points. Databricks said more than 80% of the databases on Neon, the serverless PostgreSQL company it agreed to buy on 14 May 2025, were created by AI agents. The four contributions, 5.00 + 2.00 + 0.80 + 1.20, give 9.00 points.

What holds back U.S. database spend: savings plans, PostgreSQL substitution or migration risk?

Three restraints remove 1.85 points from U.S. relational database spend per organisation growth, leaving 7.15% a year. Cost optimisation takes 1.20 points, PostgreSQL substitution of licences 0.45 points and migration risk 0.20 points.

Cost optimisation is the largest brake. AWS launched Database Savings Plans on 2 December 2025, offering up to 35% off Aurora, RDS and other database services for a one-year hourly spend commitment with no upfront payment; FinOps teams at American firms use such commitments, rightsizing and idle-database shutdowns to cap bills. Douglas Insights removes 1.20 points.

PostgreSQL substitution removes 0.45 points: each workload moved from a commercial licence to an open source engine cuts licence and support revenue even as managed service revenue grows. Migration risk removes 0.20 points, because a large Oracle or Db2 system with thousands of stored procedures can take one to three years to move; the outside work is sized in our Mainframe Modernization Services Market report.

Where in the United States is relational database spend concentrated, and why do Texas and Virginia grow fastest?

California holds the most U.S. relational databases software spend, USD 6.08 billion or 17.0% of 2025, Douglas Insights estimates. Texas grows fastest, 11.4% a year to USD 9.48 billion by 2035, with Virginia at 11.0%.

California leads because Silicon Valley and Los Angeles host the largest concentration of software companies, platforms and startups, the heaviest users of managed and serverless databases; it grows 10.4% a year. Texas, USD 3.22 billion, grows fastest as Dallas and Austin add bank, insurer, airline and energy headquarters and Oracle runs its corporate base in Austin. New York, USD 3.22 billion, grows 9.20% a year on banks, brokers and insurers whose Oracle and SQL Server estates move slowly under regulator scrutiny.

Washington, USD 2.15 billion, carries the home teams of Amazon and Microsoft and Seattle’s software firms. Virginia, USD 1.79 billion, grows 11.0% a year because federal agencies and contractors around Northern Virginia are moving systems to FedRAMP-authorised database services. The rest of the South, USD 6.80 billion, includes Georgia, Florida and North Carolina banks and retailers; the Midwest, USD 5.37 billion, and the rest of the Northeast grow 9.00% a year on manufacturers, insurers and hospitals with older estates. State values for 2035 sum to USD 93.5 billion, 0.33% above the headline; in the data table the row labelled Global holds the U.S. total, USD 35.8 billion in 2025.

Who sells relational databases to American organisations: AWS, Microsoft, Oracle, Google or IBM?

Amazon Web Services takes the most U.S. relational databases software spend, about 24.0% of 2025, USD 8.59 billion, Douglas Insights estimates. Microsoft, Oracle and AWS together hold about 61.0%, with Google Cloud fourth.

The shares are Douglas Insights estimates because no vendor reports U.S. relational database revenue. AWS leads managed databases; Microsoft wins where SQL Server and Microsoft 365 contracts already sit; Oracle keeps the most valuable systems of record and now sells them through rivals’ clouds. Data platforms are moving in: Snowflake agreed to buy Crunchy Data, a PostgreSQL provider with a record in FedRAMP environments, on 2 June 2025, three weeks after Databricks agreed to buy Neon. Oracle and Microsoft defend differently. Oracle lets American customers keep its engine while paying through AWS, Azure or Google Cloud commitments, so its database revenue follows the hyperscaler meter; Microsoft bundles SQL Server rights into Azure Hybrid Benefit so licences already owned lower the cost of moving. IBM’s Db2 holds on mainframes at the largest banks, insurers and federal agencies, and SAP HANA rises and falls with S/4HANA migrations, which many U.S. manufacturers are scheduling before SAP’s 2027 end of mainstream maintenance for older ERP releases. Specialists win where a single feature matters: CockroachDB and YugabyteDB for always-on multi-region ledgers, EDB for Oracle-compatible PostgreSQL. Fleets of this size need monitoring of the kind sized in our Enterprise Data Observability Platforms Market report.

What does a relational database cost a U.S. organisation, per core, per hour or per request?

A U.S. organisation spent an average USD 50,400 on relational database software in 2025, Douglas Insights estimates, from under USD 50 a month for a small managed instance to tens of millions a year for a bank’s Oracle estate.

Labour sets the ceiling. The Bureau of Labor Statistics (BLS) counts about 144,500 database administrators and architects with a median pay of USD 126,760 in 2025, and projects administrator jobs to grow 0% to 2035 against 9% for architects, in its Occupational Outlook Handbook. The average USD 50,400 database bill is about 40% of one median salary, which is why small American firms buy managed services rather than hire. Backup copies kept outside the database are sized in our Online Cloud Backup Service Market report.

Which U.S. rules shape database choices: CMMC, FedRAMP or the 2026 state privacy laws?

Three rule sets shape U.S. relational database choices: the Pentagon’s CMMC rule in force since 10 November 2025, FedRAMP authorisation for federal cloud services, and state privacy laws in Indiana, Kentucky and Rhode Island from 1 January 2026.

The Department of Defense issued the Cybersecurity Maturity Model Certification (CMMC) contract rule on 10 September 2025, effective 10 November 2025, with phase 2 starting on 10 November 2026 and full implementation by November 2027, Squire Patton Boggs explained. Defence contractors that store controlled unclassified information in databases must show certified controls, which pushes them to government-region managed services or hardened on-premise estates. Federal agencies buy cloud databases only with FedRAMP authorisation, which is why Snowflake cited Crunchy Data’s FedRAMP record.

State privacy laws add retention and deletion duties. Indiana, Kentucky and Rhode Island comprehensive privacy laws took effect on 1 January 2026, Koley Jessen noted, so firms must find and delete personal data across every database. Legal holds on database records are sized in our Cloud-Based E-Discovery Software Market report.

What if cost discipline wins or AI agents multiply databases: where does U.S. relational database spend land in 2035?

The U.S. relational databases software market ends 2035 between USD 69.6 billion and USD 116 billion across our three cases, around a base of USD 93.2 billion. AI-agent database creation and savings-plan discipline set the spread.

In the cost-discipline case American firms lock most usage into savings plans, move licences to self-run PostgreSQL and slow multi-region builds. In the data-surge case AI agents create databases by the million on Neon, Aurora DSQL and Snowflake Postgres, and Oracle multicloud keeps growing at triple-digit rates. One extra point of yearly organisation growth adds USD 9.48 billion to 2035 U.S. relational databases software value; one point less removes USD 8.69 billion.

Our 10.04% sits just below the 10.08% North America rate and the 11.06% global rate in the Douglas Insights global model, because the United States moved to managed services first and Asia Pacific, at 12.8%, is still migrating.

Douglas Exclusive: the U.S. Database Meter Ledger

The U.S. Database Meter Ledger is a Douglas Insights model built from 13 sourced inputs in 10 company, government and legal releases dated May 2025 to March 2026, tracking how U.S. database spend moves from licences to meters.

The finding, a Douglas Insights estimate: the 35% savings-plan discount and the 0% outlook for administrator jobs point the same way. American organisations are paying less per unit of database work and employing fewer people to run it, but buying far more units. Our model has PostgreSQL-compatible engines rising from about 24% of U.S. relational spend in 2025 to 41% by 2035, while Oracle’s multicloud growth keeps commercial engines inside the meter rather than outside it; that is why the commercial licence segment still grows 1.40% a year rather than shrinking, and why managed services reach 68.0% of 2035 value.

How does the methodology turn 710,000 paying organisations into USD 35.8 billion?

Our methodology multiplies about 710,000 U.S. organisations paying for relational database software in 2025 by an average annual spend of USD 50,400 to reach USD 35.8 billion. Counts come from firm-size bands; spend from four deployment models.

The model covers 9 states or regions, 4 deployment models and 3 buyer sizes, and uses 84 data points, 22 sourced and 62 modelled. Arithmetic: 710,000 x USD 50,400 = USD 35,784 million; 35,784 x (1.0270 x 1.0715)^10 = USD 93,178 million, or USD 93.2 billion. Paying organisations reach about 729,000 in 2026 and 927,000 in 2035; spend per organisation reaches USD 54,000 in 2026.

Two cross-checks agree. First, USD 35.8 billion is 88.0% of the USD 40,664 million North America row of our global relational databases software model, in line with the U.S. share of North American GDP and cloud spend. Second, the 61.0% top-three share sits close to the about 60% global share in that model. AI tools help draft the text and automated checks test the arithmetic and links; the Douglas Insights research desk chooses the sources, builds the model and approves publication, as our editorial standards explain.

Sources

1. Oracle Oracle Announces Fiscal Year 2026 First Quarter Financial Results (2025)
2. Oracle / SEC EDGAR Oracle fiscal 2026 third quarter results, Form 8-K exhibit 99.1 (2026)
3. Amazon Web Services Amazon Aurora DSQL is now generally available (2025)
4. Amazon Web Services Announcing Database Savings Plans with up to 35% savings (2025)
5. Databricks Databricks agrees to acquire Neon (2025)
6. Snowflake Snowflake acquires Crunchy Data (2025)
7. Microsoft SQL Server 2025 generally available (2025)
8. U.S. Bureau of Labor Statistics Database Administrators and Architects, Occupational Outlook Handbook (2026)
9. Squire Patton Boggs The CMMC DFARS final rule goes live (2025)
10. Koley Jessen New state privacy laws effective January 1, 2026: Indiana, Kentucky and Rhode Island (2026)

What counts in the U.S. relational databases software market, and what is excluded?

The U.S. relational databases software market counts what American organisations pay for relational engines, licences, support, subscriptions and managed relational database services. NoSQL databases, standalone data warehouses, separately sold tooling and IT services are excluded.

The by-deployment split covers the four models above; the by-buyer split covers large enterprises, mid-sized organisations, and small organisations and startups; the by-state split covers California, Texas, New York, Washington, Virginia, the rest of the West, the rest of the South, the rest of the Northeast and the Midwest. Spend is counted where the buying organisation is based, not where the data centre runs.