We sometimes have an issue with impatient users clicking RUN on their report when they don't think the results are appearing fast enough ("Hmm, seems to be slow, maybe submitting it again will help it speed up").

Will Queuing (specifically the Queue_Max_user_conns setting) help this situation by disallowing them from hitting Run more than a specified number of times?

- ABT

This message has been edited. Last edited by: Kerry,

Having the option "Queue_Max_user_conns" will not solve your problem, it only put in queing the run request of a user where the number of request exceed the value set to option "max_connections_per_user".

Per exemple, in my case I have "max_connections_per_user" set at 1 and "Queue_Max_user_conns" to "Y", so a user cannot have more than one deferred request running at the same time but will have other request in the queue. But they will all run one after the other...

I don't know any solution to avoid a user to press multiple time the run button and nor solution to avoid impatient users :-)

Hi ABT,

Here is suggestion from our technicals: when it queues the user, it will go into that pool of (total maximum number of queued connection). That is, there is no distinction (during queuing) that this person should not submit any more jobs. Potentially you can now fill up the queue with repeated requests.

Cheers,

Kerry

Kerry, I was actually after the exact opposite. I was being a bit sarcastic about my users and their thought process.

Do the technicals have any suggestions about preventing users from repeatedly clicking Run/Submit? My users would be using MRE via a BID.

- ABT

No idea if this is going to be possible at all, just a thought ...
After clicking the submit button, could it perhaps be possible to grey the submit button (or make in invisible) before actually submitting the request? If that's possible to do, then the user simply cannot click twice.

GamP,
These are plain old auto prompting pages. I was thinking this would have to be done at a coding level, like write a record to a DB for the execute, and then read that DB to see if that user has executed that program within a defined period of time. If so, they are rerunning and prevent it. If not, let it pass.

Wondering what IBI had out of the box to prevent this? Resource Governor?

One of the other forum sites I visit has a feature preventing non-logged in users from searching but every 15 seconds. Conceptually, I know its possible, just the difference in 'off the shelf' and 'roll your own'.

- ABT

This message has been edited. Last edited by: ABT,