I wouldn't be concerned about the number of rows or the size of the
database. My concern would be in ensuring that my hardware can provide the
space to backup the database and test restore it. Sounds like you'll need
some considerable disk real estate to achieve this.
Numbers of records - no sweat

Alan

-----Original Message-----
From: Svein Erling Tysvaer
[mailto:svein.erling.tysvaer@...]
Sent: Wednesday, 11 December 2002 7:39 PM
To: ib-support@yahoogroups.com
Subject: Re: [ib-support] Re: time series and FB/IB


I would expect Fb/IB to handle such a table (it is nowhere near 2^64, it is
even below 2^32), but I have no experience with anything that size.

Set

At 14:56 10.12.2002 +0000, you wrote:

>I'll try both aproaches and will see the results.
>Another question which comes to my mind is this data table structure:
>
>pk integer,
>series_id integer, (FK)
>time timestamp,
>value double precision
>
>This would result in table with 350 000 000 rows and very fast
>growing (45 000 000 row/year). Can FB/IB handle such tables?

To unsubscribe from this group, send an email to:
ib-support-unsubscribe@egroups.com



Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/