RE: FN-FORUM: dB growth

date posted 22nd September 2006 13:08

Hi,

I've worked on large systems, and would not consider a separate database per
customer. There are other ways to scale out if required rather than just
move databases around. Also, about management reporting across all data...
Sounds messy if you need include data from each database.

Debbie

-----Original Message-----
From: [EMAIL REMOVED] [EMAIL REMOVED] On Behalf Of Gary Short
Sent: 22 September 2006 13:07
To: FN-FORUM / [EMAIL REMOVED]
Subject: RE: FN-FORUM: dB growth


> -----Original Message-----
> From: [EMAIL REMOVED] [EMAIL REMOVED] On Behalf Of Dom
> Latter
> Sent: 22 September 2006 12:54
> To: [EMAIL REMOVED]
> Subject: Re: FN-FORUM: dB growth
>
>
> On Thursday 21 Sep 2006 4:12 pm, Dave Fennell wrote:
>
> > separate databases per customer.
>
> Asked a couple of mates about this last night, one of whom has a
> background in "Big Iron" [1]. He said "no".

I'm surprised to hear that the "Big Iron" guy said that. In the enterprise
scale situation separate databases give you an easy route to scalability.
Too much traffic on the database server? No problem, move customers M - Z to
a new server. Then as you scale, just repeat this binary chop to maintain
database throughput.

Cheers,
Gary
http://www.garyshort.org/



--
Freelancers, contractors earn more with Prosperity4 Call 0870 870 4414 or
visit www.prosperity4.com and benefit from Inland Revenue approved expenses
today.

To advertise here: http://www.freelancers.net/advertising.html