6 Replies Latest reply on Nov 11, 2014 5:43 AM by Russell Abraham

    EPDM Speed

    Russell Abraham

      We initially installed EPDM in June 2012 after changing from DBWorks. The difference in speed of opening files for the normal viewer was vastly improved.

      Over the interviening 2 years the system slowed down drastically. To the point where users some times get 3, 4 or even more copies of a drawing to open because they have double clicked the file so many times as the is no indication that anything is happening. We are talking minutes here not a few seconds.

      We upgraded to 2013 SP5 in April this year. Our VAR had suggested that we upgrade to this as it would speed things up. They actually wanted us to upgrade to 2014 but due to other organisational demands we couldn't do this.

      Currently we have 2 large assemblies (large for us approx 2600 parts) that when one specific engineer opens it it will take approx 4-5 mins. If anyone else opens it it takes approx 90 seconds. Then when he saves it every other engineer (9 of us) groans because the system just stops. This can sometimes take up to 20 minutes to correct itself.

       

      Has anyone else experienced issues similar to this and if so how did they overcome them?

        • Re: EPDM Speed
          Richard Bremmer

          Hi Russell,

           

          Do you have a SQL admin? If not you should check the SQL server and at the very least read the last chapter of the EPDM installation guide:

          C:\Program Files\SolidWorks Enterprise PDM\Lang\GB\Installation Guide.pdf

          Read the part about the transaction log. You should also be making backups of the database (not the entire OS as some IT admins like to do).

          And there is a lot more maintenance to be done to a SQL server. Start a search on my.SolidWorks.com and you will find many solutions, S-059700 and S-066203 should cover the basics.

            • Re: EPDM Speed
              Russell Abraham

              Hi Richard,

               

              Strictly speaking we don't have an SQL admin. In theory it is done by our IT team. I am the EPDM admin but I am not allowed access to the server to make any changes to SQL.

              Our VAR moved the transaction log on to a different disk and changed its max size which made no discernable difference to the speed.

              The SQL is configured to do a backup on a daily basis which is then stored on the IT backups.

              Our VAR also set up the maintenance stuff but I can't remember exactly what was included.

                • Re: EPDM Speed
                  Jason Kerns

                  Like any Microsoft product, SQL requires some occasional maintenance. Tim Kwong, SolidWorks Sr. Technical Support Engineer, recommends this schedule:

                  Daily:

                  • Preform backups of the SQL database (and log file if using Full Recovery Mode)
                  • If using the SQL backup feature, offload the backup from the SQL server

                    Weekly or Monthly: 

                  • Rebuild the SQL indexes using SQL Maintenance Plan Wizard
                  • Review the MDF and LDF files to make sure they haven’t exceeded the initial sizes
                  • Defrag the SQL drives

                    Quarterly: 

                  • Check the integrity of the SQL backup by restoring and testing a recent database backup on a test setup
              • Re: EPDM Speed
                Russell Abraham

                Thanks gents for the useful info. I will give some of the a go and see if it has any effect and report back.

                • Re: EPDM Speed
                  Russell Abraham

                  After having had our VAR and SolidWorks look at the system it looks like there is an issue with the archive server.

                  It appears that as we use Windows authentification and have changed domains last year this has had a strange effect.

                  In the archive server it goes to the active directory to get the user details and then stores it. It doesn't then clear out any old information. In one instance it has the user in twice with 2 different domain names and 2 different naming conventions.

                  We are slowly getting to the bottom of it but it has been a long and frustrating process :-(