DBohner-(db)
Legendary Poster
FINALLY!! - I trapped a user into telling me how they killed the Video Star... Blue Squirrel ... I mean Froze Production....
For too long, we've had this random production crash - and haven't been able to identify what Application was cause an 'Out of Memory' heap crash on one of our web servers.
Today, I had a confession from one of my SME(s) - when he texted me and said he thought he killed a test environment. I am able to replicate the Killing Process - but I don't know how to keep it from reoccurring.
Basically:
- Custom Application over Customer Master
- If the ">|" Go To End is pressed, the application tries to load more rows than my family has fingers and toes.
- If the user is paying attention - they can try to push the "Stop and view results" button (but no user ever pays attention, right?)
* even if they do happen to push the button - the query may decide it wants to continue, anyway...
Workarounds:
- I can FORCE some form of limiting Data Selection - or disallow the Find until the do (klunkie and irritating)
Isn't there something that can do a pre-fetch, and respond back that "The Holy-Monster of Queries Is About To Happen, Are You Sure You Want To Continue"....
I want a weekend...
(db)
For too long, we've had this random production crash - and haven't been able to identify what Application was cause an 'Out of Memory' heap crash on one of our web servers.
Today, I had a confession from one of my SME(s) - when he texted me and said he thought he killed a test environment. I am able to replicate the Killing Process - but I don't know how to keep it from reoccurring.
Basically:
- Custom Application over Customer Master
- If the ">|" Go To End is pressed, the application tries to load more rows than my family has fingers and toes.
- If the user is paying attention - they can try to push the "Stop and view results" button (but no user ever pays attention, right?)
* even if they do happen to push the button - the query may decide it wants to continue, anyway...
Workarounds:
- I can FORCE some form of limiting Data Selection - or disallow the Find until the do (klunkie and irritating)
Isn't there something that can do a pre-fetch, and respond back that "The Holy-Monster of Queries Is About To Happen, Are You Sure You Want To Continue"....
I want a weekend...
(db)