This gives you a mixed bag in my opinion. Final Builder has this in which TFS does the monitoring and scheduling of builds and some details, but Final Builder does the actual work. This would then form a complete Continuous Integration solution for databases, without any need for the command line steps, and so allow easy adoption and maintenance. This isnt an awesome answer as I dont know Team City, but you may ask the Team City group if they have a TFS build process template that delegates to Team City. tSQLt) tests defined in the database schema, and load the test results back in to TeamCity. Ideally, a mature plugin would also run any SQL Test (i.e. Another useful step would be to integrating with SQL Data Compare to load source controlled data into the database, which a number of implementations use. I hope that Red Gate can expand this plug in to cover steps like clearing out the existing database (perhaps a tick box in the current implementation?) - this would cover my first step, which I think most implementations will want in order to give a predictable build. I’d bet my bottom dollar that in lieu of a build and deploy environment, this is your rollback strategy. Select the Newman report from the artifacts of the build and make sure you select 'Latest finished build' so that you see the report. As you can see this is a simple process to source control a database, and one that I can see being a great help in quickly getting up and running with continuous integration for databases, whether in a database-only build (as this simple example), or part of a bigger application test process. Rollback you know how rollback is most commonly done Copy the target folder and rename it oldMyWebApp, publish the new app then if it breaks, copy the old files back over. Go to the project settings and create a new project report tab.

Teamcity how to make rollback