5 ms·

I run a small one, with little effort other than what comes along with Windows - its our only Windows based system. I would be interesting to know what the pro

by bsg75 11y ago

I run a small one, with little effort other than what comes along with Windows - its our only Windows based system. I would be interesting to know what the problems you have faced are.

EC1 11y ago
I think a better question is what problems they haven't faced.
- tremguy 11y ago
  +1
- untog 11y ago
  This is an extremely frustrating thread to follow. We have some people who have run a Tableau server with no issues, and now two people who are effectively saying "oh, it's awful but I have no interest in telling you why".
  - EC1 11y ago
    I wouldn't even know where to start to be completely honest.
    - recursive 11y ago
      Thanks for your honesty, but I hope you understand that's completely useless. I might have preferred if you lied.
      - EC1 11y ago
        To be completely honest I've never even heard of Tableau.
  - karmawitch 11y ago
    five people telling in detail horror stories that make every other devop feel the pain? (except those seasoned exchange-experts of course) did you ever consider there might be valid reasons some folks prefer *nix based servers?
    - untog 11y ago
      five people telling in detail horror stories that make every other devop feel the pain? Check the timestamps of those messages vs mine. At the time there were only the two responses I mentioned.
      - karmawitch 11y ago
        you have a point there
- bsg75 11y ago
  > I think a better question is what problems they haven't faced. Deploying visualizations without having to develop any HTML or JavaScript code. Publishing to the desktop (Windows or Mac), to the web, to the cloud, or mobile devices (iOS and Android). Publish to the server once, consume on all supported platforms. Deploying a copy of a current site for redundancy, testing or development. Install the app, backup the primary Tableau database with its admin utility (command line), restore it on the new box. All data, visualizations, users and permissions are contained in that single restore step. Tableau means I spend time working with my data, instead of the presentation of it. Its not a perfect product by any measure, and could obviously use some improvements, but is a timesaver in many areas.
click170 11y ago
My experiences are very different. Many Linux services have a concept of reloading. If the config file changes you can send the running program a signal and it will re read the config. This is very useful for production systems. Tableau (9 at least) has no such concept. Change the email address it reports to? Restart tableau. Change the location of the SSL certificates? Restart tableau. Want to apply an update for tableau? Uninstall your current version and install the new one. Oh and until recently when you downloaded the installer for tableau server the file name didn't actually contain the version number. This product was not designed with ops in mind at all. Edit: I forgot, I've actually had a tableau server fill itself up with logs. Tableau has logs in many different locations outside of windows event viewer and doesn't include log rotation facilities for all if them.
- radicalbyte 11y ago
  That sounds like most Enterprise software. It's like that because R&D and Operations never talk; and of course your average Windows Ops person has a poor understanding of operating systems.
- Florin_Andrei 11y ago
  "tabadmin cleanup" helps a little. But yeah, this thing is a mess.
- bsg75 11y ago
  Those things are indeed a pain with Tableau, and also common with a lot of Windows based applications. Never understood why Tableau is either Windows only or has the restart to reconfig issue. Last I looked, it was largely a Tomcat and PostgreSQL based product.
  - click170 11y ago
    [Replied to wrong comment]
- Eridrus 11y ago
  What's the actual issue with restarts? Is the downtime due to a restart unacceptable? Is it that users lose application state when a restart happens? Just trying to understand since I've written software with the same restart to config workflow and would like to understand what causes it to be problematic.
deleted 11y ago
[deleted]

by bsg75 11y ago

I run a small one, with little effort other than what comes along with Windows - its our only Windows based system. I would be interesting to know what the problems you have faced are.

EC1 11y ago

I think a better question is what problems they haven't faced.

tremguy 11y ago
+1
untog 11y ago
This is an extremely frustrating thread to follow. We have some people who have run a Tableau server with no issues, and now two people who are effectively saying "oh, it's awful but I have no interest in telling you why".
- EC1 11y ago
  I wouldn't even know where to start to be completely honest.
  - recursive 11y ago
    Thanks for your honesty, but I hope you understand that's completely useless. I might have preferred if you lied.
    - EC1 11y ago
      To be completely honest I've never even heard of Tableau.
- karmawitch 11y ago
  five people telling in detail horror stories that make every other devop feel the pain? (except those seasoned exchange-experts of course) did you ever consider there might be valid reasons some folks prefer *nix based servers?
  - untog 11y ago
    five people telling in detail horror stories that make every other devop feel the pain? Check the timestamps of those messages vs mine. At the time there were only the two responses I mentioned.
    - karmawitch 11y ago
      you have a point there
bsg75 11y ago
> I think a better question is what problems they haven't faced. Deploying visualizations without having to develop any HTML or JavaScript code. Publishing to the desktop (Windows or Mac), to the web, to the cloud, or mobile devices (iOS and Android). Publish to the server once, consume on all supported platforms. Deploying a copy of a current site for redundancy, testing or development. Install the app, backup the primary Tableau database with its admin utility (command line), restore it on the new box. All data, visualizations, users and permissions are contained in that single restore step. Tableau means I spend time working with my data, instead of the presentation of it. Its not a perfect product by any measure, and could obviously use some improvements, but is a timesaver in many areas.

click170 11y ago

My experiences are very different. Many Linux services have a concept of reloading. If the config file changes you can send the running program a signal and it will re read the config. This is very useful for production systems. Tableau (9 at least) has no such concept. Change the email address it reports to? Restart tableau. Change the location of the SSL certificates? Restart tableau. Want to apply an update for tableau? Uninstall your current version and install the new one. Oh and until recently when you downloaded the installer for tableau server the file name didn't actually contain the version number. This product was not designed with ops in mind at all. Edit: I forgot, I've actually had a tableau server fill itself up with logs. Tableau has logs in many different locations outside of windows event viewer and doesn't include log rotation facilities for all if them.

radicalbyte 11y ago
That sounds like most Enterprise software. It's like that because R&D and Operations never talk; and of course your average Windows Ops person has a poor understanding of operating systems.
Florin_Andrei 11y ago
"tabadmin cleanup" helps a little. But yeah, this thing is a mess.
bsg75 11y ago
Those things are indeed a pain with Tableau, and also common with a lot of Windows based applications. Never understood why Tableau is either Windows only or has the restart to reconfig issue. Last I looked, it was largely a Tomcat and PostgreSQL based product.
- click170 11y ago
  [Replied to wrong comment]
Eridrus 11y ago
What's the actual issue with restarts? Is the downtime due to a restart unacceptable? Is it that users lose application state when a restart happens? Just trying to understand since I've written software with the same restart to config workflow and would like to understand what causes it to be problematic.

deleted 11y ago

[deleted]