SSDT: Within the Schema Compare to be allow to select publish profiles to resolve SQLCMD variables when comparing schema
Compare the database project against the SQL Server Database with code that uses SQLCMD variable, to allow different settings at deployment time, always show up as different because of the SQLCMD variable.
Which can cause problems when reserve engineering as the schema compare tool would remove the SQLCMD and cause problems when deploying to the others environments. Also miss-inform users that the object has drifted from the project when trying to manually investigate project and database drift.
Upvotes: 12<=-=Apr 9 2014 7:43AM=-=>
This is a significant reason why I have not yet adopted SSDT as my primary database development platform. I use this functionality extensively in VSDB projects.<=-=Apr 9 2014 8:16AM=-=>
I want to convert my VS2010 DB projects to SSDT and the SQLCMD variable issue is definitely a hindrance.<=-=Jul 3 2014 3:57AM=-=>
Schema Compare is practically unusable as is if you use SqlCmd variables and have multiple environments that you deploy to (i.e. dev, uat, live etc)… which is exactly the case that ssdt is designed mostly for.<=-=Oct 2 2014 11:04AM=-=>
Thank you for submitting this feedback and adding the comments. We are evaluating this request and will update you when we have more information.
SQL Server Tools Dev Team
To me, this is a must have requirement for the SQL compare tool.. The hard work appears to already be done, as the Comparison tool knows how to substitute SQLCMD vars for comparison purposes (i.e. It doesn't show any differences if the only changes are SQLCMD based).. But when another change is identified, ALL SQLCMD vars are also marked as a change, which is pretty bonkers. :(