• I like where you are going with this. I work in a small MIS shop supporting a collections center for a large bank. We started using SQL server a couple years ago to replace some of our Access db that outgrew that platform. The management team was of the opinion the SQL server did not need a formal DBA and started building databases as if they were still in Access, each project had its own database and was owned by virtualy all team members. Security is a nightmare, there is very little documentation and we have since built 5 more servers with only a general "idea" of how we would like the environment to look.

    I would like to see this discussion expanded to try and define the various roles involved in building/supporting SQL server applications.

    I'll stop here so this doesn't turn into a rant about my current environment.