In the case of our automated build, the user account that runs the build process has access to the database.

Since the task does not specify a user name and password, the schemaSync task uses the Windows security credentials of the user running the build to logon to the database. You’ll notice the target uses a couple of properties to point at the location of the project root ($). Here is the actual Nant target from our build script: Thanks to the SQL Compare API that was included with RedGate’s SQL Toolbelt, I was able to put together an NAnt task that does the job. As part of that process, we need to update the database structure from the scripts folder. Our build process includes a step to deploy a test/demo version of our web to a server. It’s ability to export the database structure to a scripts folder and then synchronize changes from a database back to the scripts folder is a its greatest feature It allows the database structure to be placed under source control with a high degree of granularity since each database object becomes a script file. Redgate’s SQL Compare is an indispensible tool for anyone doing development against Microsoft SQL Server.

Sql toolbelt 2012