https://community.databricks.com/t5/community-articles/serving-tableau-and-databricks-dashboards-from-one-gold-layer/m-p/160844#M1326 <P>Part 5 - the final post in my enterprise data platform series - is up. This one is about what actually happened when we connected BI tools to the Views layer.</P><P>We had two tools: Tableau for the finance team's analytical workbooks, and Databricks Dashboards for operational reporting. Both connect to the same Unity Catalog views. No logic duplicated in either tool.</P><P>What the post covers:</P><UL><LI><STRONG>Live vs Extract tradeoffs</STRONG> - we defaulted to Live for everything and immediately hit 90-second query times from Tableau's generated SQL. Switched high-complexity analytical workbooks to scheduled Extracts</LI><LI><STRONG>The DECIMAL (18,2) precision issue</STRONG> - Tableau attempts to cast these to FLOAT in certain chart types, losing precision. Fixed with explicit CAST to DOUBLE in Tableau-specific view variants</LI><LI><STRONG>Partition scan problem</STRONG> - Tableau-generated queries bypassing partition pruning, and how embedding explicit WHERE predicates in view definitions fixed it</LI><LI><STRONG>Compute separation</STRONG> - batch Extract jobs competing with interactive queries at 9am, and why we split into dedicated Interactive and Batch SQL Warehouses</LI><LI><STRONG>Unity Catalog governing both tools from one definition</STRONG> - access controls, row filters, and column masking defined once, inherited by both tools automatically</LI></UL><P>The series wrap-up is in this post too - five parts condensed into one paragraph if you want the full picture before deciding which parts to read.</P><P>Full post on Medium: <A href="https://medium.com/@savlahanish/tableau-and-databricks-dashboards-from-one-gold-layer-no-duplication-heres-how-e6e309b66837" target="_blank">https://medium.com/@savlahanish/tableau-and-databricks-dashboards-from-one-gold-layer-no-duplication-heres-how-e6e309b66837</A></P><P>Happy to answer questions on any of the decisions - particularly around the Live vs Extract choice or the compute separation setup.</P> Mon, 29 Jun 2026 11:29:25 GMT savlahanish27 2026-06-29T11:29:25Z https://community.databricks.com/t5/community-articles/serving-tableau-and-databricks-dashboards-from-one-gold-layer/m-p/160844#M1326 <P>Part 5 - the final post in my enterprise data platform series - is up. This one is about what actually happened when we connected BI tools to the Views layer.</P><P>We had two tools: Tableau for the finance team's analytical workbooks, and Databricks Dashboards for operational reporting. Both connect to the same Unity Catalog views. No logic duplicated in either tool.</P><P>What the post covers:</P><UL><LI><STRONG>Live vs Extract tradeoffs</STRONG> - we defaulted to Live for everything and immediately hit 90-second query times from Tableau's generated SQL. Switched high-complexity analytical workbooks to scheduled Extracts</LI><LI><STRONG>The DECIMAL (18,2) precision issue</STRONG> - Tableau attempts to cast these to FLOAT in certain chart types, losing precision. Fixed with explicit CAST to DOUBLE in Tableau-specific view variants</LI><LI><STRONG>Partition scan problem</STRONG> - Tableau-generated queries bypassing partition pruning, and how embedding explicit WHERE predicates in view definitions fixed it</LI><LI><STRONG>Compute separation</STRONG> - batch Extract jobs competing with interactive queries at 9am, and why we split into dedicated Interactive and Batch SQL Warehouses</LI><LI><STRONG>Unity Catalog governing both tools from one definition</STRONG> - access controls, row filters, and column masking defined once, inherited by both tools automatically</LI></UL><P>The series wrap-up is in this post too - five parts condensed into one paragraph if you want the full picture before deciding which parts to read.</P><P>Full post on Medium: <A href="https://medium.com/@savlahanish/tableau-and-databricks-dashboards-from-one-gold-layer-no-duplication-heres-how-e6e309b66837" target="_blank">https://medium.com/@savlahanish/tableau-and-databricks-dashboards-from-one-gold-layer-no-duplication-heres-how-e6e309b66837</A></P><P>Happy to answer questions on any of the decisions - particularly around the Live vs Extract choice or the compute separation setup.</P> Mon, 29 Jun 2026 11:29:25 GMT https://community.databricks.com/t5/community-articles/serving-tableau-and-databricks-dashboards-from-one-gold-layer/m-p/160844#M1326 savlahanish27 2026-06-29T11:29:25Z