Thanks for the answer. I do know the benefits of optimizing extract.
My main concern is:
When you optimized the Extract from desktop and publish the source to Tableau server. Does the server version of the Extract get optimized?
Are you talking about a Published Data Source when you refer to "the server version" of the Extract? If so, I do not know, as I only use embedded extracts within my workbooks.
Yes, you are right. I am talking about the SERVER version of the Extract.
I don't think Tableau has any document on whether an Extract can be optimized in Tableau server. So that when the workbook connects to the server can also enjoy the optimized result.
Il I create the calculated fields before extracting the data (with live SQL server connection), are the calculated fileds included in the extract or do I need to optimise it again?
Matthew Lutton wrote:
An oldie, but a goodie:
Optimizing moves the calculated fields you’ve created into the extract so that they don’t have to be computed locally every time you use them.
Hi, how can I check if the extract has been optimized? When I select the Extract-->Optimize option, the response is immediate, I don't receive any message (via dialog box or similar)
I'm not sure if your Log files would indicate something -- but I agree, it is confusing since there is no confirmation dialog. I just trust that when I've used the option, it has been applied.
Matthew, do you have any metrics that show the difference between a local extract and a server extract? Why do you not like it? The only difference I see on server is that using a server data source goes through the dataserver proxy to get to the tde which is separated upon publishing even for the embedded.
No, it's been a long time since I tested anything with published data sources. I had lots of issues initially, but the product and I have both matured a bit since then (funny my comment above on this was exactly one year old today!)
I can provide more details offline about the struggles I encountered. I did have performance issues, and some other concerns when this feature was initially released. I'm sure some of those issues have been addressed by now.