Thanks Kimberly, That is exactly my problem .....
I'd like to investigate this to restrict developers as well .. (yeah I know .... developers have access to production). The most protection level is to drop off developers schema's in production, but we don't want to do that. I'd surely investigate assigning the roles, but NOT making them active, so you can create the session but can't do much. I think I'll follow up this idea for the time being. BTW say I want to identify objects which are accessible to users through more than one role ... what is the quickest way to find out? I think I am writing something, but it is unnecessarily complicated. Any pointers for this will be very helpful. Thanks in advance Raj ______________________________________________________ Rajendra Jamadagni MIS, ESPN Inc. Rajendra dot Jamadagni at ESPN dot com Any opinion expressed here is personal and doesn't reflect that of ESPN Inc. QOTD: Any clod can have facts, but having an opinion is an art!
*********************************************************************2 This e-mail message is confidential, intended only for the named recipient(s) above and may contain information that is privileged, attorney work product or exempt from disclosure under applicable law. If you have received this message in error, or are not the named recipient(s), please immediately notify corporate MIS at (860) 766-2000 and delete this e-mail message from your computer, Thank you. *********************************************************************2
