Ann,

> > 1) Quotas are NOT a replacement for on-demand request cancelling,

they

> > are different, although related, features appropriate for different
> > use cases.
>
> Granted - but I'd need to hear from somebody with a real application
> that could be improved by quotas. I can certainly imagine situations
> where quotas make managing an application more difficult, so I need a
> very concrete reason to go there - not just because we can.

I need it!

My application lets users create filter/select criteria using any of 50+
conditions, some of which involve join criteria, some of which involve
extended date ranges (like years). I have absolutely no control on the
manner in which they may want to construct the filter criteria -- the
user gets to ask the questions.

I cannot allow for a query to run without end -- period. This is not
something that the client software should implicit have to care about.

Further, there is the problem with the client disconnect logic -- I saw
it just this week -- where I had a FB Server process run for over **200
hours** when there was no one/process connected to the database engine.
So the engine needs a 'governor' function (controllable, granted) --
period.


Sean