How Much More Can I Put on This SQL Server?

It depends on kind of db applications you are running,
database design, overall size of databases in GB etc. A
database which is not bulky (for example more than 50gb)
in size, where most tables have a pk, and pre-defined
queries fetch one or few records at a time based on a
unique where condition, you could have few hundreds
simulaneious connections. Whereas in a data warehouse
application where you have really huge tables, users are
allowed to create and run queries as they like, and each
query ususally reads through millions of records, few
simulatneious users can saturate the system, and sometime
even one user can dominate the whole system.
Based on the information you have given, your db server
falls more into the first category, 150 or more
simultaneous users could stress the system. If possible,
you should run a stress test to see when the cpu hits 90%
or more utilization, that will be the saturation point.
i hope this answers your question to some extent. Let us
know if you have further questions.

>--Original Message--
>We have a 4 processor (Xeon 700mhz), 3GB, SQL Server 2000
Standard Edition,
>Win2K Standard, with 3 RAID Array's. Currently running
about 20 databases,
>75 concurrent connections. Performance monitor readings
look good,
>processor rarely goes above 35 percent, memory looks
good, the disk drives
>spike but are usually not too busy.
>My question is how much more can I load on this thing
(ballpark) before it
>starts to get even medium stress. I'm looking for anyone
with a similar
>configuration, with much bigger numbers to get some idea
of how fare I can
>go with this machine. I have looked on www.tpc.org site
and similar
>configurations list 67,000 concurrent users and 87,000
tmp, but that just
>doesn't seem real.
>Thanks for any info.
>Steven Berringer
>
>.
>Thanks for the feedback. I guess I was hoping to hear from someone who had
a similar configuration and had X number of users connected and running at
the same time. I understand the OLTP versus OLAP and good database design,
and all that, but 150 is a far cry from the 67,000 listed on the tpm web
site for a 4 processor box.
Does anyone have any real world stories?
Thanks
Steven
<anonymous@.discussions.microsoft.com> wrote in message
news:1401701c3f7c3$8b5961c0$a501280a@.phx
.gbl...
> It depends on kind of db applications you are running,
> database design, overall size of databases in GB etc. A
> database which is not bulky (for example more than 50gb)
> in size, where most tables have a pk, and pre-defined
> queries fetch one or few records at a time based on a
> unique where condition, you could have few hundreds
> simulaneious connections. Whereas in a data warehouse
> application where you have really huge tables, users are
> allowed to create and run queries as they like, and each
> query ususally reads through millions of records, few
> simulatneious users can saturate the system, and sometime
> even one user can dominate the whole system.
> Based on the information you have given, your db server
> falls more into the first category, 150 or more
> simultaneous users could stress the system. If possible,
> you should run a stress test to see when the cpu hits 90%
> or more utilization, that will be the saturation point.
> i hope this answers your question to some extent. Let us
> know if you have further questions.
>
>
> Standard Edition,
> about 20 databases,
> look good,
> good, the disk drives
> (ballpark) before it
> with a similar
> of how fare I can
> and similar
> tmp, but that just