I would be happy just being able to lock them out of production (read-only access). I'm trying to run uphill into a 100mph headwind. WGB -----Original Message----- From: Goulet, Richard [mailto:Richard.Goulet@xxxxxxxxxxx] Sent: Wednesday, December 16, 2009 12:49 PM To: Blanchard, William; oracle-l@xxxxxxxxxxxxx Subject: RE: New Survey William, I have no problem with developers having READ ONLY access to production, staging, and QA. It gives them an ability to research problems with the app without always having to bother me. Beyond that no I do not approve of developers having access to anything other than DEV & I like to throw them all out on a monthly basis so that I can "rake out the sandbox". Dick Goulet Senior Oracle DBA/NA Team Lead PAREXEL International -----Original Message----- From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Blanchard, William Sent: Wednesday, December 16, 2009 11:58 AM To: oracle-l@xxxxxxxxxxxxx Subject: New Survey Greetings listers, I am trying to justify locking the developers out of our production database but I need your help. We just moved to a new landscape because the developers had horked up the last one so bad (production/qa/dev were completely out of sync). Please take a minute or two to visit SurveyMonkey and answer the survey I created. http://www.surveymonkey.com/s/LQW738K Thank you, WGB -- //www.freelists.org/webpage/oracle-l - This email and any information, files, or materials transmitted with it are confidential and are solely for the use of the intended recipient. If you have received this email in error, please delete it and notify the sender. -- //www.freelists.org/webpage/oracle-l