On creating a new migration script (Migrations V2) and switching to the "Commit changes" tab, an error in an unrelated object (e.g. stored procedure referring to a non-existent column) causes SQL Source Control to fail with "An error occurred while creating a temporary database". The complete error message shows a stack dump, originating with the error in the script which has been run to create objects in the temporary database.

It would be much more helpful if SQL Source Control recognised that an error has occurred in the script and make the script available for viewing, similar to the way that SQLCompare makes deployment scripts viewable.