george sibbald (1/3/2014)
....a lot of posts talk about devs and dba working on the same team, whether that is possible will depend on the size of the organisation, the larger it is the more likely skills will be siloed and the DBAs more focused on production support than say code reviews. ......
While I have observed the same thing, I also have observed that this pushing of skills into silos is a huge contributor to the problem. In fact, it could be the root of the problem. It naturally pits the "sides" against each other since you look out for your own team. It externalizes the problems of the "other" guy. In this scenario if the DBA does (or allows) something that benefits the Developers at the cost of the DBAs, then said DBA is a traitor to the team. Putting them on the same team makes it sharing the pain. Neither wants to be an undue burden to the other.
Having a team of DBAs, a team of Developers, and a Support team leads to three way fighting. Common practice doesn't make it right, or even good.