Subject | Re: problem using backup |
---|---|
Author | Fikret Hasovic |
Post date | 2004-02-04T09:08:24Z |
Hi Helen.
views...
And I think that limit of single table is ~40 Gb...
Will classic perform better than superserver on dual machine? I think
so.
And we have some growth plans, but if you have sugestions, I am
listening...
Fikret Hasovic
TAMP R&D Team
>of
> >Can you, please, give me some advices about firebird.
> >I am not beginer, I am using Interbase since `97. But, since I am
> >planning to use Firebird in one really BIG project (est. 15-18 gig
> >data per year), one table with images stored in blobs (~40kb imagelimit on
> >size).
>
> I'm not clear whether you mean this is going to be a multi-gigabyte
> database consisting of one table. If so, Firebird has an upper
> the size of a single table. I think Nickolay mentioned around 13Gb but my
> memory could be faulty regarding the actual number.Sorry, my fault... DB have ~60 tables, ~30 Stored procedures, ~50
views...
And I think that limit of single table is ~40 Gb...
> >I would like to use Firebird on linux box (SUSE Enterprisedatabases of
> >Server 8), dual P4 2.8G 2 Gig RAM.
> >I think that would be the best to go with classic version, not
> >superserver. What do you think?
>
> Personally I have no experience comparing Classic and SS with
> that size. If confronted with that prospect, I would want to test abenchmark
> typically-sized database under typical production conditions and
> them.store
>
> Linux is a wise choice for the server. I assume your database will
> tax records, so you need this robustness. The database itselfdoesn't care
> whether the server is Classic or SS.Who told you that DB will store tax records?! ;) It's true :)
>
Will classic perform better than superserver on dual machine? I think
so.
> >What else I should know since this is going to be very big db?been using
>
> Obviously, a very big db has to have growth planning, but you've
> IB for a long time so you are aware of that. If you really havedesigned
> the database with only one table, I'd strongly recommend animmediate and
> urgent re-design into a relational model (startingYes, we have normalized our db...
> yesterday). Normalization will be of utmost importance.
>
And we have some growth plans, but if you have sugestions, I am
listening...
> /helenBest regards
Fikret Hasovic
TAMP R&D Team