August 2026 Summaries

Following SAP’s acquisition of Dremio, the piece advises customers to continue using existing deployments while assessing longer-term effects on product roadmaps, cross-platform connectivity, portability, governance, and AI workloads. It recommends asking whether promised features will remain funded, whether the platform can maintain native access to data outside the SAP ecosystem, whether table formats and catalogs preserve the ability to move workloads, and whether security policies, definitions, and audit trails apply consistently across all queried sources. It also emphasizes that AI agents need current, governed access to data across databases, warehouses, SaaS applications, and lakes to avoid producing confident conclusions from incomplete information. Rather than urging a full replacement of Dremio or rejecting SAP integration, the piece advocates selectively moving data when necessary and using a data-federation approach to provide access to distributed data while preserving existing investments and vendor flexibility.

Data virtualization creates a logical access layer that enables users to query and combine data across databases, warehouses, lakes, lakehouses, SaaS applications, and cloud environments without first relocating it, extending data federation with semantic abstraction, centralized governance, and security controls. It supports “read in place” analytics, real-time reporting, AI exploration, and data mesh or fabric architectures by making distributed sources appear more unified, while hybrid strategies can materialize high-value datasets into formats such as Iceberg or Delta Lake for demanding workloads. Its effectiveness is constrained by cross-source performance, network latency and egress costs, SQL and API differences, rate limits, inconsistent security models, limited cross-system transaction guarantees, and difficulties in monitoring and recovering distributed workflows. The recommended approach is incremental adoption, beginning with manageable ad hoc analytics use cases, then combining federation, caching, materialized views, governance integration, and observability based on workload needs rather than treating virtualization as a replacement for all data movement or ETL.

As enterprises shift from analyst-mediated business intelligence to AI agents and large language models that query data directly, the central challenge becomes preserving the institutional context analysts once supplied, such as approved metric definitions, reliable sources, business rules, and domain-specific interpretations. The proposed enterprise context layer is a governed functional tier between agents and data that provides structured metrics and logic, semantic relationships across disparate systems, and traceability and access controls for auditable answers. Unlike broad data catalogs that can expose agents to obsolete, temporary, or conflicting assets, it selectively presents steward-certified “gold” data products and metadata harvested from tools such as dbt, Tableau, catalogs, and query histories. Treating data products as code through version-controlled YAML definitions and CI/CD workflows can keep context aligned with changing data pipelines across distributed architectures. The layer can also improve over time by incorporating agent usage, human feedback, and steward corrections, with the goal of giving both people and AI systems a current, certified shared understanding of enterprise data.

As companies increasingly favor AI over traditional Business Intelligence (BI) dashboards, the shift is driven by the need for more dynamic, contextual, and rapid data analysis. AI provides the ability to engage in conversational analytics, allowing business users to ask ad hoc questions and receive immediate, context-rich answers, unlike the static nature of BI dashboards that often become obsolete due to the time taken to produce them. Despite AI's promise, success hinges on a robust data architecture that integrates data from various sources, enabling access to structured, unstructured, and semi-structured data. This transition involves overcoming challenges like AI's susceptibility to bias and hallucinations, and necessitates a federated data model and a well-defined governance framework. Starburst's enterprise intelligence platform exemplifies such a solution, offering data lakehouse technology to connect and manage data efficiently, thereby facilitating the transition to AI-enhanced decision-making.

In the evolving landscape of artificial intelligence, the text emphasizes the critical importance of context over merely relying on semantic layers to achieve accuracy in AI-driven decision-making and insights. Context encompasses the implicit knowledge a human possesses, such as fiscal calendars and business-specific definitions, which AI lacks unless explicitly provided. As AI models become commoditized and widely available, the differentiator shifts to how effectively an enterprise provides context to these models. The text outlines four types of context—technical, semantic, business, and operational—and introduces the concept of "context intelligence," which is essential for selecting, ranking, and applying the right context at query time. This context intelligence requires capabilities like resolution, schema linking, ranking, and attribution to ensure accuracy and adaptability. The text argues that while traditional semantic layers are necessary, they are insufficient for the dynamic and conversational nature of modern AI interfaces, which require a broader architecture that integrates governed context, a trust loop for continuous improvement, and the ability to self-heal and adapt as business environments change. This comprehensive approach, involving governed context and intelligence layers, ensures that AI systems not only provide accurate and relevant insights but also continuously evolve and improve over time.