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.
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.
Like any Microsoft product, SQL requires some occasional maintenance. Tim Kwong, SolidWorks Sr. Technical Support Engineer, recommends this schedule:
- 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
- Check the integrity of the SQL backup by restoring and testing a recent database backup on a test setup
Rebuilding the SQL indexes weekly has helped out at. few sites that I know of.
Thanks gents for the useful info. I will give some of the a go and see if it has any effect and report back.
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 :-(