How to See SQL in Tableau

Ever wondered what’s happening behind the scenes when you drag and drop fields in Tableau? Tableau translates your visual actions into Structured Query Language (SQL) and sends those commands to your database. This article will show you exactly how to see that auto-generated SQL, giving you a powerful tool for debugging, performance tuning, and deepening your data skills.

Graphed

Build AI Agents for Marketing

Build virtual employees that run your go to market. Connect your data sources, deploy autonomous agents, and grow your company.

Build Your First Agent

Why Look at Tableau's Auto-Generated SQL?

Viewing the SQL Tableau generates isn't just an academic exercise, it's a practical skill that helps you build better, faster dashboards. It's like looking under the hood of your car - you start to understand how all the parts work together.

• For Debugging: Sometimes a visualization shows a number that just doesn't feel right. Seeing the SQL can reveal an unexpected join, an incorrect aggregation (like SUM vs. AVG), or a filter that's not being applied as you intended. The query is the ultimate source of truth for what data is being pulled into your view.
• For Performance Tuning: If a dashboard is slow, the auto-generated SQL is often the first place to look. A verbose query with excessive joins or inefficient subqueries can bring a database to its knees. By identifying the bottleneck SQL, you can optimize your data model, adjust calculations, or work with your data team to create more efficient database views.
• For Learning SQL: If you're new to SQL, there's no better teacher than Tableau. Build a simple view with a few dimensions, measures, and filters. Then, examine the SQL it generates. You'll quickly learn the syntax for SELECT, FROM, WHERE, GROUP BY, and more, seeing a direct link between your visual choices and the underlying code.
• For Creating Custom SQL: You can copy Tableau’s auto-generated SQL and use it as a starting point for your own Custom SQL connections, modifying it to handle more complex transformations or logic that are difficult to achieve with the standard drag-and-drop interface.

Method 1: Using Tableau’s Performance Recorder

The Performance Recorder is the most direct and user-friendly way to see the SQL commands Tableau sends to a live database connection. It records the performance information for key events you perform, including query execution.

Step-by-Step Guide:

1. Start the Recorder: In Tableau Desktop, navigate to the top menu and select Help > Settings and Performance > Start Performance Recording.
2. Perform the Action: Now, perform the single, specific action you want to analyze. This could be refreshing a data source, applying a filter, or simply dragging a new field onto a worksheet. It is best to keep this action isolated to avoid cluttering the performance log with irrelevant queries.
3. Stop the Recorder: Once the action is complete (e.g., your worksheet has updated), go back to the menu and select Help > Settings and Performance > Stop Performance Recording.
4. Analyze the Results: A new Tableau workbook will automatically open. This is your Performance Summary dashboard. It contains three main sections:
5. Find Your SQL: In the Timeline view, look for green bars labeled "Executing Query". A single user action might generate multiple queries. Click on one of these green bars. The Query pane at the bottom of the dashboard will immediately populate with the full SQL code that Tableau sent to the database for that specific event. You can now copy and paste this query into a database client of your choice (like DBeaver or SQL Server Management Studio) to analyze or modify it further.

AI Agents for Marketing

Crash Course

Graphed

Free PDF · the crash course

AI Agents for Marketing Crash Course

Learn how to deploy AI marketing agents across your go-to-market — the best tools, prompts, and workflows to turn your data into autonomous execution without writing code.

Download the PDF

Method 2: Digging into Tableau’s Log Files

For a more comprehensive, raw view of everything Tableau is doing, you can look directly at its log files. This method captures all activity, including metadata queries, and is especially useful for troubleshooting complex connection issues or for situations where the performance recorder isn’t sufficient.

Step-by-Step Guide:

1. Locate Your Log Files: Tableau keeps its logs in your "My Tableau Repository" folder. The locations are typically:
2. Start with a Clean Slate: The logs can get very long and confusing. To isolate your query, close Tableau Desktop completely. Then, either delete or rename the existing log.txt file. The next time you open Tableau, it will generate a completely fresh one.
3. Recreate the Action: Open your Tableau workbook and perform the same action you want to investigate, just like you did for the performance recorder. After the action completes, close Tableau Desktop once more to ensure the session logs are fully written to the file.
4. Search the Log File: Open the newly created log.txt file in a text editor (Notepad++ or VS Code work well as they have better search capabilities than a standard notepad). The file is verbose, containing a lot of JSON and XML, so you need to know what to look for. Use the search function (Ctrl+F or Cmd+F) to find one of these keywords:

Here's an example of what you might find in the logs:

What About SQL for Tableau Extracts (.hyper)?

This is a common point of confusion. Tableau extracts - the .hyper files - are highly optimized, columnar in-memory databases. When you interact with a dashboard built on an extract, Tableau is not generating standard SQL. Instead, it uses a proprietary internal query process to pull data from the hyper file.

Because of this, you cannot use the Performance Recorder or log files to see real-time SQL queries against a Tableau Extract. The "Executing Query" event for an extract just shows an internal command to the Hyper engine, not human-readable SQL.

However, you can see the SQL that Tableau used to create or refresh the extract in the first place. To do this, simply start the Performance Recorder just before you click the "Create Extract" or "Refresh" button. The resulting log will capture the query sent to your original live database to pull the necessary data to build the .hyper file.

Graphed

Build AI Agents for Marketing

Build virtual employees that run your go to market. Connect your data sources, deploy autonomous agents, and grow your company.

Build Your First Agent

When to Take Over with Custom SQL

Once you are comfortable reading Tableau’s SQL, you may be tempted to write your own using the Custom SQL option when connecting to data. This gives you complete control by allowing you to write your own SELECT statement. It's powerful, but should be used wisely.

Reasons to Use Custom SQL:

• Performing cross-database joins that Tableau can't do natively.
• Unpivoting data - turning columns into rows.
• Leveraging special, database-specific functions (like string parsing functions) during ingestion.
• Pre-aggregating data or applying complex logic before the data ever reaches Tableau.

Cautions with Custom SQL:

Be careful, as custom SQL can sometimes harm performance more than it helps. Tableau often bundles your entire Custom SQL query into a subquery. For example, your query:

SELECT * FROM my_table WHERE region = 'West'

May become part of a larger query run by Tableau:

SELECT * FROM (
    SELECT * FROM my_table WHERE region = 'West'
) AS "CustomSQLQuery"
WHERE "CustomSQLQuery"."state" = 'California'

This "wrapping" can prevent the database’s own query optimizer from working efficiently and may lead to performance issues, as the entire inner query might run before outer filters are applied. Whenever possible, it's better to let Tableau construct the query from the standard drag-and-drop interface, as it has more latitude to generate optimized, efficient code.

AI Agents for Marketing

Crash Course

Graphed

Free PDF · the crash course

AI Agents for Marketing Crash Course

Learn how to deploy AI marketing agents across your go-to-market — the best tools, prompts, and workflows to turn your data into autonomous execution without writing code.

Download the PDF

Final Thoughts

Understanding how to see the SQL behind your visualizations is a superpower. The Performance Recorder offers a quick and easy way to review queries on live connections, while Log Files provide a comprehensive look for deeper troubleshooting. This knowledge empowers you to build more efficient Tableau workbooks and resolve data discrepancies with confidence.

Instead of digging through log files or mastering complex query syntax, most marketing and sales teams just want a clear path from data to decision. With Graphed, you skip this entire troubleshooting process. We connect directly to your data sources like Google Analytics, Shopify, and Salesforce, letting you build real-time dashboards and ask questions using plain English. We handle writing the efficient, optimized queries for you, turning hours of technical work into a 30-second conversation.