We are developing an aspx project with Visual Studio 2010 Professional, SQL Server 2008 R2 and Team Foundation Server 2010. Because the development has been completed in multiple offices, each developer has their very own local cases of the databases. I wish to bring these multiple databases under source control (or at best the schemas from the DB, structure and saved methods - data does not matter in my experience). My preferred approach would be to add database projects towards the Versus solution, that is already source controlled in TFS. Any changes is going to be provided by TFS, and may be used in your area.

The issue I am getting would be that the database projects have a mention of the a nearby database instance (server &lifier title). When someone will get the most recent version of my changes, they're going to have a mention of the my local DB instance (that is dissimilar to their local DB instance). They will have to alter the DB particulars (thus checking the dbproj out) to be able to get my updates.

So, can there be in whatever way the database server &lifier title could be excluded from source control as the schemas remain under source control? Any help could be much appreciated!

I am unsure if you're able to. However, you could utilize an alias, so all the designers make use of a database on their own local machine, but recommended through the same alias.

Have a look at: http://www.mssqltips.com/sqlservertip/1620/how-to-setup-and-use-a-sql-server-alias/ based on how to create an alias up.

That method for you to separate the database in the connection particulars.