December 5, 2011 at 1:53 pm
The Database Administration group stands alone. The DBA cannot report directly to the manager of software development. This creates a conflict of interest. This alignment allows the manager of development to direct the duties of the DBA. A software manager may desire to bypass change management or override the recommendations of the Database Management team. Tasks and projects need to be discussed rather than assigned.
The Database Administration group should also not be under networking. A Networking Manager typically does not understand enough about databases to accurately plan for projects and tasks.
The database group works WITH all groups and needs to stand alone in the organizational structure reporting to IT Management.
In large meetings, the database group needs accurate representation for proper planning. If they do not stand alone in the org, who will be able to discuss what type of hardware is warranted? DR issues? availability? Scalability? These issues differ dramatically when you are dealing with a file server, mail server or database server.
Certainly the software engineers are NOT qualified to speak on behalf of the database backend.
December 6, 2011 at 12:18 am
That is one of the better comments I have seen on any tech forum. I agree and I appreciate the feedback.
Steve
January 19, 2012 at 2:08 pm
Flavours of DBA? No wonder I felt the strain for many years juggling the Admin side, the dev side AND the BI side! Sometimes my brain melts when I read up a new area of SQL that I've never touched yet seems to be used by everyone.
Viewing 3 posts - 16 through 17 (of 17 total)
You must be logged in to reply to this topic. Login to reply