Using MS Team System 2008 Database Edition

I want to start a source that controls our databases. I read a lot of questions here and found that MS Team System 2008 with database is what I need. So we get it and we are really lost.

We would like to first of all compare the various DBs we have (DEV, STA and PROD) because we never did any control over the source codes, they probably have some differences that we would like to solve ... I read that MS Team System 2008 DB Edition can do this, but I think we are not finding how to do it.

Once we had each DB in the same "state", we would like to create some kind of plan to propagate the changes from the local developer base to some control source (I think creating a database project under SVN would do the job ). And then you have a way to generate a "change script" to propagate the changes to STA and then to PROD of course. Any ideas on how to do this?

This may have been asked already, but I think I am not finding anything because I am not using the correct search terms.

A link to another SO question or some article describing how to work with MS Team System 2008 Database Edition and SQL Server 2005 projects is greatly appreciated.

Thanks everyone

Greetings

+2


source to share


1 answer


The answer to your first question is the schema and data comparison functions of Visual Studio Team System - Database Developer. You should have a menu item between your build and test called Data. This data menu has options such as Schema Compare and Data Comparison, which are fairly intuitive to use.

The next question is how to use the original database control. The original control should be your only source of truth for the schema. When you create database projects and save them in the original control, I would suggest mirroring first. You can then apply the changes to projects and compare projects against target environments like dev / QA / prod to identify and script differences that can be ported to those environments.



EDIT: I also highly recommend Chapter 8 in Professional Team Foundation Server . This chapter covers the use of Team Edition for database professionals for schema management purposes.

+2


source







All Articles