1 of 1 people found this helpful
It seems like 1 million rows should not be a problem.
Have you tried hide all unused fields to make it smaller? And did you see why it failed. I assume this is a hyper extract and you have Tableau Server?
If so Tableau server has some stats on failures if you hover over the marks under Background Tasks for Extracts. You can see the errors
This is 2018.2 Tableau Online, hopefully screens are similar in 10.5
You may need to look at Tableau Server Performance too we did a webinar on this
And there is some good info on Hyper here. At the post below there are even more resources.
Too much to read too little time
I can't say for sure what is the issue is. That said part of the issue is that the tables are not aggregated at the same level. While I was writing a custom SQL statement to help with this issue, it just won't work.
That said I had a conversation with my boss and we are going to build one view from one table as a single source. The other view from the other table as a single source. Both views will have a common hierarchy that will allow us to filter. While this does reduce some of Tableau's functionality at this point, hopefully in the future, I can have the DBA go back and create a custom view for me that will accomplish what I was originally trying to do.
Tableau is good and wonderful but poor data structure is hard to work around.