4 Replies Latest reply on Jan 20, 2009 12:17 PM by Todd Puckett

    Test/Development Environment

      Does anyone have a recommendation for the setup of a PDM test/development environment? I currently have all of the PDMWE components installed on one server, including a "production" vault and a "test" vault. I would like to test the 2009 upgrade process before going live. I would like to be able to test new features and add-ins as well.

      I was thinking of creating the setup on my local machine but I wasn't sure of the implications of that, e.g. licensing, performance, etc. Any suggestions?
        • Test/Development Environment
          Christina Seay
          I was told by our VAR that there is no way to "downgrade" PDM once it's been upgraded. You would have to do a complete reinstall of PDM. So far we haven't had any problems with our add-ins and such after we upgraded... but I didn't have much set up either, so there wasn't a lot that could break.

          I'm not sure about setup on a local machine, perhaps someone else can chime in there on what the impact would be of that.

          Our upgrade process went pretty smooth though. It took significantly longer to backup the database before upgrading than what it did actually performing the upgrade. We set the database backup to run overnight and the upgrade was done and client-machines upgraded within a couple hours.
          • Test/Development Environment
            Todd Puckett
            A test environment will require another server. You will need a copy of the database and the file vault from your production server.

            The test server can be a normal desktop computer but it will need Server 2003 as the OS. You can install all four components on the server (MS SQL Server, Database server, Archive server, Client). I don't think Solidworks will install on a server OS so you will need a seperate computer with the newer client to test the new features. PDMWE clients are not backwards compatable.

            Our upgrade from 2008 to 2009 took about 10 hrs mostly because our vault is 500 Gb.
            • Test/Development Environment
              I use a virtual machine. (vmware) It works out great. I especially like the snap-shot feature of the software; if I break something beyond repair I can just go back to the last working state. (just like system restore.)
                • Test/Development Environment
                  Todd Puckett
                  We used VMware for our last test upgrade. It is a good option as long as you have the spare RAM, disk space, and capable processor(s). In our case the database server uses almost 4 Gb RAM and the upgrade process is very processor intensive.
                  My previous test server was 4 yrs older than our production server and it took almost 2 days to run the test upgrade. An underpowered test server also makes it difficult to test the client perfomance, but this is a good option if you are limited on resourses and all you want is to make sure the upgrade works and check out the new features.