MIP Logo

New Feature in Tableau 2018.3 – Normalized Extract

This post was originally published on The Data School blog between 2018 and July 2025, before our program was renamed to MIP’s Analytics Career Accelerator. References throughout this article to “The Data School” or “DS” all refer to what is now MIP’s Analytics Career Accelerator. The program, its people, and its commitment to launching outstanding analytics careers remain the same – just under a new name.

If you are having trouble viewing this article, please report it here. 

 Multiple table Hyper extracts

  Normalized Extracts is a new performance feature for extracts with one or more join statements. Now each table you see in the connection pane will be brought in and stored as separate tables in a single Hyper extract file. This will result in smaller extract file size and fastest extract creation and refresh. 

How it was earlier? 

You were getting following window with no option to choose from Single table or Multiple table

 

 

 

 

 

 

 

 

 

 

How to create a normalised extract:

  •   Connect to your data and join two or more  tables.
  •    In the upper-right corner, select Extract, and then click the Edit link to open the extract Data dialog box.
  •    Under “Schema,” select “Multiple Tables.”
  •    Click “OK

 

 

 

 

How to view your extract schema?

  •    In any of the sheet tabs, right-click your extracted data source. It’s under the “Data” section in the top-left corner of the window.
  •    Select Extract ­- Properties and in Data Storage, we can read Multiple Tables

Best practices for entitlements tables are now feasible in Extracts

Earlier, joining an entitlement table and a fact table into a single table would result in too many rows for extract creation to be feasible. Now, these tables can be stored separately in the extract file, before the join, so the extract creation is much faster.

Limitations

There are few limitations for other extract functionality while using normalised extract by selecting “Multiple tables” 

  •     No incremental refresh
  •     no extract filters
  •     no top-N / sampling
  •     no database-specific functions (neither in calculated columns nor in join conditions)
  •     only equality-based joins in the join conditions.

 

 

 

 

 

 

 

 

 

 

 

Share this post