Google pushed the "measures" feature of BigQuery Graph to preview this week, targeting the most common failure mode for enterprise AI Agents (AI programs that autonomously call tools to complete tasks) — looking like an answer, but actually nonsense. The company's own negative case: an Agent at a retailer saw "Seattle winter coat sales down 12%" and immediately recommended an across-the-board 15% discount, without knowing the real cause was a regional blizzard that delayed suppliers. The Agent took action, but answered the wrong question.
What this is
Traditional enterprise data mostly lives in flat tables: order tables, customer tables, product tables. When an Agent needs to analyze, it can only run SQL queries (using structured query language to pull data from a database), seeing "what happened" but not "why."
Google's solution this time is to introduce a "graph" structure — in short, drawing the relationships between data (who supplies whom, which warehouse covers which city) as a network, then layering metrics (such as sales and profit margin) on top. The Agent can then follow the network to drill down: sales dropped → which region dropped hardest → did that region's suppliers have issues → and only then does the answer land on the actual point.
Technically, Google defined MEASURE fields directly inside BigQuery's Property Graph (a data structure that uses nodes and edges to describe entity relationships), so SQL doesn't double-count rows during graph traversal, avoiding the "counted twice" bug.
Industry view
Supporters call this "the last mile of enterprise AI implementation." For the past two years, large model companies have been racing on parameters and context windows — but what truly blocks enterprises is: data scattered across a dozen systems, with business relationships never clearly mapped. By connecting the graph database and the metrics layer, Google gives Agents a tool to "see the whole picture."
But there are sober voices. A Forrester analyst recently warned that laying graph structure across an enterprise's full data set is an engineering effort comparable to deploying another data warehouse; and once business relationships are mapped incorrectly, the "insights" an Agent produces become even more misleading — because they sound more plausible. A product lead at a domestic data middle office vendor told us privately: "Everyone's talking about Agents now, but 80% of clients haven't even cleaned up their master data (an enterprise's core entity definitions — e.g., who exactly counts as a 'customer'). Talking about AI decision-making is premature."
Another risk is vendor lock-in. BigQuery Graph only runs on Google Cloud, meaning a company's relationship modeling and data governance all have to be bet on a single vendor. For organizations already on Snowflake or Databricks, migration costs are nontrivial.
Impact on regular people
For enterprise IT: What's most worth evaluating this year isn't another AI tool — it's a top-to-bottom review of your core business relationships: the dependency graph between suppliers, customers, and product lines. If you have to look up who to contact when an order goes wrong, no Agent can save you, no matter how smart.
For individual careers: The business analyst role is being redefined. Execution work — running queries, generating reports — will be eaten by Agents faster, but "judging whether the data is right, whether the relationships are mapped correctly" is becoming the new scarce skill. People who understand both business and data modeling will be worth more than pure SQL writers.
For the consumer market: You'll probably never use BigQuery Graph directly, but it determines whether the "personalized recommendation" the AI gives you next time you receive a brand push actually understands you, or is yet another baffling discount text.