SQL Server 2026: BAGI Edition (#TSQL2SDAY 100!)
It’s T-SQL Tuesday’s 8 year birthday (or close enough), and Adam Machanic has challenged us with the question: what will the world be like when T-SQLTuesday turns 16?
Not familiar with T-SQL Tuesday? It’s a monthly event where you’re invited to join in blogging on a given topic. Invitations are posted centrally here, and here’s how to set up emails if you’d like the invitation in your inbox.
In 2026, SQL Server will still exist, but times will have changed
Individual servers, virtual machines, instances, databases – many of us will still know those concepts well and fondly. But most new applications will be written for and deployed on BAGIs.
The Big BAGI: Big Awesome Giant Infrastructure
Big BAGIs will be giant compute clusters, run by a variety of providers. These compute clusters won’t have any tape storage, no spinning disks, not even any SSDs as we know them today. Instead, they’ll be loaded with vast amounts of specialized memory, which achieves high availability by super fast networking between compute clusters in different datacenters.
Little BAGI’s live on the Big BAGI
Data will be stored not in databases, but in little BAGI’s: Bundles of All Generated Information.
Your BAGI may contain relational data, document data, graph data, or many more different types of data. Your applications will be able to access BAGIs of different types, and manipulate and process that data using Daemons — one of which is the SQL Server Daemon, whose binaries live on the Big BAGI. Different Big BAGI Daemons will have specialized optimization techniques and abilities to scale.
When you create a little BAGI, it will always live on one more more Big BAGI, and your writes to your BAGI are always written to both, with automatic conflict resolution.
How is the conflict resolution determined? You configure your BAGIs in groups, and each group of BAGIs has a data steward. On a contractual basis of your choosing, Cordelia (Cortana’s descendant), checks in with the data steward with a Q&A session on data retention, conflict resolution, and BAGI security, and cost management.
What’s the licensing like?
You have options. You can either pay by the gram — literally, the weight that the data takes up in memory, multiplied by a fluctuating currency charge — or if you want lower-latency data access, you can pay higher rates for bigger individual BAGIs, many BAGIs guaranteed to be in close proximity of one another, or a certain level of global redundancy of your BAGIs, having your BAGIs hosted on a minimum number of providers, etc.
My data is in a BAGI and it’s sold by the gram?
Yes, data will have truly become our favorite cultural drug.