Vlad Horsun wrote:

>
> User, even very experienced, can't prognose such things as number of
> fetches (or page reads). Statement execution time however is usually
> known to him. At least he can say for sure about upper time limit after
> which statement execution must be stopped.

The kind of user who knows what to expect from a statement doesn't write
statements that use unreasonable amounts of system resources. A
solution that relies on fools recognizing their own foolishness is not
going to succeed.

And, of course, gbak executes a single statement to retrieve all the
data from a table - a system wide setting will cause backups to fail.
And no, it's not a good idea to put in a special switch that lets gbak
ignore the system rules.


Regards,


Ann