I'm assuming that you mean the clients are getting the "out of memory" error
and not the server.
A couple of things:
- Sounds like this application(s) came from a standalone type database
(DBase, Paradox,etc), originally, and was maybe "ported" to a Client Server
(CS) type database, such as what you are using now.
- To be very blunt, it's just crazy to bring 200k ~ 200k records across the
network from the server to the client program just to give the user the
ability to scroll through them all.. There is simply not a person on the
face of the earth that's going to look at that many rows of data.
- In a CS environment, you really need to look at the requirements or needs
and balance that with the amount of data that's retrieved from the server,
for display, and any time.
- If re-writing the application(s) isn't an option, than I would highly
suggest that you at least re-work the SQL such that smaller, much smaller,
usable amounts of data are brought across the wire to the client program at
any time.
It's not the answer that I'm sure you want to hear, but you've really
limited yourself, by the current client application(s) design..

Best regards,
Fred Wilson
SE, Böwe Bell & Howell
fred.wilson@... <mailto:fred.wilson@...>



-----Original Message-----
From: Jason Frey [mailto:jason_frey@...]
Sent: Tuesday, April 01, 2003 1:29 PM
To: ib-support@yahoogroups.com
Subject: [ib-support] IB6.0OE + ~250k records = Out of Memory?


We're receiving some reports from different customers that they're receiving
Out of Memory errors when running our software. We've tracked it down to
appearing like it's related to a table having 200 or 250k records in it.
The table in question has quite a few fields and indexes, so each record is
large. I would say something like "Bad data in the table" but it's
happening in multiple sites, and the data looks clean from the sites we've
gotten it from.
What's more, IBConsole is also getting this error when looking at the data
tab in a table's properties (Originally, the tech guys thought it had
something to do with the BDE, which our application uses (Yes, boo hiss) to
connect to IB.. Then I pointed out that IBConsole doesn't use the BDE and it
was also having this issue, and they said "Oh"). I've seen posts across the
internet saying "Umm.. Yeah.. That happens, don't make huge scrollable
datasets.". I'm wondering if the gurus here know anything more, since the
architecture of this version of our program relies on scrollable table type
access and rewriting it isn't an option. Is increasing page buffers/size
any sort of viable solution to this?
Switching to IBO (Since that's a popular answer to most any problem that's
not strictly SQL) is a possibility, if I can prove that it's solved this
sort of thing before. IE we don't want to take the time to write another
compatiblity layer using the IBO components unless we know, or have a strong
suspicion, that it will fix the problem. But, given that the problem
happens using both BDE and IBX components, I have my doubts about IBO fixing
the problem.
Any help is greatly appreciated.

- Jason



Yahoo! Groups Sponsor

ADVERTISEMENT

<http://rd.yahoo.com/M=246920.2960106.4328965.1728375/D=egroupweb/S=17051153
86:HM/A=1513703/R=0/*http://www.gotomypc.com/u/tr/yh/cpm/grp/300_06F/g22lp?T
arget=mm/g22lp.tmpl>

<http://us.adserver.yahoo.com/l?M=246920.2960106.4328965.1728375/D=egroupmai
l/S=:HM/A=1513703/rand=156530220>

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



Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service
<http://docs.yahoo.com/info/terms/> .




[Non-text portions of this message have been removed]