📊 HiddenMerit Morning Post · Issue 68
Focus on Database Frontiers, Practical Insights for DBAs August 5, 2026 ｜ 5 Selected Global Breaking News
01｜Google Launches Two AI Database Agents: Setup Agent + Observability Agent, Natural Language Takes Over Daily Operations
On August 4, Google officially launched two AI database agents – Database Onboarding Agent and Database Observability Agent – as the latest implementation of its Agentic Data Cloud strategy. The former handles database initialisation setup and configuration recommendations. Users simply describe their workload requirements in natural language (e.g., “I need a PostgreSQL instance that supports high‑concurrency read/write”), and the system automatically recommends the appropriate instance type and generates deployment commands. The latter focuses on daily operations, integrating telemetry data from Database Insights, Cloud Monitoring, Cloud Logging, and Cloud Trace. Users can query via natural language such as “Which databases had the highest CPU usage in the last hour?” or “Why is there lock contention?” The system automatically identifies root causes and provides remediation recommendations, with automatic execution after approval in some scenarios.
The observability agent covers Google’s full range of managed database products, including AlloyDB, Bigtable, Cloud SQL (PostgreSQL/MySQL/SQL Server), Spanner, Firestore, and Memorystore.
- DBA Perspective: Google’s AI database agents are another milestone in “intelligent operations” for cloud databases. Unlike Tencent Cloud’s DatabaseClaw approach of “distilling hundreds of thousands of DBA work orders into Skills,” Google has chosen a technological path of “natural language + full‑stack telemetry fusion.” For DBAs, this means routine monitoring, slow query analysis, capacity assessment, and other repetitive tasks will gradually be replaced by AI agents. The DBA role is evolving from “manual operations” to “AI agent policy manager” – defining AI operational boundaries, auditing execution traces, and triggering circuit breakers during anomalies. DBAs should focus on the observability agent’s root cause analysis capability – it is the core indicator of whether AI truly “understands” the operational state of databases.
02｜ClickHouse Establishes Research Labs, CMU’s Andy Pavlo Appointed VP of Research
On August 4, open‑source real‑time analytics database ClickHouse announced the establishment of ClickHouse Labs and appointed Andy Pavlo, Associate Professor of Computer Science at Carnegie Mellon University (CMU) and head of the CMU Database Research Group, as Vice President of Research. Pavlo’s research areas include autonomous databases, transaction processing, and large‑scale data analytics – fields facing growing pressures in the context of increasingly AI‑driven workloads. ClickHouse Labs will focus on foundational research in database architecture, query processing, system performance, and infrastructure, with research outcomes benefiting both the ClickHouse and PostgreSQL open‑source projects.
Pavlo stated: “The most exciting database research doesn’t just put new ideas into papers, but proves their feasibility by building and testing real systems. ClickHouse has an excellent engineering culture, a strong open‑source community, and workloads that push database technology to its limits.” ClickHouse CTO Alexey Milovidov said: “We are delighted to have Andy Pavlo join ClickHouse as Vice President of Database Research and lead our new research team, ClickHouse Labs.”
- DBA Perspective: Andy Pavlo is a landmark figure in the database academic community – he has received the IEEE TCDE Ramez Elmasri Database Education Award, the VLDB Early Career Award, the NSF CAREER Award, the Sloan Research Fellowship, and the ACM SIGMOD Jim Gray Best Paper Award. The establishment of ClickHouse Labs sends two clear signals: first, the boundaries between academia and industry are further dissolving – CMU’s academic expertise will directly translate into production‑grade optimisations for ClickHouse; second, open‑source databases are building trust through “open research” – research outcomes will be publicly released, allowing external developers to review, test, and extend them, which is crucial for DBAs evaluating the long‑term vitality of database technology paths. Pavlo previously co‑founded OtterTune, which applied machine learning to database optimisation. His dual background in academia and business means ClickHouse is likely to accelerate in the direction of AI‑driven autonomous databases.
03｜July 2026 Domestic Database Milestones: OceanBase RMB 2‑3 Billion Funding, Kingware RMB 6.22 Million Contract, Dameng Xinchuang Deepening
According to Modb’s July domestic database milestones, the domestic database sector saw multiple landmark events in July:
Industry Events: The 2026 Trustworthy Database Development Conference was held, with CAICT releasing the “Database Development Research Report (2026)” and the “China Database Industry Landscape (2026).” OceanBase had “Government” added to its leader categories for the first time, achieving full coverage of the three core industries: finance, telecommunications, and government.
Financing: OceanBase officially launched its Series A funding round, targeting RMB 2‑3 billion, with annualised revenue exceeding RMB 1.4 billion, up approximately 70% year‑on‑year. This marks OceanBase’s first external funding, signalling the transition of domestic databases from “internal incubation” to “market‑oriented independent operations.”
Major Contracts: CETC Kingware won Dajia Insurance’s database licensing procurement project for approximately RMB 6.22 million, covering 81 group‑side licences and 3 asset management‑side licences. Previously, the OceanBase expansion project was won by Digital China for RMB 6.3 million – combined, the two contracts exceed RMB 12 million.
Technology Progress: LoongArch (loong64) officially entered the PostgreSQL official APT repository, becoming the fourth CPU architecture officially supported by PGDG, joining AMD64, ARM64, and PPC64EL.
Xinchuang List: The Phase IV security and reliability assessment results were announced, with 23 products from 16 vendors selected – 8 centralised and 15 distributed – with Grade II certification increasing to 6 products.
- DBA Perspective: July’s domestic database events delivered multiple signals: OceanBase’s funding validates the commercial maturity of domestic distributed databases; Kingware’s RMB 6.22 million insurance contract, combined with Dajia Insurance’s RMB 6.3 million OceanBase expansion order reported in Issue 62, confirms that a trend of “multi‑brand parallel procurement” is forming among leading insurers – DBAs need to focus on cross‑brand database operations capabilities rather than a single product; LoongArch’s entry into the PG official repository is a milestone for domestic chip ecosystems entering the international open‑source mainstream (previously, deploying PostgreSQL on LoongArch required manual source compilation or third‑party ports with lagging updates – now official APT sources provide synchronised versions with x86/ARM); Phase IV assessment provides DBAs with an authoritative “whitelist” reference for Xinchuang selection.
04｜Google Cloud: Database Onboarding Agent Completes Initial Configuration with Natural Language
Complementing News 01, the specific capabilities of Google’s Database Onboarding Agent deserve separate attention. The agent aims to solve the pain point of “complex documentation and numerous configuration parameters” in the initial database deployment phase. Users simply describe workload requirements in natural language (performance needs, data scale, data types, reliability requirements, etc.), and the agent recommends the best‑matched managed database service (AlloyDB, Cloud SQL, Spanner, Bigtable, etc.) and generates complete configuration and deployment commands.
The agent also supports understanding more granular technical metrics such as IOPS, latency thresholds, replication lag, and incorporates them into recommendations. Its design goal is to “put database guidance in chat, console, and developer interfaces,” enabling developers unfamiliar with specific database products to complete deployments quickly.
- DBA Perspective: The Onboarding Agent represents the trend of “zero‑friction deployment” for cloud databases. In the past, DBAs spent hours or even days researching the specifications, IOPS baselines, and replication topology configurations of different cloud database products. Now natural language descriptions can generate recommendations. For DBAs, this means repetitive deployment work will be significantly reduced, but it also requires DBAs to have the ability to “validate AI recommendation rationale” – understanding why AI recommends AlloyDB over Cloud SQL, and whether the recommended IOPS configuration meets real business peak demands.
05｜ClickHouse Labs: Another “Handshake” Between Academia and Industry
The establishment of ClickHouse Labs will conduct research that combines academic rigour with production‑grade validation. Researchers will work with ClickHouse engineers to test ideas under real workloads, with research outcomes publicly released for broader review and adoption. ClickHouse President Yury Izrailevsky said: “Because ClickHouse is open source, ideas generated here can be tested, challenged, and extended by teams around the world. ClickHouse Labs, under Andy’s leadership, will lead our investment in foundational research, helping shape the future of ClickHouse and the broader database industry.”
ClickHouse has a distinguished user base including Sony, Tesla, Anthropic, Memorial Sloan Kettering, Lyft, and Instacart.
- DBA Perspective: Andy Pavlo’s appointment is another significant milestone following his co‑founding of OtterTune (applying machine learning to database optimisation). For DBAs, this event means that ClickHouse’s technology roadmap for AI‑driven autonomous databases will gain academic‑level theoretical support. Pavlo’s autonomous database research at CMU’s Database Research Group could accelerate ClickHouse’s implementation in areas such as automatic tuning, anomaly detection, and query optimisation. DBAs should pay attention to ClickHouse Labs’ subsequent research publications – they are important references for assessing ClickHouse’s long‑term technology direction.
📚 SQL Little Knowledge Point
This Issue’s Knowledge Point: What is a “Database Observability Agent”?
A “Database Observability Agent” is Google’s latest AI operations tool. Its core difference from traditional monitoring systems lies in natural language‑driven interaction and cross‑service root cause analysis.
Traditional Monitoring vs. AI Observability Agent:
| Dimension | Traditional Monitoring System | Database Observability Agent |
|---|---|---|
| Interaction | Dashboards, alert rules, log search | Natural language queries |
| Data Integration | Services viewed independently | Fused Metrics+Logs+Traces |
| Root Cause Analysis | Manual investigation, multi‑system switching | Automatic correlation analysis, root cause identification |
| Remediation Execution | Manual operations | Automatic recommendation + execution after approval |
| Typical Query | “Why did CPU suddenly spike?” | System automatically identifies and provides recommendations |
Google Observability Agent’s Technical Path: Unifies telemetry data from Database Insights, Cloud Monitoring, Cloud Logging, and Cloud Trace. Users ask natural language questions (e.g., “Which databases consumed the most CPU?”), and the system automatically performs cross‑service correlation analysis, completing root cause identification within minutes. In some scenarios, the system can recommend remediation plans (e.g., “Recommend enabling connection pooling for Cloud SQL instances”), with automatic execution after user approval.
Implications for DBAs: Observability agents are freeing DBAs from the heavy work of “cross‑system log checking, monitoring review, and execution plan analysis,” but also require DBAs to have the ability to “evaluate AI root cause analysis conclusions” – understanding whether AI has missed critical context and whether the recommended remediation direction is correct. In the future, a DBA’s core competitiveness will no longer be “querying fast enough,” but “judging accurately enough.”
HiddenMerit Team Production Slogan: 绩优隐于内，金石启新程 | Hidden deep. Merit bold. Forge ahead.