Suggestions for HUGE DB Design

[Jaunty Edward]

Hi,
I am to make a DB that will handle over a million inserttions every
month. Right Now I am to design it. I was wondering if any of you have
a tutorial or some guide that can talk about the best practices that a
DBA has to folow before he designs the new huge DB.

The DB will be used with ASP and will be online on a Dedicated
webserver in US only.

I will be thankful if anyone can guide me to a tutorial or tell their
own expiriences about such DBs.

Regards
jaunty Edward

[Greg D. Moore \(Strider\)]

"Jaunty Edward" <sm***********@hotpop.com> wrote in message
news:1e**************************@posting.google.c om...

Hi,
I am to make a DB that will handle over a million inserttions every
month.

Ok, unless the insertions are major BLOBs, that's not really huge. I have
one that handles that many an hour.

Right Now I am to design it. I was wondering if any of you have
a tutorial or some guide that can talk about the best practices that a
DBA has to folow before he designs the new huge DB.
Half seriously... learn what a huge DB is. More seriously, MS Press has a
couple of decent books on the subject.

Generally I'd consider a DB huge based on the size. Planning disaster
recovery for a 5 GB is different than a 500GB database.

Also, what are your needs? Is is 24*7? 9-5 operations, etc?

The DB will be used with ASP and will be online on a Dedicated
webserver in US only.
Well, first, make sure it's on hardware separate from the webserver.

Second, put the logs on a separate PHYSICAL set of drives. (not logical,
that won't improve performance much).

Make sure you do decent backups.

Give us more details if you want more help.

I will be thankful if anyone can guide me to a tutorial or tell their
own expiriences about such DBs.
Well, based on the one real comment you made on size, this is a piece of
cake.

You could probably do this on a desktop class machine if you really needed
to (you're talking 2-3 insertions a second).


Regards
jaunty Edward