What would happen if you did a server upgrade say from 2017 to 2018 and some files were still checked out?
I would highly recommend that there are no checked out files when you do the upgrade. Why risk it? We have done upgrades with files checked out yet without issue (but I never liked doing it, and I always made sure my files were checked in).
That being said, starting weeks before I started the upgrade, I always notified all users that the update was coming. I then told them what day the upgrade was going to happen. And I told them that they should check in all files because there is always a chance that there will be issues with those checked out files after the upgrade (and any of their work might be lost). I made it perfectly clear to them that if there was an issue it was their problem and not mine and they would need to recreate any lost data themselves. Then I went ahead and did the upgrade as scheduled.
I've always had everyone check files in. Just curious what would happen if a few got missed.
I have had users who wouldn't check in files and left on vacation but the upgrade had to happen. Nothing went wrong with those files and after returning to the office after the upgrade, they were able to check those files in without an issue.
Believe in The Q!
The worst case scenario is that if the local PDM client upgrade went sideways.
If that happens, the end user would have to recreate the local vault view. It's possible to save the checked out/changed files and get them back into the new local vault view but it's time consuming and tedious. Having all the users check in the files before upgrade sidesteps that possibility. The reality is that the server and database really don't care.
While it is desirable to have everyone check in their files, we've never had that happen in ten years despite weeks of sending out reminders. Never had a problem. However, I'm not going to take responsibility if someone takes my advice and it goes sideways.
Retrieving data ...