How to set up the right policies to query the DB Production

Hi expert,
I'd like to hear your comments on how to put in place a good policy to query the database of Production.
We have a group of developers to report that sometimes run report against Production and took about 3 hours and almost consuming 100% of CPU.
I need to put in place a policy of good but not ridiculous for this.

My senior DBA insist on limiting the time as no more than 5 minutes, which I disagree. I think time is not a matter as long as it is not breaking the system. However, our developers in my opinion have a knowledge of Oracle. This is why we must put in place a policy which is good and easy to be digested by them. I think it is the reason for my senior DBA to take the shortcut of plan for the application of the limit of 5 minutes for the query.

any input and comments are appreciated. Thank you

There is a very simple strategy, which can be implemented rightaway:

Developers should not be near any system of production, and no test code should be run on a production database.
You simply implement the Production, acceptance, Test strategy, where acceptance is hosting a realistic production as a version of the database.
If it works on the database of acceptance, it can be run on production.

Involve other correct strategies
-limit the amount of time processor
-limit the amount of disk i/o
etc., using profiles
This means that the session is disconnected, once a limit is exceeded.

The Resource Manager using Oracle is a different option, which will allow the list of unwanted users at a lower priority, but it is an additional burden.

Finally, "developers" are the only virus against no scan anti-virus software to protect your server.
Make sure you only keep the!

----------
Sybrand Bakker
Senior Oracle DBA

Tags: Database

Similar Questions

Maybe you are looking for