Home > Archive > microsoft.public.sqlserver.server > June 2002 > SQL sizing





You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author SQL sizing
Niels Meyer

2002-06-25, 6:25 pm

My task is to bring the full company product catalog online (around 6000
items in 10 groups). We've rented a dedicated server and will be developing
within the asp.net framework. We received an offer for our own MS SQL 2000
server but the budget wouldn't allow for it to start with. Instead the
provider offered us a shared solution with one of the following 4 options:

Name Small Medium Large Xtra Large
Diskspace 10 MB 60 MB 250 MB 500 MB
Read/writes 30.000 300.000 1.000.000 20.000.000

Which one should we opt for? We have an average of 600 unique visitors/day
(with a peak of around 1000) and the main traffic on the server relates to
product images (we sell antiques and collectibles). How do we calculate the
approximate load on the SQL server? Could it be an alternative to split the
stocklist into 10 different MS Access databases (I've heard about a
limitation of about 20 simultaneous requests) ?

Any advice would be higly appreciated Niels
Gert-Jan Strik

2002-06-26, 11:25 am

You might want to pick up the book SQL Server Performance Tuning from
Microsoft Press which covers these kinds of issues...

Gert-Jan


Niels Meyer wrote:
>
> My task is to bring the full company product catalog online (around 6000
> items in 10 groups). We've rented a dedicated server and will be developing
> within the asp.net framework. We received an offer for our own MS SQL 2000
> server but the budget wouldn't allow for it to start with. Instead the
> provider offered us a shared solution with one of the following 4 options:
>
> Name Small Medium Large Xtra Large
> Diskspace 10 MB 60 MB 250 MB 500 MB
> Read/writes 30.000 300.000 1.000.000 20.000.000
>
> Which one should we opt for? We have an average of 600 unique visitors/day
> (with a peak of around 1000) and the main traffic on the server relates to
> product images (we sell antiques and collectibles). How do we calculate the
> approximate load on the SQL server? Could it be an alternative to split the
> stocklist into 10 different MS Access databases (I've heard about a
> limitation of about 20 simultaneous requests) ?
>
> Any advice would be higly appreciated Niels

Sponsored Links





Free Braindumps | MCSE braindumps software forum

Copyright 2003 - 2008 examnotes.net