1 of 1 people found this helpful
This SQL was probably generated by Tableau in response to a user's (complex-ish) filter or calculated field that is part of the workbook associated with the extract. If you can identify / remove the filter then your problem goes away...but the user who created this filter probably won't be very happy with you
Do you use Tableau Server, too? If so, I'd suggest you create a "virgin extract" with very few of these filters in place. This data source can be published to Tableau Server as a "Data Server Data Source",and then everyone can use it. They can also "decorate it" with additional stuff (like the filter)...The beauty of this will be that their "decoration filter" will only hit the EXTRACT. When the extract populates itself during your batch window, it'll be firing your clean SQL.
What about scheduling these extracts at night when no one is around? That would help, too.
yes I thought about that. its a few hundred million rows of data which takes quite a long time to chew through.
still much faster than seven functions in the where clause.