- Dec 27, 2001
- 11,272
- 1
- 0
My experience with SQL has been that it's fairly light. It's installed on my P2 400 at work as just a little extra and has been performing well for some small time web work. Since my company recently moved to a new vendor that uses Access as a front end and SQL Server as a backend, I ordered a server from HP with 2.4 Ghz Xeon 256 RAM and two 80 GB IDE HDs in RAID1. The application performs like an absolute dog. My intention was to add 1 GB Ram, but the server just got here a day before they did and they installed while I was off--I needed to get the exact specs of the RAM before ordering anyway. I assumed we just needed to get the ram, but the vendor is insisting that we need a dual 2.4 Ghz Xeon with 6 SCSI drives for three volumes and 2 GB RAM. Is that typically how much horsepower a SQL Server running under Server 2003 needs to server a couple dozen people with an Access app? They were by far the most emphatic about the SCSI drives.
Anyway, it's out of my hands because they sufficiently spooked my supervisors into the need for this behemoth and my suggestion that a little more RAM would solve things went virtually ignored. I'm just looking for some validation or clarification so I can rest easy about this. Thanks.
Anyway, it's out of my hands because they sufficiently spooked my supervisors into the need for this behemoth and my suggestion that a little more RAM would solve things went virtually ignored. I'm just looking for some validation or clarification so I can rest easy about this. Thanks.