User on test DB, "Response time is terrible."
DBA, "You are the only user on the DB, but you have a dozen sessions open. Can you close some sessions?"
User, "I can't see my sessions through the application. Bounce the database"
DBA, " I can see the sessions just fine. I'll kill your excess sessions."
User, "No, don't kill my sessions. Bounce the database. I'm bouncing the database."
We don't need no stinking controls around here.
Everyone can do everything.
He bounced the database.
User, "I bounced the database. My [one] session is running just fine."
Q.E.D. - bouncing the database improves performance.
==========================================================
An update to the post above:
The same user has informed me that I should always shutdown the database with "Shutdown abort" . "It works much better."
I have always assumed that everyone else knows more than I do.
Maybe that isn't true. Maybe I do understand more than some people...
2 comments:
One day something is going to go horribly wrong because whatever application is being develpped here is going to be designed to run with a user account with DBA privileges. When it does its going to be you're fault, if users can shutdown the database they can delete datafiles etc.
Chris, You are SO right. On the other hand, if I remove DBA privileges, many hidden things in the system will break.
Post a Comment