It seems that Mordac has discovered that I have the ability to log into SLX as admin using the admin's password, and as such can still perform my job duties.  He'd like to put a stop to this ("in a perfect world, no one would be able to do anything"). 

 Over the years, I have heard that there "are things" that must be done as admin.  Does anyone have a list of such "things" that can't be done by users who are granted some of the admin's abilities through Administrative Roles?

Also, I use DTS packages with the SLX provider to do some mass updates.  The IT gods would also like to remove my ability to update the SLX database outside of the application.  I currently (as the Siebel admin) have R/W permisssions on the database. Not sure how to alow me to update things using DTS if I don't.....???

What, me worry?

If you can't update some stuff or run integrity checker or cut remote databases and work in the SLX Architect to clean up Groups who cares? You just point to that Guardians of the Deep and have them either give you permissions to accomplish corporate goals or start going above them and point at your email requests and their denials for permissions.

I'm reminded of a time that an overzealous DBA trying to conserve disk space set Oracle MaxExtents on 'big' SLX tables like Account, Contact, Address.....then wondered why the import of accounts\contacts program wasn't storing records...the corporate goal was to work x00 new accounts a day....the DBA's goal was an efficient tight database.....guess who won?