Using an extract filter is an effective way to reduce the amount of data in a Tableau extract. Extract filters allow you to specify a subset of the data to include, which can significantly decrease the size of the extract by excluding unnecessary data. This is particularly useful when you only need partial data from a larger SQL Server data source.
References: The recommendation to use extract filters to reduce data size is supported by Tableau's best practices for optimizing extracts. These practices suggest keeping the extract's data set short through filtering1. Additionally, discussions in the Tableau Community confirm that hiding fields and using extract filters before extracting data can help reduce the extract size2.
When dealing with large datasets in SQL Server and needing to create a manageable extract in Tableau, using an extract filter is the most direct and effective method to limit the data included:
Extract Filter: This involves setting filters that apply directly when the data is extracted from the source. This means that only the data meeting the specified criteria will be extracted and loaded into Tableau, significantly reducing the size of the extract.
To apply an extract filter, in the Data Source page in Tableau, drag the fields you want to filter by to the Filters shelf. Then, configure the desired filter criteria. When you create the extract, choose the option to "Add Filters to Extract" and select the configured filters. This ensures that only the data that meets these conditions is extracted from the SQL Server.
This approach not only minimizes the data volume but also speeds up performance in Tableau because it processes a smaller subset of the full dataset.
References
This procedure is described in detail in Tableau's help documentation on managing extracts and optimizing performance by using extract filters, which is recommended for scenarios involving large datasets or when specific subsets of data are required for analysis.

For a performant live connection in Tableau Cloud, especially when dealing with large datasets that preclude the use of extracts, relating the tables in Tableau Desktop is the recommended approach. This method allows for flexibility in how the data is queried and can improve performance by leveraging Tableau's relationships feature, which optimizes queries for the underlying database.
References: The best practices for live connections in Tableau Cloud suggest using relationships to manage complex data models efficiently1. Additionally, Tableau's documentation on connecting data sources recommends using relationships for better performance with live connections2.

To effectively display quarterly profit growth and aggregated sales totals across different product categories, a combination of a Waterfall chart and a Tree Map is recommended:
Waterfall Chart: This chart type is excellent for visualizing the sequential growth or decline of profits across different quarters for each sub-category. It clearly shows how profits accumulate over time, highlighting both positive and negative changes, which makes it ideal for tracking profit growth or decline through the quarters.
Tree Map: A Tree Map can efficiently display aggregated sales totals where each block size represents the total sales of a product category, providing a quick, visually impactful comparison across categories. This is especially useful when the client wants to understand which categories contribute most to sales in a glanceable format.
Together, these charts provide a comprehensive overview of both profit trends over time (Waterfall Chart) and a comparative snapshot of sales performance across categories (Tree Map), meeting the client's need to analyze performance dynamics in a detailed yet consolidated manner.
References
These recommendations are based on common best practices for data visualization in Tableau, where specific chart types are chosen for their strengths in communicating certain types of data relationships and dynamics, as detailed in Tableau's official visualization guides.

. Add the calculated fields as a Detail under the Marks card of the floating view, create a "Change Parameter" action, and set the
"Target Parameter" and "Source Fields" to the parameter and calculated field you created.
. Check the box for "Control visibility using value" in the Layout tab of the floating view and select the parameter you created.
Explanation:
The most efficient method for toggling between two views (forecast summaries and year-on-year metrics) while keeping main KPIs visible involves using a parameter and calculated fields for controlling visibility:
Create a Boolean Parameter: This parameter will have two aliases representing the two views ("Forecast View" and "Year-on-Year View"). This allows the user to select which view they wish to see directly from the dashboard.
Calculated Field: Create a calculated field that always returns True. This field acts as a constant placeholder to enable the visibility control tied to the parameter.
Dashboard Setup: Place both the forecast summary and the year-on-year metrics sheets on the dashboard. Set the year-on-year metrics sheet as a floating object over the forecast summary.
Visibility Control: Use the "Control visibility using value" option in the Layout tab for the floating year-on-year metrics view. Tie this setting to the Boolean parameter so that changing the parameter will show or hide this view without affecting the main KPIs displayed on the dashboard.
Interactivity: Implement a "Change Parameter" dashboard action where selecting different options in the dashboard (e.g., clicking on certain parts) triggers the parameter to change, thus toggling the visible view.
References
This method leverages Tableau's dashboard interactivity features including parameters, calculated fields, and visibility settings, as recommended in Tableau's user guide on dynamic dashboard design.

For optimal performance, it is recommended to limit the data to what is necessary for analysis, which in this case would be the current and previous years. Moving the calculation of averages to the data layer and aggregating the dates to a monthly level will reduce the granularity of the data, thereby improving the performance of the dashboard. This approach aligns with best practices for optimizing workbook performance in Tableau, which suggest simplifying the data model and reducing the number of records processed12.
References: The recommendation is based on the guidelines provided in Tableau's official documentation on optimizing workbook performance, which includes tips on data management and aggregation for better performance12.