Looking to get a feel of what other DBAs are doing. Need some feedback to confirm or deny my expectations.
My company is looking to out source the DBA group (3) and others. We will have the opportunity to go with the new company or stay. The separation of duties have fallen into "Operations" and "Applications". Basically, the new company will take over all hardware (server/network/san) and on the operations side the job will be backups, promotions, performance monitoring, service packs, installations, ect. On the application side, know the schema's, help developers write efficient code, tune. What it looks like to me is a "DBA" role and a "Database Developer role". Mainly because the new company will not allow admin access to any piece of HW or SW that they take over. Management is touting this is also popper "separation of duties". And a Gartner consultant is telling management that this is how it is done now and the only way to have speration of duties with promotions. I don't agree. Both SOX and SCC state that separation of duties means that the creator of a database object should not be promoting the object. If one DBA creates an object, they can't promote it. We have approvals and paper trails on all promotions from Dev to Stage to UAT to Prod.
My objective is to keep my team together. I am countering management that make all of us be "new" DBA and let us continue to work on everything we are doing. Not to have this "Operations" VS "Application" DBA roles.
So, with those with 2 or more DBAs. Anybody doing this? any one out there have "production DBA" and "development DBA"? Any one have "Operation" VS "Application" dba?