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.
> -----Original Message----- > From: Steven Critchfield [mailto:[EMAIL PROTECTED] > 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. _______________________________________________ Asterisk-Users mailing list [email protected] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
