All the hardware that is used in your EPDM environment is important. But first of all is how you install the EPDM software servers (SQL, DataBase and Archive servers).
I think the best solution is to separate software servers on different virtual or real machines. If is possible separate SQL+Database from Archive server on separate machines. It is important because one is database server and the other one is a file server. The necessary hardware resources are different.
Also try to use the machine with SQL and DataBase server only for this don't install any unnecessary software.
The machine used for archive server can be used also as file server but is better if you can use it only for archive server.
As example we use this kind of installation on virtual servers
SQL+DataBase use 2cores and 8Gb RAM
Archive Server (that also is used as file server) 2 cores 4Gb RAM
Our EPDM archive is about 200Gb and the SQL vault database is about 4 Gb
13 users in 2 different locations with a replicated server
Can you post your ePDM server configuration and specs?
Just for your information and to compare, we have 3 servers:
- One SQL server with 24gb of memory (20gb is currently in use). SQL DB size is about 3.2gb.
- Two replicated file archive servers with 8gb of memory (5gb in use)
- We have 250,000 documents in the system
- The file size total on the archive is around 588gb.
- We have 100 view and 100 edit licenses.
Thanks for everyone's ideas and responses. I should have asked this question after I got back from vacation not before.
Our current server configuration is as follows;
Dell PER720 server running Windows Server 2008 R2, Service pack 1
64 Bit operating system
32GB of ram
Both the File Archive Server and the SQL Server are running on the physical server.
Most of the workstations are connected to the server via a 48 port GB Switch.
The SQL Server is 540MB
The File Archive Vault is 80GB with 173,239 files
Thanks again for everyone's input! Much appreciated.
One thing that hasn't been mentioned. Put all your EPDM users on a dedicated Gigabit subnet on your network.
We have been running PDME since 2007. We started by following recommendations from SW and our VAR, but soon found that it was better to resolve this ourselves. Now we are running the file archive a virtual Win 2008 server, and the SQL server runs on a physical HP BL460C with good specs. The most critical performance factor we have found is the SQL-server. Last year we tried to run the PDME database on a virtual SQL-server, that was a complete disaster.
We just upgraded our infrastructture so that we are running VMWare 5, HP bladeservers (BL460), HP 3Par SAN, Cisco Catalyst for network, and gigabit switches servicing the clients. Also, we just upgraded from SW and PDME 2013 SP5 to 2014 SP4, we NEVER install any earlier releases after our experiences with 2010....
The performance is now satsifactory, even though both SolidWorks and PDME have serious shortcomings regarding the use of CPU-cores, network capability and the disgusting filestructure nesting innumerable small files into a binary tree based on the primitive Microsoft file-system.
We are currently serving 30+ SW users, all running PDME Editor. We hav passed 1.2 million files, and our database is around 5 GB. Unfortunately there are basically no tools to maintain, monitor or measure the actual performance realtime (that we know of).
The smaller the environment, the lesser HW requirements...
Best of luck,
Unfortunately there are basically no tools to maintain, monitor or measure the actual performance realtime (that we know of).
We use Idera to monitor our EPDM SQL Server.
Gb network....don't even consider anything less, + a dedicated server - non virtualised.