Best Practice with version control of DB schemas..

So I am currently working a Microsoft data integration project (more on that later). For the first time, we have setup multiple SSIS environments to mirror that of our production database environments, i.e. Development, Test and Production. I am currently using Visual Studio 2010 to manage database changes (via a database project). All source code is version controlled via TFS.

At the moment, if I make any changes to the development SSIS database, I do so directly through SQL Server Management Studio. Within VS 2010, I then perform a schema compare against the Project schema and update the project schema with any changes.

Once packages have been deployed and tested, on Development, I build and deploy my database solution out to test and production.

This process while it works seems to be a little combersome. I was wondering if anyone out there reading this, has experience in managing multiple database instance using VS, and how they manage schema changes. Thanks!