Skip to Main Content
Spotfire Ideas Portal
Status Future Consideration
Product Spotfire
Categories Installation
Created by Guest
Created on Feb 6, 2016

Clearer recommended, tested and documented robust upgrade and migration paths

The problem is that there is a lack of solid boundaries around the upgrade process. The product allows you to "upgrade" a few different ways. You can either directly upgrade using the documented procedure, or you can do a clean install of a newer version of Spotfire and then migrate your Library objects and configure your new server accordingly.

A clearer understanding of all the possible ways to upgrade, their pros and cons, and their proper usage (when to use one procedure vs. another) is needed. The recommended upgrade and/or migration procedures also needs to be robust and handle possible failures along the way in such a way that downtime for end-users is kept to a minimum. 

  • Attach files
  • Guest
    Apr 16, 2016

    I'd also add that a SWOT analysis for each new release would be great. Of course there is the what's new documentation but we can go further. The idea is to provide argument to upgrade. Many are still reluctant to change.