Although I’m not on the team that maintains the Tableau Servers, the indication I get (and I could be wrong, so please correct me if so) is that backwards compatibility is problematic. The client and server versions must be in lockstep. If you are using Tableau Desktop with Tableau Server, the versions are important. It’s a simple drag-and-drop app, which is easy to do. The Tableau Desktop installer itself can be publicly downloaded (and AutoPkg recipes exist). This blog post will talk about the methods we use of deploying and licensing the Tableau Desktop software for Professional use with Server. I’ve been told by other users that using Tableau Desktop without Server is much simpler, as users merely have to put in the license number and It Just Works™. ![]() We deploy Tableau Desktop to connect with Tableau Server. Enough EditorializingĪs of writing time, the version of Tableau Desktop we are deploying is 9.3.0. Because Tableau doesn’t really make this easy. Since our users want it, however, we have to deploy it.Īnd that’s why I’m sad. I’ll trust them that the software does what they want and has many important features, but it’s not something I use personally. It’s expensive software – $2000 a seat for the Professional version that connects to their Tableau Server product. The data scientists here love it, and many of its users tell me the software is great. One such vendor here is Tableau, a data visualization and dashboard engine. The horrible bitter truth is that enterprise vendors are just as terrible at large-scale deployment as educational software vendors, except they cost more and somehow listen less. In a shining example of naive optimism, I walked into the doors of Facebook expecting relationships with great software vendors, who listen to feedback, work with companies to develop deployment methods, and do cool things to make it easy to use their software that I couldn’t even have imagined.
0 Comments
Leave a Reply. |