Does Your Tableau Server Have Too Many Versions of the Same Number?
Every published .tdsx was reasonable on the day it was made. Together they are hundreds of private definitions of the same metric, and no way to tell which one is right.
The data warehouse automation platform trusted by data teams across industries
Does this sound familiar?
- Search for a metric on Tableau Server and four published data sources come back.
- Two departments quote different figures for the same month and both cite Tableau.
- Nobody knows which .tdsx is safe to delete, so none of them are.
- The same extract is stored several times over, and storage keeps growing.
Every published data source was a reasonable decision on its own day. The trouble is that each one also contains a private answer to what a metric means.
How the sprawl accumulates
- Duplicating is the fast path. Copying a data source and adjusting it ships tomorrow; changing a shared one needs agreement.
- The logic travels with the copy. Filters, exclusions and calculated fields are baked
into the
.tdsx. - The differences do not show. Two sources named “Sales” look identical from the catalogue.
- Nothing can be retired, because no one can prove which workbooks depend on which source.
Certification helps, but only after somebody decides what the number is. That decision is not a Tableau feature.
Why it lands on you
- You are asked to reconcile figures produced by choices made in other departments.
- Reconciliation is invisible work, noticed only when it has not been done.
- You can certify your own source. You cannot make four teams agree on one definition.
The work is in the wrong place
- Defining a metric is warehouse work. Done separately in each
.tdsx, it produces several answers. - It belongs in one central place: a data warehouse or data hub, built once and read by every workbook.
- If that sounds expensive, the estimate probably assumes hand built pipelines. A specialised automation platform generates them from a model, which changes both the cost and the time it takes.
What changes when the model arrives finished
Datavault Builder holds the business rules in the warehouse and generates the dimensional views that every workbook connects to.
- The metric is calculated once, and every workbook reads the same figure.
- The rule is visible and versioned, rather than sealed inside a published extract.
- Lineage shows the derivation, so a disagreement is settled by opening the graph.
- New questions reuse the model, which is what stops the next hundred copies.
- Storage stops multiplying, because the same mart serves many workbooks.
What to ask for
“We have four published sources calculating revenue differently, and the logic is inside the .tdsx files. Can the rule live in the warehouse so every workbook connects to one governed dimensional view?”
That moves the discussion from which data source is correct to where the definition belongs.
See It Working on Your Own Data
Book a free demo and bring the report that gives you the most trouble.
Three Steps to Numbers That Add Up
-
Extract the existing logic
Collect the calculations, joins and filters that live in your reports today.
-
Centralize it in one place
The logic moves into the warehouse model once, so every report reads the same definition.
-
Enjoy numbers that add up
Every report shows the same figure, and “where did this number come from” has a visible answer.
How Datavault Builder Hands Your Report a Finished Model
-
The model arrives finished
Datavault Builder generates the vault and the star schema to run natively in the database you already have: SQL Server, Azure SQL, Synapse, Fabric, Snowflake, Databricks or BigQuery.
-
The work leaves the report
No merge, no parsing, no fuzzy match. That work is gone from the report.
-
Sources arrive integrated
Customers from the ERP, the CRM and the web shop are matched into one set of conformed dimensions. The join happens once in the warehouse, not again in every report.
-
History you can query
Every change is retained as it arrives, so you can report as-was as well as as-is, even where the source system overwrites its own records.
-
Every number has lineage
The logic gains lineage, so “where did this number come from” has a visible answer.
-
Changes handled upstream
Slowly changing dimensions are handled upstream as vault satellites, not approximated.
Recognized by BARC in The Data Fabric Survey 26
Meet Our Expert
Twenty minutes with our Sales Director, and an honest answer on whether this fits your situation.
Matt Collett
Sales Director
Great, pick a time that works for you:
Other Problems This Series Covers
-
Are Your Tableau LOD Expressions Too Complex to Touch?
FIXED, INCLUDE and EXCLUDE are precise tools for genuine multi grain questions. Most of the ones in your workbook are there because the warehouse never resolved the grain or kept the history.
-
Do Your Tableau Extract Refreshes Keep Failing or Running Late?
The backgrounder times out, the .hyper file keeps growing, and the dashboard shows yesterday. The extract is large because it is carrying raw rows that were never aggregated upstream.
-
Is Your Tableau Dashboard Slow Every Time You Change a Filter?
Twenty seconds of “Executing Query” on every filter click. Tableau is not rendering slowly. It is waiting for a database that was handed a question it cannot answer quickly.