Insufficient memory for this operation

rbuser

I'm currently evaluating RBServer, and I'm running into the following
error message:

"Server Error: Processing request for report Report
Forms\Customers\Customer List EDBEngineError, Insufficient memory
for this operation Alias: Database1."

I'm using "Demos\Clients\03. Client Report Catalog\02. Dynamic List" as
the client, and "Demos\Servers\02. Volume Types\01. Reports in Delphi
Forms" as the server.

The error occurs when I start 6 - 10 instances of the client and preview
a report in each. The above error is reported by the client and
"TrsServer - Fatal Exception" is reported by the server.

Any ideas on what's causing this, or how to resolve it?

Thanks,

Ed Vander Hoek

rbuser

"Ed Vander Hoek" wrote in message

rbuser

Marvelous, that did the trick. Thanks for the fast response, Mike.

Ed.

nardmoseley

-----------------------------------------------
Tech Tip: RB Server and the BDE
-----------------------------------------------

Question
--------

Why do I get the following error when accessing my report server with
several clients: "EDBEngineError, Insufficient memory for this
operation"?


Answer:
-------

For simplicity, the RB Server demos use the BDE and paradox tables.

However, in actual use, the BDE is a poor choice for multi-thread server
applications. If you search Google Groups you can find many references
to this topic.

The BDE's legacy architecture was never designed to support running many
concurrent sessions on a single machine. Each BDE session requires too
much memory overhead. Depending upon your machine's resources and the
configuration of the BDE you will eventually run out memory when too
many client sessions are created on the server.


A note about scale ability:
--------------------------

RB Server is highly optimized on the server side, the client side, and
the web tier. However, you still need strong hardware, strong database
performance, etc. Any weak link can become the bottleneck. RB Server and
most database server software can take advantage of multiple CPU's.
Running the database server software on a separate machine is also an
option, as is building a farm of report servers that the WebTier can
utilize to load balance request across several machines.

rbuser

Nard Moseley (Digital Metaphors) wrote:


Thanks for the reference. I'll look into using dbExpress.