In theory, yes, but each situation is different - do you have a DB with thin
tables (ie, maybe 2 fields), but 45million records, or one with 25million
blobs? Its highly dependant on your design.

Largest Interbase DB at present (AFAIK) is 200gig, someone in the US I
beleive. Thats according to the web site.

N

--
Nic Wise - [EMAIL PROTECTED] / Inprise/Borland New Zealand
main line: 09.360.0231 / ddi: 09.360.6713 / cell: 021.676.418



> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
> Behalf Of Edward Huang
> Sent: Thursday, 14 September 2000 12:16
> To: Multiple recipients of list delphi
> Subject: RE: [DUG]: Database Size
>
>
> It wouldn't take too long to populate a large database.  I think we could
> have a test some stage after we go further.
>
> But if someone else already use the database with the size we
> required, then
> we could save the testing time, anyway it's quite time consuming task.  I
> think all major database systems should have some figures about how large
> (how far) it can go (with real examples), so save people do the load test
> every time when they want to evaluate a database system.
>
>
>
> > -----Original Message-----
> > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
> > Behalf Of Mark Derricutt
> > Sent: Thursday, 14 September 2000 11:51
> > To: Multiple recipients of list delphi
> > Subject: RE: [DUG]: Database Size
> >
> >
> > On Thu, 14 Sep 2000, Edward Huang wrote:
> >
> > > I'm not worrying about the connections.  The connections I
> want is very
> > > small (10~15), so there should be no problem.  Only problem for
> > our database
> > > is large volume.  The largest two tables could go over 20GB.
> > It's pretty
> > > hard to loadtest this kind of hurge database (take a while to
> create one
> > > database with this size).
> >
> > Out of curiosity how long would it take?  Assuming we have a small
> > app/script which is just sitting there doing INSERT INTO's,
> allowing it to
> > take as much CPU time as it needs?
> >
> > I'm thinking even if it took a week to max out the db and fell
> over at say
> > 19.5gb, it'd be better to know NOW before you have committed clients and
> > live systems to try and solve the problem, I remember awhile ago reading
> > about some EFTPOS/ATM system that was never load tested properly, they
> > went live, then blam - people actually used the system more than they
> > expected and it fell over.  I'd assume the cost of repair down the line
> > would be alot higher than the cost at the start...  plus you
> could take a
> > holiday whilst the db's being populated :)
> >
> > --
> > "We don't guarantee anything except that it will take up disk space..."
> >   Apache 2.0alpha5 Disclaimer
> >
> > Now Playing: <no audio cd present>
> >
> > ------------------------------------------------------------------
> > ---------
> >     New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
> >                   Website: http://www.delphi.org.nz
> > To UnSub, send email to: [EMAIL PROTECTED]
> > with body of "unsubscribe delphi"
> >
>
> ------------------------------------------------------------------
> ---------
>     New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
>                   Website: http://www.delphi.org.nz
> To UnSub, send email to: [EMAIL PROTECTED]
> with body of "unsubscribe delphi"
>

---------------------------------------------------------------------------
    New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
                  Website: http://www.delphi.org.nz
To UnSub, send email to: [EMAIL PROTECTED] 
with body of "unsubscribe delphi"

Reply via email to