Sure... This particular db is really only used for storing blobs (in
our case tiff and pdf images of letters sent, documents received, etc).
It performs fine. We do not back it up with gbak, but instead perform
nightly sweeps.

Our largest database that contains only data records (no blobs at all)
is around 15 GB and also performs really well. We backup/restore with
gbak nightly (it seems to make a big performance difference when
compared to nights when the job doesn't run).

For both sets of databases (we service multiple clients -- each client
has a data db and an image db) we learned the hard way that you better
make sure you are using indexed fields for searching because stuff that
works well in a smaller tables doesn't run so fast when those tables now
have a couple millions records and you are joining them together...
Also we seem to get burned on triggers that update other tables (to
modify status flags) which in turn could update other different tables.
Those also seem to get through our developer testing and SQA testing,
but really cause slow downs in the field as the users start dumping in
100,000 records at a time.

So basically we are happy with our databases because they are cheap to
maintain (we don't have a DBA) and they run really well under linux.

-steve

On Thu, 2005-07-21 at 23:01 +1000, Alan McDonald wrote:

> > Our largest db (multi-file gdb on linux) is around 82 GB.
> >
> > -steve
> >
>
> would you like to titillate us with some of your experiences with a DB
> this
> size?
> Alan
>
>
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> Visit http://firebird.sourceforge.net and click the Resources item
> on the main (top) menu. Try Knowledgebase and FAQ links !
>
> Also search the knowledgebases at http://www.ibphoenix.com
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> Yahoo! Groups Links
>
>
>
>
>
>
>


[Non-text portions of this message have been removed]