LOL. The software we write has a lot of role-based security on certain tables. Tables that users (well, the application that they're domain user is logged into) need to be able to see (ie SELECT), but not alter (ie INSERT, UPDATE, DELETE).
I do spatial application DBA (GIS) stuff. A customer of ours has a third-party DBA who granted them (the customer) the ability to assign permissions/roles etc and apparently was experimenting IN PRODUCTION and totally fucked the system...
As a DBA, I'm normally pretty accommodating to people who want to see data or need access to data dictionaries to do work (like program against things), but this was ridiculous!
Database administration is the Bodybuilding of the IT world. You want to build the biggest, strongest, most tuned database you can and have as many people use it (see it) as possible. To do that takes time, constant maintenance, adjustment (performance tuning), and minimizing the fat (extra fields, tables, etc). If you let it go, it gets slow, fat, and sluggish. If you don't give it enough beef, it will can not handle the load. LOL.
Biotest-- you need any DBA work?