私は小規模なソフトウェア開発チーム (4 人) を率いており、ソース管理された SQL Server 2008 データベース プロジェクトに着手したばかりで、開発者ごとに分離された開発データベースを使用しています。私はまだこれを 1 ステップずつ実装していますが、各開発者が独自のデータベースを持ち、<ProjectName>_DEVELOPMENT_<TFSUserName>. これはすべて、私が読んでいる MSDN の記事で推奨されていたものですが、それがおかしいと思われる場合は誰かが教えてくれました。
Anyway, we have a shared application solution that we've been developing for some time. In the past, we had no database version control, and just modified our database directly from SQL Server Management Studio when new reference data needed to be populated, or when we were testing functionality -- one change immediately affected everyone else. So with this new change, I'm wondering what the best way would be to have each person connect to their isolated development databases from the application solution. Prior to isolated databases, our connection to the database was specified in our application's web.config as a connection string. If we're each going to have our own database, the only way I can see it working is for each developer to set their connection string in their local solution to point to their personal database. But changing the web.config will check out that file in the solution, so developers will always have to specifically uncheck that file when checking in application changes to the baseline. Is there a less clunky way for each developer to use their isolated database when doing application testing?