March 19, 2004 at 5:01 pm
After many expansion steps, we have still hit bottlenecks in our installation of SQL Server 2000. We are running the standard version on some pretty nicely powered machines with multiple processors, large amounts of memory and large powervault disk arrays with terabytes of storage space. We still run into bottlenecks due to the massive amounts of data we move through our servers on a daily basis. Can anyone here tell me when they gave up on the standard version of SQL 2000 and moved on to Enterprise. What are the signs that no more tweaking is going to work? I know this question is kinda vague but I am just reaching for straws here. I want someone to tell me that they have run massive multi server installations on standard and not had any problems. If you call your local MS rep, right away they tell you "You need to move to Enterprise" as soon as you tell them you have one 25 million record table. Any help in this matter would be greatly appreciated.
Rick
March 22, 2004 at 11:46 am
I can't help specifically, but will offer an opinion.
There is very little difference in the engine between Std and EE. Except for EE's ability to support more memory, and processors.
The size of tables should have little effect, except as noted above.
So if you are CPU or Memory constraint, EE might be the direction to take.
KlK
March 22, 2004 at 12:23 pm
Agree. If you need to add procesors and/or memory and it exceeds the permited in the standard edition, then you should upgrade.
March 22, 2004 at 7:19 pm
If you have more than 4 processors or 2 GB of RAM then you need EE to take advantage of the hardware. However 25 million records isn't that much. I have more than 50 million records in 5 call center databases (combined) which are queried together running on 2 500 PII Xeons and 1 GB of ram. Runs quite well. But my records may not be as wide as yours.
Take a look around MS SQL Site
and this might be helpfull
http://www.microsoft.com/sql/evaluation/overview/default.asp
Viewing 4 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply