You mean you don't separate them? Absolutely there needs to be a division of labor here. As a developer I have no time to keep up with mundane tasks as password verification, file resizing and maintenance, upgrades, etc... That doesn't even touch on the security and accountability issues.
In a small shop (< 50 users) you might be able to get away with combining the two roles. But in any shop larger than that, I don't see how you could effectively do both jobs. Gordon J. Glorfield Sr. Applications Developer MAMSI (A UnitedHealth Company) 301-360-8839 [EMAIL PROTECTED] wrote on 12/08/2005 04:28:09 PM: > When we started implementing Sarbanes-Oxley, I knew the question of why we > don't separate the Database Admin role from the Programmer role would come > up. Has anyone on this list been able to provide a satisfactory answer to > the auditors, without spending a lot of time explaining the benefits of an > MV database? > Charlie Rubeor > Unix/Database Administrator > Wiremold/Legrand [snip] This e-mail, including attachments, may include confidential and/or proprietary information, and may be used only by the person or entity to which it is addressed. If the reader of this e-mail is not the intended recipient or his or her authorized agent, the reader is hereby notified that any dissemination, distribution or copying of this e-mail is prohibited. If you have received this e-mail in error, please notify the sender by replying to this message and delete this e-mail immediately. ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
