Source Control for Databases - Nightmares with TFS

[woohoo]

connects Management Studio directly to TFS, overlays SSMS with source control features. I should be a salesman for Redgate (If only they matched my day rate!)

SQL Source Control - download a free trial for a month. I will be buying it at the end of the trial and it only took me 1 hour to realise that!

Great will take a look when back off my hols.

[BlueSharp]

In the past we have got VS to deploy the development instance to a local db and then made changes using SSMS. When it comes to checkin you can do a compare in VS to identify the changes so it will auto check-them out for you. If it builds locally with sql unit testing, checks then your good to check the changes in.

[NorthWestPerm2Contr]

In the past we have got VS to deploy the development instance to a local db and then made changes using SSMS. When it comes to checkin you can do a compare in VS to identify the changes so it will auto check-them out for you. If it builds locally with sql unit testing, checks then your good to check the changes in.

Try using the tool I suggested and you will see the phenomenal difference. Even if you are working as you suggest it still is very useful. Most places I have worked have a single dev Database due to limited number of developers - usually I control things when it comes to dev/source control/deployment. Local DB makes a lot of sense in larger teams, except it can kill your machine with intensive queries.