I think I've had one in the recent 24 months or so that had an RB2 appx
2.4GB.  Admittedly, it was "ad hoc", f/a set of one-off reports and, as the
source data was new to me and the requirements a bit fluid, had lots of
redundant/un-normalized data.  However, it never failed that I can recall.

Steve in Memphis

----- Original Message ----- 
From: "Bob Simms" <[EMAIL PROTECTED]>
To: "RBASE-L Mailing List" <[EMAIL PROTECTED]>
Sent: Sunday, September 14, 2003 10:21 PM
Subject: [RBASE-L] - Re: Database capacity constraints?


> Frank,
>
> The size limit is 2 GB per file.  Most typically, the limit is
> reached with the RB2 file, that is, the data file, the RB3 file being
> used for the indexes.  This is a hard limit, and when it is exceeded, your
> database pretty much turns into hash.  This has been my experience.
> Oterro won't help with this.
>
> A question for the dream team:  would it be possible to extend the
> capacity of RBASE databases (in, say, version 7.5) by allowing multiple
> RB2, 3, and 4 files for a single database?  The first version of this
> scheme might
> constrain tables to being wholly contained in a single RB2 file.  The RB1
> file would have to
> keep track of which RB2 file contains each table, but after that, I/O
> operations would
> be the same as before, and best of all, no application programming changes
> would be required.
> This could keep users like Frank from having to migrate to some odious
> Brand X database.
>
> . . . Bob S
>
>
> At 11:56 AM 9/15/03, you wrote:
> >Good morning everybody.
> >
> >I developed a system for the NZ Police for criminal profiling in Rbase
6.5+
> >This system is going into its 8th year and was originally written as a
small
> >system in 1994 with Rbase 4.5.
> >
> >The database consists now of 46 tables with 310 fields. We have currently
> >loaded 11,743,000 records. One table contains slightly over 4,000,000
> >records.
> >
> >We tried to add extra data and noticed that the system stops after
loading
> >an additional 470,000 records (approximately).
> >
> >Apart from the fact that this is hindering an important piece of work, we
> >are currently loading an additional 30 - 40,000 records to the database
each
> >month, which implies that we would be running out of space within the
next
> >year.
> >
> >Is there a capacity limit within Rbase? Is Oterro a viable alternative?
Or
> >should we go to something like mySQL and use Rbase as a front end through
> >ODBC?
> >
> >Thanks
> >
> >
> >Frank van der Zwaag
> >
> >
> >____________________________________________________________________
> >CAUTION - This message may contain privileged and confidential
> >information intended only for the use of the addressee named above.
> >If you are not the intended recipient of this message you are hereby
> >notified that any use, dissemination, distribution or reproduction
> >of this message is prohibited. If you have received this message in
> >error please notify Air New Zealand immediately. Any views expressed
> >in this message are those of the individual sender and may not
> >necessarily reflect the views of Air New Zealand.
> >_____________________________________________________________________
> >For more information on the Air New Zealand Group, visit us online
> >at http://www.airnewzealand.com
> >_____________________________________________________________________
>
>
>
> ------------------------------------------------------------
>   Bob Simms
>   Robert A. Simms and Co., Los Angeles
>   818-345-5306 Fax 818-345-5136
>   E-Mail:   mailto:[EMAIL PROTECTED]
>   URL:      http://www.pacificnet.net/simms
> -------------------------------------------------------------
>

Reply via email to