It sure seems like thereâ€™s a lot of miscommunication between developers and database specialists. In fact, the communication can become so poor that outright hostility between the groups is common. At the end of the day we are all working towards a common goal, to add value to whatever organization we are working for. It’s a shame that we all lose sight of this commonality and create such a false dichotomy between the groups. I think there are some ways that we, as database specialists, can use to attempt to cross that gap.
Prior to being suborned to the dark side, I was a developer. I had a little over 10 years experience working in VB, Java & C#. I remember, distinctly, cursing our database team for being so problematic about how they did things. They slowed me down. They got in the way. When I had problems they were slow to respond, unless the problems were on production. I know I even instigated a few fights with them in an attempt to get them to move the way I wanted (hard to believe, I know). Then came the day when I shifted over to all database work.
Suddenly, Iâ€™m responsible for making sure the production system stays online and that the data is readily available to the business. Now Iâ€™m slowing down development, because I want a chance to review their design and validate their code to ensure itâ€™ll work well and not affect production. Now Iâ€™m acting as a gatekeeper to prevent unauthorized access to the systems or at least keep people from making any of the 10,001 simple errors that could impact production. Now when a developer wants something fixed in dev, Iâ€™m the guy telling them they have to wait because something in production is wonky. And yeah, Iâ€™ve instigated fights from this side as I tried to get devs to understand that simply delivering code is not enough and that data persistence is there for a reason (again, shocking Iâ€™m sure).
Remember, both of these groups are more right than wrong, and both are working towards that common goal, value for the business. But they really donâ€™t get along. Whatâ€™s more, what they work on and how they work with it is frequently at odds. Ever heard of the object-relational impedance mismatch? How about the concept that you donâ€™t have a database, but a persistence layer? What about managing data integrity within the application (one of my abiding favorites)? Never heard of those terms or concepts? Then youâ€™re probably a database specialist and youâ€™re probably not talking to your developers. If they havenâ€™t already, theyâ€™ll soon be introducing an Object Relational Mapping tool to your enterprise. Best of luck.
A lot of these communication issues probably canâ€™t be solved, but I know of one place where most database specialists are not communicating well with their dev teams, and database guys, itâ€™s your fault. Source Control. Do you think of the structures and procedures within your database as code? You should, because, to a large degree, it is. The Data Definition Language (DDL) calls that make up your tables, views and procedures are code. That code needs to be checked into a source control management system. There, the individual objects can be versioned and managed. There you can create labeled releases of your code. There you can branch your code to create alternate development or support streams that contain variations of your database. There you can merge changes from multiple users and branches into a single main source for deployment to production. There you can keep your database directly in sync with application developers code.
Did you catch that last one? You can become more tightly coupled with your development team. Best of all, you can do this using their tools and their language. This is the communication problem I want you, the database professional to solve. Very few of us database types are using source control these days. This, despite the fact that there are fantastic tools and methods under development from different vendors that directly address the issue of getting and keeping database code within a source control system.
Years ago, when I first made the jump to databases, I was appalled that I couldnâ€™t keep my code in source control. Then, as I worked more and more with databases, despite the problems, I abandoned the idea of managing the code in source because, frankly, it was way too hard. But several years ago new tools appeared on the market to make it possible (if still somewhat painful) to get the database into source control. Iâ€™ve been working that way for years now. It has completely eliminated one of the many problems I used to have with developers. They now know that my code is stored with theirs. That my versions are their versions. That their labels are my labels. That we branch the code together. Itâ€™s taken completely for granted, and we share a common language about change and deployment.
This has not solved every problem or conflict with database teams Iâ€™ve worked with. It has eliminated a source of friction. It has increased communication. Itâ€™s something that I could do, and you can do, to get a little closer to your development team. Not to mention the fact that you will now have your databases in a known state, all the time, that youâ€™ll be deploying from a single location, that you can manage access to your code, and all the other things that having your databases in source control will bring.
For more details on the concept of putting your database in source control, and working better within teams in general, Iâ€™d recommend reading the SQL Server Team-based Development book. Itâ€™s a free download.
Addendum (3/27/2011): If you got this link through an email, could you post a comment belowÂ as to which distribution list it’s from? Thanks.