Dmitry Yemanov wrote:

>
> Let me suggest you another one. You have an ERP database and some
> applications. The used FB database is quite big and complex. Your users
> create necessary reports in Crystal Reports which connects to the server via
> EasySoft ODBC driver (BDE/dbExpress/whatever else). Our API cancel feature
> is not available for Crystal Reports. But users can easily forget some join
> condition when linking a few huge tables. If this reports implies sorting or
> complex stored procedures, your server is guaranteed to become hard loaded
> for a few hours (or even days).
>
> People often don't have full control over the software they use, so they can
> trust FB server only. And configurable timeouts give them some level of
> protection.

How does the server-side timeout recognize the difference between a
badly-designed Crystal Report that takes forever, and one that is as
good as it can be, is absolutely required, and takes nearly forever?

Regards,


Ann