Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Temporary Table Resource Limit

354 views
Skip to first unread message

Alain Deschenes

unread,
Dec 5, 2001, 8:03:26 AM12/5/01
to
I am running a local SQL/Link call (single machine) and I get this error
message back "Temporary Table Resource Limit". This didn't happened before
and my client has been running with my system for years.

I thought at first it was the size of the hard-drive. I added a new 60gigs
HD with a bigger one, but I couldn't change the C: drive with it. So C: has
a little 2gigs free and I moved my application to D: (new 60gigs HD) and the
Session.PrivateDir to D:\TEMP.

I've played around with the BDE Config also, here is what I have:

LOW MEMORY USAGE LIMIT=32
MAXBUFSIZE=65535
MAXFILEHANDLES=48
MEMSIZE=128
MINBUFSIZE=128
SHAREDMEMSIZE=4096

I have BDE 5.11 installed there as well.

The data that is query'ed is pretty big too! It works when I do it on
smaller results.

Please I need help!

Alain Deschenes.


Danny Mavromatis

unread,
Dec 6, 2001, 5:26:30 PM12/6/01
to
Alain,

I and many others have had this problem too. You can find out the history of
this problem by typing in the error message to the Google search engine.

Basically, you cannot read more than about 600Mb of data from a query using
the BDE. The BDE seems to always copy the data to a temporary Paradox table
which has this as an upper limit. I've read where you can play around with
BDE settings to control the Paradox version number and temporary table block
sizes etc., but I couldn't get any joy when I tried.

What would have been nice was a query property that said "don't save result
set to a temporary table" but there is no such option. It's just another
example of the BDE showing it's age. I can only suggest you investigate
using other middleware.

Regards,
Danny.

"Alain Deschenes" <adesc...@videotron.ca> wrote in message
news:3c0e1c1e$1_2@dnews...

Patrick Dunford

unread,
Dec 9, 2001, 6:43:10 PM12/9/01
to
In article <3c0fef91$1_1@dnews> in newsgroup borland.public.bde on Fri, 7
Dec 2001 09:26:30 +1100, Danny
Mavromatis(dmavr...@comops.com.au.remove_this) said...

> Alain,
>
> I and many others have had this problem too. You can find out the history of
> this problem by typing in the error message to the Google search engine.
>
> Basically, you cannot read more than about 600Mb of data from a query using
> the BDE. The BDE seems to always copy the data to a temporary Paradox table
> which has this as an upper limit. I've read where you can play around with
> BDE settings to control the Paradox version number and temporary table block
> sizes etc., but I couldn't get any joy when I tried.
>
> What would have been nice was a query property that said "don't save result
> set to a temporary table" but there is no such option. It's just another
> example of the BDE showing it's age. I can only suggest you investigate
> using other middleware.
>
> Regards,
> Danny.

We had a guy in our list in NZ had this problem on Interbase. He was
doing a query of 11 million records, it conked out at 650 MB.

Trevor Stripling

unread,
Dec 19, 2001, 11:13:57 AM12/19/01
to
Does anyone know if Borland has any plans of increasing the Temporary Table
Resource Limit?

Trevor


"Danny Mavromatis" <dmavr...@comops.com.au.remove_this> wrote in message
news:3c0fef91$1_1@dnews...

0 new messages