Tableau SQL Tutorial: Connections, Custom Queries and Data Grain

Tableau can analyze relational sources through live connections or extracts. Understand how source SQL shapes the data available to a workbook, then distinguish physical joins from logical relationships before interpreting marks and aggregated measures.

Here's a popular Tableau SQL video — watch it, then summarize it with one click. Or paste any other YouTube link below.

— or paste your own YouTube link —

Want to keep the key points from a YouTube video? Paste the link below to turn it into structured notes.

Why Use Tableau SQL Tutorial: Connections, Custom Queries and Data Grain

Frequently Asked Questions

Does custom SQL replace every Tableau calculation?

Custom SQL defines a source relation, while Tableau calculations operate within its analytical model and view context. Their timing and aggregation behavior differ, so moving logic between them can change the resulting meaning.

Why can a joined source overstate sales?

Joining a sale to several related detail records can repeat the original amount before Tableau aggregates it. Examine physical row grain rather than blaming the chart for correctly summing duplicated input values.

How does an extract affect freshness?

An extract stores a prepared copy used for analysis and must be refreshed according to its configuration. Source updates are not necessarily visible immediately simply because a workbook continues to open successfully.

Are relationships equivalent to physical joins?

Relationships preserve logical tables and guide how Tableau combines data for analysis, whereas physical joins define a flattened row structure. Choose with the analytical grain and query behavior in mind.

Why might a workbook behave differently after publishing?

The published environment may use different credentials, network access or refresh arrangements. Evaluate the deployed connection and source permissions before assuming a successful local workbook establishes a working server workflow.