Cross-database joins in Tableau - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Cross-Database Joins in Tableau

Which statement best describes how Tableau handles cross-database joins?

A Tableau requires exporting all data into a single database before joining tables from different sources.

B Tableau combines data from different databases by creating a temporary in-memory join during query execution.

C Tableau cannot join tables from different databases directly; it only supports blending.

D Tableau duplicates all data from one database into the other to perform the join.

💡 Hint

Think about how Tableau processes data without moving it permanently.

Tableau performs cross-database joins by creating a temporary in-memory join at query time, allowing seamless combination of data from different sources without data duplication.

❓ dax_lod_result

intermediate

Result of Cross-Database Join with Filters

Given two tables from different databases joined in Tableau: Sales and Products. Sales has 1000 rows, Products has 100 rows. After applying a filter on Products to only include category 'Electronics' (20 products), how many rows will the joined result contain?

A All 1000 sales rows where the product is in 'Electronics' category, approximately 200 rows.

B All 1000 sales rows regardless of product category.

C Only 20 rows, one for each product in 'Electronics'.

D Exactly 1000 rows, but with nulls for non-matching products.

💡 Hint

Consider how the join and filter on the product table affect the sales rows.

The join filters sales rows to those matching products in the 'Electronics' category. If about 20% of sales are for electronics, the result will be about 200 rows.

❓ data_modeling

advanced

Designing Efficient Cross-Database Joins

You have two large tables from different databases: Orders (5 million rows) and Customers (500,000 rows). You want to join them in Tableau. Which design choice will optimize performance?

A Join without filters and use calculated fields to filter after joining.

B Use a full outer join to keep all data from both tables.

C Duplicate the Customers table into the Orders database before joining.

D Use an inner join on customer ID and apply filters to reduce data before joining.

💡 Hint

Think about reducing data volume before joining.

Applying filters before joining reduces the data volume, improving join performance. Inner join limits rows to matching keys, which is efficient.

🔧 Formula Fix

advanced

Troubleshooting Nulls in Cross-Database Join

After creating a cross-database join between Orders and Customers on Customer ID, many rows in the Orders table show nulls for customer fields. What is the most likely cause?

A The join type is left join from Customers to Orders, causing unmatched Orders rows to show nulls.

B The data source connection for Customers is broken, so fields cannot load.

C Customer IDs in Orders do not match any IDs in Customers, causing nulls in joined fields.

D Tableau does not support cross-database joins with Customer ID keys.

💡 Hint

Consider data quality and matching keys.

If Customer IDs in Orders do not exist in Customers, the join will produce nulls for customer fields in those rows.

❓ visualization

expert

Visualizing Cross-Database Join Results

You joined Sales data from a SQL Server database with Marketing Campaigns data from a cloud database using a cross-database join in Tableau. You want to create a dashboard showing total sales by campaign and campaign start date. Which visualization approach best follows best practices?

A Use a line chart with campaign start date on x-axis and total sales on y-axis, grouping by campaign.

B Use a pie chart showing total sales per campaign and a separate table listing campaign start dates.

C Use a scatter plot with campaign start date on x-axis and total sales on y-axis, with campaign names as labels.

D Use a bar chart with campaigns on the x-axis, total sales on the y-axis, and campaign start date as a color gradient.

💡 Hint

Think about how to show trends over time and compare campaigns clearly.

A line chart with campaign start date on the x-axis and total sales on the y-axis grouped by campaign clearly shows sales trends over time per campaign, following best visualization practices.

Practice

1. What is the main purpose of a cross-database join in Tableau?

easy

A. To export data to an external file

B. To create a copy of data within the same database

C. To combine tables from different data sources into one view

D. To filter data based on user input

Solution

1. Step 1: Understand cross-database join concept

   A cross-database join allows combining tables from different data sources in Tableau without moving data.

2. Step 2: Identify the main purpose

   The main goal is to create a richer view by joining data from multiple sources.

3. Final Answer:

   To combine tables from different data sources into one view -> Option C

4. Quick Check:

   Cross-database join = combine tables from different sources [OK]

Hint: Cross-database joins combine data from different sources [OK]

Common Mistakes:

• Thinking it copies data instead of joining
• Confusing with data filtering
• Assuming it exports data

2. Which of the following is the correct way to create a cross-database join in Tableau?

easy

A. Drag a table from one data source onto a table from another data source in the Data pane

B. Use the Data Extract option to combine tables

C. Create a calculated field to merge data sources

D. Export both tables and merge in Excel

Solution

1. Step 1: Recall Tableau's method for cross-database joins

   In Tableau, you drag a table from one data source onto another in the Data pane to create a cross-database join.

2. Step 2: Eliminate incorrect options

   Options A, B, and D describe other unrelated methods not used for cross-database joins in Tableau.

3. Final Answer:

   Drag a table from one data source onto a table from another data source in the Data pane -> Option A

4. Quick Check:

   Drag tables between sources = cross-database join [OK]

Hint: Drag tables between sources to join cross-database [OK]

Common Mistakes:

• Using data extracts instead of joins
• Trying to merge with calculated fields
• Exporting data outside Tableau

3. Given two tables from different databases joined on CustomerID, what happens if some CustomerID values exist only in one table?

medium

A. Those rows will be excluded from the join result

B. Those rows will appear with NULLs for missing columns

C. Tableau will throw an error and stop the join

D. Those rows will be duplicated in the result

Solution

1. Step 1: Understand join behavior with unmatched keys

   When joining tables, rows with keys only in one table appear with NULLs for columns from the other table if using a left or full outer join.

2. Step 2: Apply to cross-database join context

   In Tableau cross-database joins, unmatched keys show rows with NULLs, not excluded or duplicated.

3. Final Answer:

   Those rows will appear with NULLs for missing columns -> Option B

4. Quick Check:

   Unmatched keys = rows with NULLs [OK]

Hint: Unmatched keys show NULLs, not errors or duplicates [OK]

Common Mistakes:

• Assuming unmatched rows are excluded
• Expecting errors on unmatched keys
• Thinking unmatched rows duplicate

4. You created a cross-database join but Tableau shows incorrect results. Which of these is the most likely cause?

medium

A. You joined tables from the same database

B. You forgot to refresh the data extract

C. You used a calculated field instead of a join

D. Join keys have mismatched data types between sources

Solution

1. Step 1: Identify common issues in cross-database joins

   Mismatched data types in join keys cause incorrect or missing matches in joins.

2. Step 2: Evaluate other options

   Refreshing extracts or using calculated fields are unrelated to join key mismatches; joining same database tables is valid but not an error cause here.

3. Final Answer:

   Join keys have mismatched data types between sources -> Option D

4. Quick Check:

   Data type mismatch = wrong join results [OK]

Hint: Check join key data types match across sources [OK]

Common Mistakes:

• Ignoring data type differences
• Assuming refresh fixes join logic
• Confusing calculated fields with joins

5. You want to join a large SQL Server sales table with a small Excel customer list using a cross-database join. What is the best practice to optimize performance?

hard

A. Create extracts for both sources before joining

B. Use a left join with the Excel table on the left side

C. Import the Excel data into SQL Server and join there

D. Join directly without extracts to get live data

Solution

1. Step 1: Understand performance impact of cross-database joins

   Joining large and small tables across sources can slow performance; extracts improve speed by caching data.

2. Step 2: Evaluate options for optimization

   Creating extracts for both sources reduces query time and improves join speed compared to live joins.

3. Final Answer:

   Create extracts for both sources before joining -> Option A

4. Quick Check:

   Extracts speed up cross-database joins [OK]

Hint: Use extracts to speed up cross-database joins [OK]

Common Mistakes:

• Joining live without extracts on large data
• Importing Excel into SQL unnecessarily
• Placing smaller table on left without extracts