I'm not DBA at least not as usually is understood by DBA. I'm almost
always worked in the development side between big ocean of customers
and developers ;) But we have reached mutual agreement with our
customer that for rather dynamic and many joins including search we
will use these restrictions and our app will show users a "user
friendly" message something like "resource usage exceeded give
something else". Of course we will log these cases and either we or
customer will be able to analyze such queries later. Fortunately our
customer is advanced enough to understand that resources are finite
and all combinations of ~15 search parameters cannot be tested in a
resonable time ;)
2006/3/14, Ethan Post <post.ethan_at_gmail.com>:
> Be aware you are more likely going to come across as an unreasonable DBA.
> Better to monitor for long running queries and when you find one find out
> who, what, when and why before you shoot.
>
--
http://www.freelists.org/webpage/oracle-l
Received on Tue Mar 14 2006 - 14:30:25 CST
