To upgrade the vault files or not?

I know it’s customary to upgrade all of your vault files when you go to a new version of SolidWorks, but I got to thinking that maybe that’s not necessary.  Won’t the files simply get updated as used and resaved?  Thoughts, comments, cynicisms?

SolidworksWorkgroup Pdm
Answers 6
SF
SF 2010-02-17 Best Answer

Hello Christine-

One of my clients had these exact same questions. Really, it doesn't really matter, each method is OK.

Here's why they decided to upgrade all their Workgroup PDM files:

  • some files hadn't been opened since 2006, so we upgraded them and archived them too.
  • one of the goals was to eliminate as many errors in the vault files, so upgrading them help here a little
  • upgrading the files was written into their software validation requirements

Devon Sowell

http://www.pdmsolution.com

SF
SF 2010-02-17

In addition to Devon's comments, another benefit of an upgrade is when you open the files (but don't change them).  Each time you open an down version file, SolidWorks gives you all kinds of notifications about it being a down version.

On the flip side, upgrading them may create issues, particularly with files who's history structure is at or near the limits of breaking.  I've seen files come in broken when upgrading them.  However, this isn't nearly the issue it used to be.

Matt Lorono

SolidWorks Legion

Twitter: fcsuper
SF
SF 2010-02-18

Thanks guys, I agree with what you both have said, and I ascertain that it is the client's choice.  Personally, if it was up to me, I think I would leave the files alone in 2009. I’ll leave this open for a bit more comment, but you guys have given me a good feeling that I’m not missing a major red flag. 

SF
SF 2010-02-18

I haven't done mass updates since SW06 to SW07 when I did the batch update of all of our files all the configurations disapeared except the one is use.  This wasn't in a vault and thankfully I had done what is recomended and backed up all the files before doing the update. If a file was opened in SW it was fine but if it was done through the task schedular it broke.

  Since then I just let files get updated durring the natural course of things.

SF
SF 2010-02-19

I also have bad experiences with this from back in the day.  This doesn't seem to be as much of a problem these days, though

Matt Lorono

SolidWorks Legion

Twitter: fcsuper

SF
SF 2010-02-20

When upgrading to both 2009 and then 2010, our PDMW based setup suffered SERIOUS performance issues until we fully converted all files via Task Scheduler. At first, we were clueless to the cause of the sluggish behaviour but soon realised the reason after converting all files (part, asembly and drawings). Our VAR also confirmed that this was a likely reason based on their own experience. Maybe it was just the nature of our network setup, but this is pretty much a given for every upgrade we will do from now on.