<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Databricks Metric Views - Moving Towards Business Semantics in Community Articles</title>
    <link>https://community.databricks.com/t5/community-articles/databricks-metric-views-moving-towards-business-semantics/m-p/149921#M1054</link>
    <description>&lt;P&gt;Discussed the BI &amp;amp; Metrics Tax elimination using Databricks Metric Views &lt;A title="here" href="https://medium.com/@balajij8/eliminating-metrics-bi-tax-with-databricks-metric-views-041548df55f5" target="_self"&gt;here&lt;/A&gt;. Semantic Layer is a core component of the lakehouse with Metric Views.&amp;nbsp;Modern stack is moving toward ai data experiences where organizations ask questions instead of building large ad hoc queries &amp;amp; dashboards.&lt;/P&gt;&lt;P&gt;&lt;FONT size="5"&gt;&lt;U&gt;&lt;STRONG&gt;Semantic Layer belongs to the Lakehouse&lt;/STRONG&gt;&lt;/U&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;Semantic layers resided in BI tools (Tableau, Power BI) &amp;amp; adhoc SQL tools creating fragmentations in the last decades. Organizations can define BI logic once by moving KPIs to metric view definitions into the lakehouse and use across the border.&lt;/P&gt;&lt;P&gt;&lt;FONT size="5"&gt;&lt;U&gt;&lt;STRONG&gt;Metric Views&lt;/STRONG&gt;&lt;/U&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;Metric Views are governed metric objects registered in Unity Catalog helping Organizations as a semantic layer embedded in Lakehouse.&amp;nbsp;AI BI Dashboards and Genie can now rely on the foundational metrics emitted via Metric Views in the Lakehouse.&amp;nbsp; Organizations gain&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Consistent metrics across tools&lt;/LI&gt;&lt;LI&gt;Strong governance and lineage&lt;/LI&gt;&lt;LI&gt;Faster self analytics&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;FONT size="5"&gt;&lt;U&gt;&lt;STRONG&gt;Building Metric Views&lt;/STRONG&gt;&lt;/U&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;Metric View has few core ingredients such as the fact source (table/view/sql), measures (calculations) and dimensions (region, sales year). Find the regional revenue metric view below&lt;/P&gt;&lt;P&gt;&lt;FONT color="#008000"&gt;&lt;EM&gt;CREATE VIEW regional_revenue_metrics&lt;/EM&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#008000"&gt;&lt;EM&gt;WITH METRICS&lt;/EM&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#008000"&gt;&lt;EM&gt;LANGUAGE YAML&lt;/EM&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#008000"&gt;&lt;EM&gt;AS&lt;/EM&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#008000"&gt;&lt;EM&gt;version: 1.1&lt;/EM&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#008000"&gt;&lt;EM&gt;comment: "Standardized Regional Revenue KPIs for cross reporting"&lt;/EM&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#008000"&gt;&lt;EM&gt;source: sales.silver.orders_region -- Point to the table&lt;/EM&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#008000"&gt;&lt;EM&gt;dimensions:&lt;/EM&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#008000"&gt;&lt;EM&gt;- name: Transaction Year&lt;/EM&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#008000"&gt;&lt;EM&gt;expr: DATE_TRUNC ('YEAR', date)&lt;/EM&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#008000"&gt;&lt;EM&gt;- name: Market Segment&lt;/EM&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#008000"&gt;&lt;EM&gt;expr: segment&lt;/EM&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#008000"&gt;&lt;EM&gt;- name: Revenue Category&lt;/EM&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#008000"&gt;&lt;EM&gt;expr: |&lt;/EM&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#008000"&gt;&lt;EM&gt;CASE&lt;/EM&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#008000"&gt;&lt;EM&gt;WHEN price &amp;gt; 1000 THEN 'High Value'&lt;/EM&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#008000"&gt;&lt;EM&gt;WHEN price BETWEEN 1000 AND 10000 THEN 'Mid'&lt;/EM&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#008000"&gt;&lt;EM&gt;ELSE 'Standard'&lt;/EM&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#008000"&gt;&lt;EM&gt;END&lt;/EM&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#008000"&gt;&lt;EM&gt;measures:&lt;/EM&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#008000"&gt;&lt;EM&gt;- name: Gross Revenue&lt;/EM&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#008000"&gt;&lt;EM&gt;expr: SUM (price)&lt;/EM&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#008000"&gt;&lt;EM&gt;- name: Regional Order Volume&lt;/EM&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#008000"&gt;&lt;EM&gt;expr: COUNT (DISTINCT key)&lt;/EM&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#008000"&gt;&lt;EM&gt;- name: Average Deal Size&lt;/EM&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#008000"&gt;&lt;EM&gt;expr: SUM (price) / COUNT (key)&lt;/EM&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#008000"&gt;&lt;EM&gt;- name: Tax Impact&lt;/EM&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#008000"&gt;&lt;EM&gt;expr: SUM (price * (1 + tax))&lt;/EM&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;Metric Views translates transaction data into business concepts (Gross Revenue, Regional Order Volume). The metrics can power AI/BI Dashboards or Databricks Genie.&amp;nbsp;Organizations can create &amp;amp; expose high quality semantic metrics and dimensions to BI tools seamlessly.&lt;/P&gt;&lt;P&gt;&lt;EM&gt;&lt;STRONG&gt;Created the metric views part of a regional sales semantic layer &amp;amp; compatibility with AI BI stack is great.&amp;nbsp;&lt;/STRONG&gt;&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Define metrics once&lt;/STRONG&gt; - Organizations should maintain a single definition for key KPIs such as revenue, active users or conversion rate.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Semantic naming&lt;/STRONG&gt; - Avoid column names such as cus_geo_rgn_cd. Expose clear dimensions such as customer_region.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;KPI Metric&lt;/STRONG&gt; - Semantic layer should focus on creating KPI logic and not complex transformations (ETL).&lt;/P&gt;</description>
    <pubDate>Thu, 05 Mar 2026 16:55:37 GMT</pubDate>
    <dc:creator>balajij8</dc:creator>
    <dc:date>2026-03-05T16:55:37Z</dc:date>
    <item>
      <title>Databricks Metric Views - Moving Towards Business Semantics</title>
      <link>https://community.databricks.com/t5/community-articles/databricks-metric-views-moving-towards-business-semantics/m-p/149921#M1054</link>
      <description>&lt;P&gt;Discussed the BI &amp;amp; Metrics Tax elimination using Databricks Metric Views &lt;A title="here" href="https://medium.com/@balajij8/eliminating-metrics-bi-tax-with-databricks-metric-views-041548df55f5" target="_self"&gt;here&lt;/A&gt;. Semantic Layer is a core component of the lakehouse with Metric Views.&amp;nbsp;Modern stack is moving toward ai data experiences where organizations ask questions instead of building large ad hoc queries &amp;amp; dashboards.&lt;/P&gt;&lt;P&gt;&lt;FONT size="5"&gt;&lt;U&gt;&lt;STRONG&gt;Semantic Layer belongs to the Lakehouse&lt;/STRONG&gt;&lt;/U&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;Semantic layers resided in BI tools (Tableau, Power BI) &amp;amp; adhoc SQL tools creating fragmentations in the last decades. Organizations can define BI logic once by moving KPIs to metric view definitions into the lakehouse and use across the border.&lt;/P&gt;&lt;P&gt;&lt;FONT size="5"&gt;&lt;U&gt;&lt;STRONG&gt;Metric Views&lt;/STRONG&gt;&lt;/U&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;Metric Views are governed metric objects registered in Unity Catalog helping Organizations as a semantic layer embedded in Lakehouse.&amp;nbsp;AI BI Dashboards and Genie can now rely on the foundational metrics emitted via Metric Views in the Lakehouse.&amp;nbsp; Organizations gain&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Consistent metrics across tools&lt;/LI&gt;&lt;LI&gt;Strong governance and lineage&lt;/LI&gt;&lt;LI&gt;Faster self analytics&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;FONT size="5"&gt;&lt;U&gt;&lt;STRONG&gt;Building Metric Views&lt;/STRONG&gt;&lt;/U&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;Metric View has few core ingredients such as the fact source (table/view/sql), measures (calculations) and dimensions (region, sales year). Find the regional revenue metric view below&lt;/P&gt;&lt;P&gt;&lt;FONT color="#008000"&gt;&lt;EM&gt;CREATE VIEW regional_revenue_metrics&lt;/EM&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#008000"&gt;&lt;EM&gt;WITH METRICS&lt;/EM&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#008000"&gt;&lt;EM&gt;LANGUAGE YAML&lt;/EM&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#008000"&gt;&lt;EM&gt;AS&lt;/EM&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#008000"&gt;&lt;EM&gt;version: 1.1&lt;/EM&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#008000"&gt;&lt;EM&gt;comment: "Standardized Regional Revenue KPIs for cross reporting"&lt;/EM&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#008000"&gt;&lt;EM&gt;source: sales.silver.orders_region -- Point to the table&lt;/EM&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#008000"&gt;&lt;EM&gt;dimensions:&lt;/EM&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#008000"&gt;&lt;EM&gt;- name: Transaction Year&lt;/EM&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#008000"&gt;&lt;EM&gt;expr: DATE_TRUNC ('YEAR', date)&lt;/EM&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#008000"&gt;&lt;EM&gt;- name: Market Segment&lt;/EM&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#008000"&gt;&lt;EM&gt;expr: segment&lt;/EM&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#008000"&gt;&lt;EM&gt;- name: Revenue Category&lt;/EM&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#008000"&gt;&lt;EM&gt;expr: |&lt;/EM&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#008000"&gt;&lt;EM&gt;CASE&lt;/EM&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#008000"&gt;&lt;EM&gt;WHEN price &amp;gt; 1000 THEN 'High Value'&lt;/EM&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#008000"&gt;&lt;EM&gt;WHEN price BETWEEN 1000 AND 10000 THEN 'Mid'&lt;/EM&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#008000"&gt;&lt;EM&gt;ELSE 'Standard'&lt;/EM&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#008000"&gt;&lt;EM&gt;END&lt;/EM&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#008000"&gt;&lt;EM&gt;measures:&lt;/EM&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#008000"&gt;&lt;EM&gt;- name: Gross Revenue&lt;/EM&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#008000"&gt;&lt;EM&gt;expr: SUM (price)&lt;/EM&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#008000"&gt;&lt;EM&gt;- name: Regional Order Volume&lt;/EM&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#008000"&gt;&lt;EM&gt;expr: COUNT (DISTINCT key)&lt;/EM&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#008000"&gt;&lt;EM&gt;- name: Average Deal Size&lt;/EM&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#008000"&gt;&lt;EM&gt;expr: SUM (price) / COUNT (key)&lt;/EM&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#008000"&gt;&lt;EM&gt;- name: Tax Impact&lt;/EM&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#008000"&gt;&lt;EM&gt;expr: SUM (price * (1 + tax))&lt;/EM&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;Metric Views translates transaction data into business concepts (Gross Revenue, Regional Order Volume). The metrics can power AI/BI Dashboards or Databricks Genie.&amp;nbsp;Organizations can create &amp;amp; expose high quality semantic metrics and dimensions to BI tools seamlessly.&lt;/P&gt;&lt;P&gt;&lt;EM&gt;&lt;STRONG&gt;Created the metric views part of a regional sales semantic layer &amp;amp; compatibility with AI BI stack is great.&amp;nbsp;&lt;/STRONG&gt;&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Define metrics once&lt;/STRONG&gt; - Organizations should maintain a single definition for key KPIs such as revenue, active users or conversion rate.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Semantic naming&lt;/STRONG&gt; - Avoid column names such as cus_geo_rgn_cd. Expose clear dimensions such as customer_region.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;KPI Metric&lt;/STRONG&gt; - Semantic layer should focus on creating KPI logic and not complex transformations (ETL).&lt;/P&gt;</description>
      <pubDate>Thu, 05 Mar 2026 16:55:37 GMT</pubDate>
      <guid>https://community.databricks.com/t5/community-articles/databricks-metric-views-moving-towards-business-semantics/m-p/149921#M1054</guid>
      <dc:creator>balajij8</dc:creator>
      <dc:date>2026-03-05T16:55:37Z</dc:date>
    </item>
  </channel>
</rss>

