AI Can Write Your Data Platform. Who’s Going to Keep It Running?
AI can write SQL, generate pipelines, build infrastructure, create database migrations, and even diagnose production problems. But what happens when it confidently does the wrong thing? As AI becomes part of how we build and operate modern data platforms, the key question is no longer just, “Can AI generate this?” It’s whether we can trust the result, deploy it safely, observe what happens, and recover when things go wrong. Join Hamish Watson for a practical session on bringing AI-assisted development into production reality. Drawing on experience across SQL Server, cloud platforms, Databricks, and database DevOps, Hamish will explore how version control, CI/CD, automated testing, drift detection, observability, and governance help keep AI-generated changes safe and recoverable. The session will include practical examples, lessons learned, and a live demo. And, because live demos rarely go exactly to plan, there may even be a surprise or two. AI might be able to write your data platform. The more important question is: who’s going to keep it running? Register for the sessionWhy Enterprises Still Need an Ontology
Some VP, in a meeting near you, is asking: "We already have a data warehouse, a semantic layer, and a knowledge graph. Do we really need an ontology?" This 30-minute, demo-heavy talk answers yes — and shows it under a closed-loop LLM constraint that prevents hand-waving. We walk the four-layer enterprise data stack : Lakehouse, Semantic Layer, Knowledge Graph, Ontology, and run one live LLM demo per layer against a small, fully readable fictional dataset (NorthWind Outdoor: ~9 customers, ~21 orders). Each demo poses one question that the layer in question cannot answer cleanly, and the audience watches the next layer turn out to be exactly what removes the gap: 1. Lakehouse + revenue. The LLM lands on the right number, but only by stacking three labeled guesses (what column is money, what "revenue" is, whether to include returns). Motivates the semantic layer. 2. Semantic + co-purchase. The LLM hand-rolls a multi-CTE self-join. Works, but the LLM is the query author. Motivates the knowledge graph. 3. KG + churn risk. Every fact is on every node, but no class for ChurnRiskCustomer. The LLM invents a rule or declines. Motivates the ontology. 4. Ontology + VIP promo email. The LLM cites nw:VIPCustomer, nw:RestrictedMarketingRegion, and a SHACL Forbid rule by name; returns an auditable answer with citations and exemptions explained. You leave with a portable narrative you can run against your own data, a 4-cell rubric for evaluating whether your ontology layer is earning its keep, and a defensible 30-day starter plan. Git Hub repository Containing Code samples and the deck. Recording
About Data Under Pressure User Group
Open Group
Members
mzachariasOwnerJoined September 25, 2026
catudOwnerJoined September 25, 2026
Events
- Oct13
AI Can Write Your Data Platform. Who’s Going to Keep It Running?
AI can write SQL, generate pipelines, build infrastructure, create database migrations, and even diagnose production problems. But what happens when it confidently does the wrong thing? As AI bec...Tuesday, Oct 13, 2026, 04:45 PM PDTOnline2Views0likes1Attendee0Comments