Geeks With Blogs
ken spencer

Well, my good friend Ben Day beat me to the blog post on this. We have both worked on projects where the dev team all wanted to use a shared database for development. And this always turns out to be a bad idea for many reasons. Problems such as the following are neatly summarized in Ben’s article:

Reason #1: Fuzzy Version Control

Reason #2: Shared databases rot your brain and encourage you to write bad unit tests.

Reason #3: Developers are integrating on top of each other in real-time.

Reason #4: Everyone has DBO permissions.

There are many other reasons that pop up too but for now these suffice. Check out Ben’s great article to see his description of each problem and the solution.


Posted on Tuesday, January 25, 2011 8:47 AM | Back to top

Comments on this post: Databases during Development: Shared or developer specific?

No comments posted yet.
Your comment:
 (will show your gravatar)

Copyright © xamlnotes | Powered by: