Yes, I refer to that page as "standard" requirements, but for 4 clients I think is too much: those requirements wants two servers!
I'm asking advices for only one server.
For 4 users, you should be fine with one server.
We have 3 servers (One SQL and two Archive) but we also have 200 licenses installed on over 500 user's.
Our SQL server has:
- 1x Xeon E5540 Quad Core @ 2.53ghz
- 12gb memory (PC3-10700, DDR3, 667mhz)
- Raid 5 SCSI Hard drive (3 drives in Raid) 300GB
Archive servers are similar but with more disk space (500gb Raid 5) and less memory (6gb).
The SQL server is sitting with 8gb of memory currently in use (SQL is using 6.7gb of that). Never really seen go above that. The Archive servers usually have about 1.5gb in use so the 6gb might've been overkill. Since you are using one server for both....you might bump up the memory as its a fairly sheap upgrade.
All run Windows Server 2003 X64
One server should be fine for only 4 clients. If you eventually out grow the setup, you can always add a server later.
We used one server for many years without any problems with 20+ users and 100 Gb of data.
2 things to consider:
- When we turned on the indexing service it uses one core of the processor at all times.
- SQL server 2008 will frequently use more than 8 GB of RAM, I'm sure it would work with less but it can be very memory hungry. Your smaller database may not require as much from SQL. Make sure you get the 64 bit version of MS Server.
Our contract IT guy gave me these specs for another site after managing our single server installation for 6 months.
1 server with:
24 GB RAM
(2) Quad or Six Core CPUs
SAS Hard Drives, 10K or 15K RPM (15k is preferred when possible)
Battery Backed Write Cache on Array Controller, 512MB Min
Array1 - 3x 146 GB HDD (Min.) - RAID5 - C: - OS Volume, Program Files
Array2 - 3x 146 GB HDD (Min.) - RAID5 - E: - SQL Data Volume, Program Files
Array3 - 2x 146 GB HDD (Min.) - RAID1 - F: - Mirror set for SQL transaction logs
Hope this helps.
Are these specs for a server hosting the EPDM archive and database server?
Will this proposed server for your other site be hosting a different vault?
Your IT guy has alloted considerable disk space for items that use very little space.
We have 3 vaults totalling 1 TB on our archive server. Our database server requires less than 70 GB disk space. This includes OS, Program Files, SQL Data files <includes SQL transaction logs> (10GB), index catalog files (15GB) , swap file (10GB).
If this proposed server is only running EPDM database server then it's overkill. Ours rarely uses all 4 processor cores and usually uses between 5 and 8 GB RAM.
If its also running the archive server the drive arrays should be configured to maximize availble space for vault growth.
Array1 - 3x 146 GB HDD (292 GB) - RAID5 - C: - OS Volume, Program Files, SQL Data Volume
Array2 - 5x 146 GB HDD (584 GB) - RAID5 - E: - Archive server data volume.
Thanks for all your answers.
We have only four clients, and about 30Gb of files, so we are trying with the initial specs, except for the memory:
- 1 cpu Xeon E5606 Quad Core; future expansion allowed (to max 2 cpu)
- 12Gb Ram Ecc Cas 9; future expansion allowed
- raid 1+0 HW with hd SAS 15K, 300GB for each one.
- 1 Gb networking
Obviously the initial "experiments" with few drawings seem working fine.
I'll let you know if it will be not enough