2 of 2 people found this helpful
I'm afraid I don't fully understand your question. However, there are some things worth commenting on.
1.) Are you using Tableau data extracts (*.tde) and then publishing them to the source, separate from the workbook (*.twb) files? If not, you should consider using these. Tableau Data Extracts are by far the best way to optimize refresh performance.
2.) Why are you using Custom SQL for the connection? Without a specific example I would challenge you that you do not need to create custom SQL and should not be doing it. Use the "simple basic Tableau function" to connect to the source, through the customized Tableau data-source connector. Those connectors are highly optimized for performance and response. "Custom SQL leads consistently to particularly poorly optimized queries, because Tableau must wrap its queries around the ENTIRE Custom SQL query every time." Here is a helpful links to further explain this concept (and where the quote above came from):
3.) Why not publish all your data-source to one Project on the server to centralize their management, and then permission them accordingly to support workbooks published in other Projects? This speaks directly to your final point. The same blog as noted in point #2 has a post on just this topic.
If you have found this response helpful or it has answered your question, please mark it as such so that others can find the answer quickly.
Tableau Deployment Advisor
1 of 1 people found this helpful
Aqua, you use Custom SQL to create extracts and publish them.
Once there, you can't use SQL to read them.
This is no possible.
Thanks a lot for your feedback.
We try as best we can to indeed not use custom SQL. However for some cases the data we need cannot be easily obtained with the Tableau functions and we need to use the custom SQL code.
With regards to your 3rd point, this is exactly what we are trying to achieve. We would like to put our tables on the data source Server and then query them.