[Asterisk-Users] OT: Best DB

[Steven Critchfield]

On Thu, 2005-03-10 at 08:57 -0600, Jay Milk wrote:
> IB/FB stores the DB in one file, but the file can span multiple drives
> if needed.  However, you can't select which table goes into which file.
> Personally, I don't think that's very feasible, nor is it required -- if
> a table is accessed often enough to be mission critical, large parts of
> it will reside in memory due to caching anyway.

Maybe I work in an odd environment where writes(updates and inserts) are
probably equal to or more than the reads. Caching isn't real helpful at
making the data get to disk faster. Caching helps for reads only.

I'll admit I haven't had to use this feature yet, but I see where some
people could really need it.  

> > -----Original Message-----
> > From: Steven Critchfield [mailto:critch at basesys.com] 
> > Sent: Thursday, March 10, 2005 1:00 AM
> > To: Asterisk Users Mailing List - Non-Commercial Discussion
> > Subject: RE: [Asterisk-Users] OT: Best DB
> > 
> > If it stores the entire DB in 1 file, it can not scale as 
> > well as other DBs. Postgres 8 supports splitting a single DB 
> > up so you can put portions of it on different media if 
> > needed. If you have to tune for absolute speed, you can 
> > purchase one of the solid state drives for the tables that 
> > need that kind of speed while using much less expensive 
> > harddrives for the rest of the DB. While I do not remember 
> > mysql supporting it this directly, I think I remember the 
> > file structure being not to difficult to figure out and split 
> > and symlink back together if need be.

-- 
Steven Critchfield <critch at basesys.com>