sql,visual-studio-2013,schema,database-project,schema-compare
It is possible to avoid this issue by changing the SQLCMD Variables Default or Local settings in the Database Project Properties. The behavior is: - If a Local value is defined, this is what is used in Schema Compare - If no Local value is defined, the Default value will...
visual-studio-2012,sql-server-2012,ssdt,schema-compare,refactoring-databases
Figured out the cause of this problem. I noticed that when doing a schema compare against my SQL Data Tools project and a different (yet essentially identical) database, the refactor component was in fact considered. I took a look at the generated SQLCMD script, and at the bottom saw lots...
visual-studio-2012,visual-studio-2013,ssdt,schema-compare,mru
I checked and it's hard-coded to 5 right now. There's no way around this, but I'll look into fixing it in a future release since this does seem too low.