calculating load

SEVRER WORKLOAD PARAMETERS:
can someone suggest me something based on the following parameters given
Q1 How many transactions are expected during the peak hour of activity? How
many transactions are expected each business day?
ANS: 300 concurrent users (max) will connect to application server and based
on the activity application server will call stored procedure stored in the
database server (one at a time). Most of the stored procedure (approx 500)
has single SELECT/UPDATE statement but, around 100 procedures has multiple
SELECT/UPDATE statement inside them (max 8 statement), frequency of calling
these procedures are less compared to the other 500.
Q2 How many database connections are required? From Appln to DB
ANS: How can we check that, will SQL profiler be able to give me this info?
Q3 How much storage should be reserved for the database (data and indexes)?
15 GB of database size is expected.
Q4 Can your application support 2 appln servers talking to one db at back en
d?
ANS: Yes"NewTOPROJECT" <NewTOPROJECT@.discussions.microsoft.com> wrote in message
news:3DF1EF15-D256-4961-881E-68427A184A0B@.microsoft.com...
> SEVRER WORKLOAD PARAMETERS:
> can someone suggest me something based on the following parameters given
>
I suggest you test, there's not nearly enough information to accruately size
the hardware. By the way, no matter how detailed your questionare is, you
will still need to test.
That workload does not appear to be too extreme. 15GB is on the large size
for an OLTP application, and a big wildcard is how expensive your SELECT
statements are. With 15GB of data there is ample opportunity to create very
expensive queries. On the other hand, if the data is largly historical and
you don't do historical reporting during peak load times, your workload may
be quite light.
So throw the profiler on it and watch the Reads and the CPU. The most
expensive 10% of queries may use 90% of your resources, so identify and
optimize these.
David