4 ms·
A recent client of mine dealt with this by buying dedicated laptops to run Tableau on, when you needed to use it you just tracked down one of them. Seems like
by femto113 11y ago
A recent client of mine dealt with this by buying dedicated laptops to run Tableau on, when you needed to use it you just tracked down one of them. Seems like there should be a rule of thumb around this--software licenses should not be so expensive or inflexible that it's cheaper to buy a dedicated $1000 piece of shareable hardware than to get one for each user.
- CamperBob2 11y agoWhat keeps you from running Tableau in a VM that any number of people can open independently?
- infinite8s 11y agoI'm pretty sure that's against their license terms.
- nevi-me 11y agoYes, and they do actively monitor usage patterns.
- nevi-me 11y agoInteresting approach! How practical is it though? I can export a tbwx or whatever the extension is, so that those who need the dashboards can use Tableau Reader. I'm however wondering if such model would work for us. The one thing that I like about Tableau is that its documents are XML, which plays nice with git.
- femto113 11y agoIt seemed to work reasonably well since the typical user was only needing it an hour or two each week. All of those users needed some authoring ability so Reader wasn't a solution in this case.
- infinite8s 11y agoAren't their data extracts (TDEs) binary files?
- nevi-me 11y agoExtracts are binary yes. If you're using a workbook without extracts embedded, you're working with an XML file. We do that most of the time. We only embed extracts when someone with a Tableau Reader license needs to use a dashboard. We normally keep those out of source control.