You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Loving the dac-pac schema compare tool. I wondered if it would be possible to allow the override of the DatabaseName sqlcmd variable that gets put into the top of the generated script, from the default 'Test'.
The use case for me, is that I am actually using the generated script to run as I trust it a lot more (being able to see exactly what is being ran in the script) rather than through a dac-pac publish.
However, when doing so the DatabaseName is always hard-coded to 'Test' in the script, so it would be nice to be able to amend this within the DevOps pipeline to whatever I want it to be.
I'm going to attempt to use a 'Replace Text in Files' action on the script, but it would be really nice if this could be part of the DevOps schema-compare plugin itself.
Thanks
The text was updated successfully, but these errors were encountered:
Calumfletcher
changed the title
Possibility to override DatabaseName from 'Test'
Possibility to override DatabaseName from 'Test' in generated script
Aug 25, 2020
Hi,
Loving the dac-pac schema compare tool. I wondered if it would be possible to allow the override of the DatabaseName sqlcmd variable that gets put into the top of the generated script, from the default 'Test'.
The use case for me, is that I am actually using the generated script to run as I trust it a lot more (being able to see exactly what is being ran in the script) rather than through a dac-pac publish.
However, when doing so the DatabaseName is always hard-coded to 'Test' in the script, so it would be nice to be able to amend this within the DevOps pipeline to whatever I want it to be.
I'm going to attempt to use a 'Replace Text in Files' action on the script, but it would be really nice if this could be part of the DevOps schema-compare plugin itself.
Thanks
The text was updated successfully, but these errors were encountered: