Problems displaying this newsletter? View online.
Database Weekly
The Complete Weekly Roundup of SQL Server News by SQLServerCentral.com
Hand-picked content to sharpen your professional edge
Editorial
 

The AI Bubble and the Weak Foundation Beam

From the outside, artificial intelligence looks like limitless growth.  I see headlines online about how revenue projections will skyrocket, hardware demand is going to accelerate, and market announcements read like victory laps. But from inside the data and AI industry, the financial structure underneath American AI looks far less like a stable platform and far more like a precarious tower of cross-investments, interdependence, and capital risk layered on top of one another.  OK, so it may be my pattern-matching skills just talking here, but I know I’m not the only one, so I’ll get back to the patterns that have become so well-developed.  I use AI almost daily (it’s built into almost all applications, no matter if it is desktop, mobile, etc.) but I am always asking myself to:

  1. Justify the value of the AI feature I’m using vs. previous means
  2. Justify the financial cost to gain the AI feature
  3. Justify the amount of resources (human, financial, energy) AI cost for the feature

AI (at least American AI) today is not a free market, but a closed financial loop dominated by a small number of infrastructure owners who are simultaneously suppliers, partners, customers, and investors in each other’s success. GPU manufacturers depend on hyperscalers. Hyperscalers depend on AI vendors. AI vendors depend on enterprise buyers. Everyone depends on regulatory tolerance and cheap capital.  It’s like watching a football league where there’s only an imaginary opposing team and we’re rooting for an unforeseen championship that if done wrong could destroy our civilization, (or at least our way of living, economy and environment.)

The problem that I continue to struggle with is not innovation, but who has leverage.  The AI industry has quietly constructed a capital stack with too many mutual dependencies and too few independent cash flows. When AI profitability hiccups, the financial impact does not land in one place. It cascades across the entire championship and everyone loses and not all players are equally positioned to survive it.  This is the AI Bubble in a foundational nutshell.

The AI Financial Stack (Simplified)

At a technical and financial level, AI infrastructure breaks into four layers:

  1. Hardware: GPU vendors, chip manufacturers, energy suppliers.
  2. Cloud Infrastructure: Hyperscalers providing compute and storage.
  3. Model Builders: Companies training foundation models.
  4. Enterprise Software Vendors: Firms trying to commercialize AI into tools, platforms, and products.

There are a lot of big players, no matter if we talk about NVIDIA, AMD, Microsoft, Google, Meta, AWS, Oracle, OpenAI, Anthropic and xAI.  We also have speculators, funding AI financially, technically or by marketing, yet not really vested for the long haul, such as Palantir, JP Morgan Chase, Hugging Face, Arm, Softbank and even analytics companies like Snowflake and Databricks.  Some of the players are more leveraged than others, but also the cross-investment in many of them is highly concerning, as is the risk many of them are taking to get to the finish line as one of the first.  What makes this fragile is that money flows upward in the stack, while risk flows downward…at least that’s how it normally works.

Cloud providers buy hardware in bulk under capex-heavy models. Model builders burn cash on training. Enterprise vendors over-market AI features that generate minimal revenue relative to infrastructure expense. Yet investors value all layers as if sustainable profit exists everywhere, but it doesn’t happen here in the world of AI.  Currently, only the infrastructure layer is reliably monetized and everything above it runs at a margin deficit.

One of the biggest challenges for many to wrap their head around is the inter-investment and revenue sharing of the top companies involved in the AI Bubble, realizing the inter-dependence and risk associated.  Due to this complexity, I’m hoping it may be simpler if we look at just one, vulnerable layer and yes, this is where I’m going to get in trouble, but when has that stopped me before?

Oracle, and Why It’s Vulnerable

It may look like I’m about to pick on Oracle, but I’m not.  I love the Oracle database and Oracle tech, but Oracle is a critical case study because it represents something different than the hyperscalers: an infrastructure-adjacent enterprise software company trying to rebuild growth through AI and cloud expansion, while not actually owning the AI value chain.  It’s not the only one of those involved in the AI Bubble I could make a case from, but it is unique, I’ve observed it closely for years and I know it quite well.

Oracle’s total debt accrued in its goal of achieving AI workloads is roughly around $100-116 billion.  This total includes several recent bond issuances and borrowing around AI/cloud data center expansion.  I included its AI-related capital and borrowing, at least the material portion of its capital expenditures(CapEx) which is forecasted at $50 billion for fiscal year 2026 and is tied to its Oracle Cloud Infrastructure(OCI) build out to support AI workloads.  I also can add another $25-30 billion in bonds and a few market sources that indicated another $38 billion in new debt from financial feeds, (glad to pull up the links for anyone interested…)

Oracle’s exposure is not primarily financial or ideological, but structural.  Oracle is trying to compete in a hyperscaler world without hyperscaler economics the others could leverage.  I know many will argue that Oracle has Oracle Cloud Infrastructure (OCI) but stay with me here:

1. OCI Is Capital-Intensive Without Hyperscaler Advantages

Oracle lacks what AWS, Microsoft, and Google have: a dominant OS, a consumer ecosystem, a first-party AI platform, social data pipelines, and/or an ad-supported SaaS engine.
Because of this, OCI is pure infrastructure risk. Its revenue depends almost entirely on enterprise workloads, including databases, Exadata migrations, and Oracle applications, which is everywhere, but currently under scrutiny by most of its customers.

AI GPU clusters are expensive, short-lived assets, and Oracle is scaling them at a time when cloud budgets are tightening, multi-cloud reduces lock-in, and customers avoid long-term compute commitments.  OCI margins are slimmer than they appear: GPU purchases are up-front costs, power and  cooling rise faster than revenue, hyperscalers undercut pricing, and customers demand portability. Even with Exadata in every hyperscaler, Oracle still rents space in ecosystems it doesn't control.

2. Oracle Consumes AI; It Doesn’t Produce It

Oracle does not own a dominant foundation model like OpenAI, Copilot, or Gemini, nor does it control the AI training stack or developer ecosystems that shape pricing and influence. Oracle 23ai/26ai improves the database story, but Oracle still sells infrastructure and applications around AI, not the AI itself.  The economics are upside-down as Oracle pays the infrastructure bill, AI vendors capture the margin, customers expect AI “included,” and Oracle absorbs the compression.

Enterprise buyers already view Oracle licensing as a target for cost reduction, making this an even harder sell.

3. Oracle’s Enterprise Base Adopts AI Slowly

Oracle’s customers (which include government, finance, healthcare, insurance, and manufacturing) are risk-averse, compliance-heavy, and slow to adopt new technology. They resist exactly the models Oracle needs to monetize AI: per-call pricing, embedded AI licensing, deeper platform dependency, and vendor-controlled data flows.  This slows ROI at a time when markets expect rapid AI revenue. That mismatch creates earnings pressure and drags Oracle into regulatory and governmental scrutiny during a period when agility matters most.

Who Can Pivot More Easily in an AI Correction?

Companies with structural resilience, such as GPU vendors, hyperscalers with ad revenue, platforms with consumer lock-in, data monopolies, and defense-aligned firms can raise prices, shift investment, pass costs through, or secure government funding.  Oracle cannot raise prices without accelerating customer churn, and the market is full of alternatives. This doesn’t even touch the debt load Oracle must assume to fund its current AI and cloud timelines, but enough about poking holes in the AI Bubble at Oracle’s expense.  It’s not fair to them, as they are just part of the huge AI bubble problem, not the source of it.

Then There’s the Impending AI Bailout

So, if I haven’t convinced you why the AI Bubble is a real thing, the other is me looking into the crystal ball and seeing the future of a government bailout of AI.  If AI infrastructure collapses, governments will have to intervene because:

  • AI underpins government systems, (don’t even get me started on how dependent they are on Oracle.)
  • AI now touches healthcare infrastructure
  • AI powers national cyber operations
  • AI is treated as strategic capital, not tech optionality

Although some news will report on AI companies and projects receiving a bailout, most of it will be in smaller initiatives that will be used to save our economy, (because the few companies that are all cross-invested are over 20% of the total U.S. stock market value…) If you doubt how volatile the markets are right now, Oracle suffered a major hit just this week.

What will most likely occur if the bubble does burst is the following:

  • AI incentive bills
  • Infrastructure subsidies
  • Tariff adjustments
  • “Innovation protection policies”
  • Government cloud contracts
  • Defense modernization programs

I wanted to make sure none of my pattern matching skills were off on the big picture I was seeing, so I spent a long time researching this with and without AI to understand the weak points and opportunities in the AI bubble.  Over 90% of what I thought I was seeing, at a high and mid-level is concerning to many in the financial/tech sector and something everyone should think about as we build out the future of AI.

The most sobering thing I confirmed is who really pays for the above, and in the end, it’s we, the taxpayer.

  • Tariffs are inflation that is passed onto the consumer, which is the American taxpayer.
  • Government contract funnels reward size, not efficiency.
  • And consolidation accelerates this problem.
  • No one breaks up the monopolies, even though you’d think we’d have learned from history.
  • A few AI companies will make it big.
  • A very large group will go under, which is the norm in an economic bubble.
  • And the average taxpayer gets hollowed out paying for it all in the end.

Who Becomes the AI Cost Absorbers?

In every tech bubble, someone becomes the cost sink.

  • ISPs in the dot-com era.
  • Device manufacturers in mobile.
  • Miners in crypto.

Oracle sits closer to the cost sink than most believe and it’s not that I wish bad on any company, I just think it’s important to learn from history and make smarter decisions in the future.  There’s always those that think they can either make a big win, never minding the devastation in their wake or that they don’t need to think about how to do things the right way.  It’s always about the race to the finish for these groups and we do have an AI race well underway.

Oracle has a lot of financial capital and a lot of data gravity, but Oracle does not control the gravity of AI in this race, which makes it the weakest link.

The Bubble Reality Check

AI is not sustainable as it is today. It is subsidy-driven, capital-heavy, and dependent on public tolerance and public and private data (yes, I said private data, too.)  The cross-investment structure looks like stability if you don’t look to close, but should not be confused as such.  It is feedback risk disguised as partnership and has more in common with a house of cards someone has glued together vs. a true foundation you’d want to build a real home on.   If that glue lets go and the house gives way, the companies closest to infrastructure, without data power or distribution control will feel the impact first.  This will happen not because they failed, but because they were positioned incorrectly when the glue (gravity) shifted.

American AI won’t crash in a headline, but most likely deflate quietly through:

  • Margin erosion
  • Contract renegotiation
  • Government intervention
  • Quality/Value reduction
  • Product bundling
  • Reduced innovation

And the public will pay for it:

  • Once with a choice.
  • Continually with their money.
  • Continually with their data.

Pattern matching or opinion, this is where my editorial lead me to this week.

What are your thoughts on the AI Bubble? 

As valuable as AI is becoming and how much integration is geared to every aspect of our day-to-day life, do you worry about the AI Bubble and the financial situation created to compete? 

Do you feel it’s more about the revenue of a few vs. the benefit of all?

Peace out,

DBAKevlar

Join the debate, and respond to the editorial on the forums

 
The Weekly News
All the headlines and interesting SQL Server information that we've collected over the past week, and sometimes even a few repeats if we think they fit.
AI/Machine Learning/Cognitive Services

The Art of AI-Assisted Query Tuning: When Your SQL Needs a Little… Persuasion

From Sherpa of Data

If the last post was about using AI to argue with ...

Microsoft Reveals 7 AI Trends to Watch in 2026

From Past News - RSS Feeds

Microsoft outlines seven AI trends shaping 2026, f...

Administration of SQL Server

Troubleshooting a Distributed Availability Group Failure

From Curated SQL

Jordan Boich digs in: To give some background on t...

Page Compression on Heaps

From Curated SQL

Vlad Drumea explains why page compression might not give you quite what you expect: I recently ran into SQL Server’s page compression being applied to…

How Many Plan Variants Can You Get With The Parameter Sensitive Plan Optimization In SQL Server?

From Erik Darling Data

How Many Plan Variants Can You Get With The Parameter Sensitive Plan Optimization In SQL Server? Going Further If this is the kind of SQL Server stuff you love...

Advent of 2025, Day 10 – SQL Server 2025 – External REST endpoint invocation

From TomazTsql

In this Microsoft SQL Server 2025 series: This new functionality, you can call to the system stored procedure sp_invoke_external_rest_endpoint, and call / get: – Call REST/GraphQL endpoints from other Azure...

Data Replication and Columnstore

From Curated SQL

Niko Neugebauer continues a series on columnstore: In the Columnstore Indexes space, there is a long-standing “tradition” in Microsoft to ignore the needs of the…

Azure SQL Managed Instance

SQL Managed Instance Memory vs Cores

From Curated SQL

Kendra Little hits a pain point: Microsoft recentl...

DMO/SMO/Powershell

PowerShell String Manipulation: Swap Lines

From Sid 500 PoSh

In this article I will show you how you can swap l...

Data Access / ORMs

TouchDuck! Exploring unique features of SAS/ACCESS to DuckDB through college football

From AllAnalytics

Using college football recruiting and talent data as an example, let's see how DuckDB’s flexibility and SAS integration streamline complex transformations and queries. The post TouchDuck! Exploring unique features of...

Data Science

Using Haskell for Data Science

From Curated SQL

Jonathan Carroll has my attention: I’ve been lea...

Data Storytelling and Visualisation

Interesting Data is Usually Wrong

From Curated SQL

Mike Cisneros breaks the bad news: Tony Twyman made his name as a pioneer in the field of audience research for television and radio in…

Database Design, Theory and Development

10 Key Concepts Developers Should Know About the SQL Server model Database 

From Simple Talk

Learn how SQL Server’s model database serves as ...

DevOps and Continuous Delivery (CI/CD)

More fun with Git: git restore

From SQLServerCentral Blogs

The setup My day job involves babysitting a lot of...

Simple Workflows for Flyway and Entity Framework Code First

From Product learning – Redgate Software

Entity Framework Code First is great for development, but its abstractions can hide risky database changes until deployment. This article explores three practical EF–Flyway hybrid workflows that add visibility...

MDX/DAX

DAX UDFs is here to change things up!

From Guy in a Cube

 

Microsoft Fabric ( Azure Synapse Analytics, OneLake, ADLS, Data Science)

Tracking Historical Changes in Microsoft Fabric

From Curated SQL

Kenneth Omorodion generates a snapshot: In most mo...

OneLake Security ReadWrite Access

From Curated SQL

Kiefer Sheldon practices least privilege: Many dat...

Fabric Data Agents & Beyond - with Mathias Halkjær

From Havens Consulting

LIVESTREAM DATE/TIME ??December 12th, 9:30 AM (Pac...

Performance Tuning SQL Server

SQL Server Performance Office Hours Episode 39

From Erik Darling Data

SQL Server Performance Office Hours Episode 39 Que...

Faster Better Wronger

From Erik Darling Data

Faster Better Wronger Going Further If this is the...

PostgreSQL

Umair Shahid: PostgreSQL, MongoDB, and what “cannot scale” really means

From Planet Postgres

Last week, I read The Register’s coverage of Mon...

Robins Tharakan: 3x Faster TID Range Scans - Postgres 19

From Planet Postgres

If you've ever had to scrub significantly large ta...

Hans-Juergen Schoenig: PostgreSQL High-Availability Architectures

From Planet Postgres

PostgreSQL is highly suitable for powering critica...

UUIDv4 and UUIDv7 in PostgreSQL 18

From Curated SQL

Josef Machytka notes a change: In the past there h...

Paul Ramsey: PostGIS Performance: Simplification

From Planet Postgres

There’s nothing simple about simplification! It ...

Dave Page: Building a RAG Server with PostgreSQL - Part 2: Chunking and Embeddings

From Planet Postgres

In Part 1 of this series, we loaded our documentat...

Paul Ramsey: PostGIS Day 2025 Recap: AI, Lakehouses and Geospatial Community

From Planet Postgres

On Nov. 20, the day after GIS Day, Elizabeth Chris...

High Availability Options for Postgres

From Curated SQL

Hans-Jürgen Schönig gives us a list: This docume...

Text Search in PostgreSQL

From Curated SQL

Jay Miller is looking for strings in all the wrong...

David Wheeler: Introducing pg_clickhouse

From Planet Postgres

The ClickHouse blog has a posted a piece by yours truly introducing pg_clickhouse, a PostgreSQL extension to run ClickHouse queries from PostgreSQL: ...

PowerPivot/PowerQuery/PowerBI

Accessing Excel Files from OneDrive via Power BI

From Curated SQL

Kristyna Ferris is happy: I can’t believe it’s...

Power BI Workspace Identity Authentication

From Prologika (Teo Lachev's Weblog)

What credentials do you use to refresh your Power BI semantic models from Azure SQL SKUs, such as Azure SQL Database. Probably your credentials or a designated Entra account?...

Workspace Identity Authentication in Power BI

From Curated SQL

Teo Lachev looks at a new way of authenticating: What credentials do you use to refresh your Power BI semantic models from Azure SQL SKUs,…

Professional Development

Want to Build a Strong Team? Give Them Ownership – and Step Back

From Azure Player

Micromanagement kills teams??. It’s nothing wron...

When the Internet Stumbles: Lessons from Cloudflare & Azure Front Door Outages

From John Morehouse

Recently, the world was reminded of just how fragi...

Prepping for Certification, Part 4 of 4

From SQLServerCentral Blogs

In Parts 1-3, I covered how I prepare for a certif...

How’s the Job Market? Let’s Find Out Together.

From Brent Ozar Unlimited

Every year, I run a salary survey to help folks ha...

Erik Darling and Kendra Little Talk AI, Databases, and SQL Server 2025

From Kendra Little's Blog

Erik Darling joins me on the Dear SQL DBA Podcast ...

Be your authentic self (010)

From Dr SQL

In this conversation, I discuss the importance of sounding like yourself when writing. Authenticity in your voice will help you to connect with others. I will also discuss some...

SQL Server 2025

Regular Expression Functions in SQL Server 2025

From Curated SQL

Tomaz Kastrun continues an advent of SQL Server 2025. Day 8 looks at a pair of regular expression-related functions: Continuing with SQL Server 2025 T-SQL…

Update: SQL Server 2025’s REGEX Performance Isn’t So Bad!

From Brent Ozar Unlimited

Back in March 2025 when Microsoft first announced that REGEX support was coming to SQL Server 2025 and Azure SQL DB, I gave it a quick test, and the...

T-SQL and Query Languages

Enforcing NOT NULL in a CTAS

From Purple Frog Systems

In this blog I will show you how to use a CTAS to ...

Generating Shape-Bound Random Points in SQL Server

From Curated SQL

Sebastiao Pereira generates some numbers: Random n...

Write to the code you have (009)

From Dr SQL

In this episode of Blogging for Programmers, I want to help you avoid one of the mistakes I have tended to make myself. Writing about code I haven’t actually...

T-SQL Tuesday #193 - Notes to Self

From FLX SQL

T-SQL Tuesday is a monthly blog party hosted by a different community member each month. This month, Mike Walsh (blog) asks us: Write two short notes to yourself. One to the...

Tools for Dev (SSMS, ADS, VS, etc.)

Renaming Unsaved Tabs in SSMS 22

From Curated SQL

Greg Low shares a tip: Anyone who has worked with ...

Virtualization and Containers/Kubernetes

Securing VMware workloads in regulated industries

From Technology Review Feed - Tech Review Top Stories

At a regional hospital, a cardiac patient’s lab results sit behind layers of encryption, accessible to his surgeon but shielded from those without strictly need-to-know status. Across the street...

 
RSS FeedTwitter
This email has been sent to {email}. To be removed from this list, please click here. If you have any problems leaving the list, please contact the webmaster@sqlservercentral.com. This newsletter was sent to you because you signed up at SQLServerCentral.com. Note: This is not the SQLServerCentral.com daily newsletter list, and unsubscribing to this newsletter will not stop you receiving the SQL Server Central daily newsletters. If you want to be removed from that list, you can follow the instructions on the daily newsletter.
©2019 Redgate Software Ltd, Newnham House, Cambridge Business Park, Cambridge, CB4 0WZ, United Kingdom. All rights reserved.
webmaster@sqlservercentral.com

 

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -