Hello, in my opinion it's an evolution and not a revolution, from what I know, it's better to wait for the Sp4 and 5 versions in order to limit the bugs... otherwise an installation lasts on average an hour I think because it's better to uninstall everything and do a clean reinstall, then, update the files but all this is done well, and little risk of losing the data we have!
If you decide to do it, NORMALLY, it's not a problem. Depending on the number of machines concerned, you can migrate one, duplicate your database and do a test (be careful to isolate the test machine, once a file is saved with the new version, you can't go back)
In my previous company, we changed every 2 years by taking the SP5 version (latest) to avoid the bugs of the 1st packs, I think it's a good compromise for a use that does not require any latest evolutions.
After that, you also have to ask yourself the question of upgrading the files in the database because the best thing to do is to switch all the files back to the new version to optimize the opening and recording times. A Visiativ consultant came to manage this upgrade of the EPDM database using a mill that extracts the file, opens it and saves it in the new version for each of the SolidWorks files. There is the UpdateVersion tool of myCADtools that can do this but it must be a problem for files archived in the EPDM.
It makes me think that we are still in 2017SP4.1, we should move to SP5 anyway...
Subsidiary question: when you only switch to an SP (2017SP4.1 to SP5), what is the manipulation? Just install the new version downloaded from the SolidWorks site (no uninstallation or anything else)? What about the other workstations, you have to update each one or is it possible to install on all of them at the same time? No particular manipulation related to EPDM?
Change of SP: - if you have time and the media, uninstall the old one and do a new install directly to the right SP - If not, install the loaded version. Manipulation to be done on each station individually (I don't think the fixed/floating license nuance plays a role at this level).