Comments
Sort by recent activity
Hi jdms754, We need a bit more information about your setup. Are you using the SCA extensions in VSTS with a SCA project (formerly known as a ReadyRoll project)? If this is not the case can you please describe your pipeline to us? / comments
Hi jdms754,We need a bit more information about your setup. Are you using the SCA extensions in VSTS with a SCA project (formerly known as a ReadyRoll project)?If this is not the case can you pleas...
At present there is no way to do this using the SQL Change Automation VSTS plugin. It should be possible with SQLCMD variables, however these are not yet supported in SQL Change Automation. This is a high priority for us, so you should hear something in the near future. / comments
At present there is no way to do this using the SQL Change Automation VSTS plugin. It should be possible with SQLCMD variables, however these are not yet supported in SQL Change Automation. This is...
Hi @dsrofe, This would depend on what kind of project you have. Are you using a SQL Source Control project or a SQL Change Automation project? / comments
Hi @dsrofe,This would depend on what kind of project you have. Are you using a SQL Source Control project or a SQL Change Automation project?
Hi @GordonMPG, The step templates have not been updated yet but that should happen soon. You're correct to notice that the problem is about the DLM Automation reference and you should be able to fix it if you change the value to that Name parameter to SqlChangeAutomation / comments
Hi @GordonMPG,The step templates have not been updated yet but that should happen soon.You're correct to notice that the problem is about the DLM Automation reference and you should be able to fix ...
Hello @DavidWNAZ, I believe that is the expected behavior as abandoning a release on VSTS just stops the release from proceeding but it does not have any effect on SQL Change Automation. When the next release is created it will still try to deploy all the changes that have not been deployed to the target database. You should revert your change in source control if you don't want it to be released. / comments
Hello @DavidWNAZ,I believe that is the expected behavior as abandoning a release on VSTS just stops the release from proceeding but it does not have any effect on SQL Change Automation. When the ne...
Hi @pporter . /scr1 is your local checkout of the repository. / comments
Hi @pporter ./scr1 is your local checkout of the repository.
Hi @pporter, Can you give us a bit more detail about what you mean by "version of a stored procedure". Would you be interested in knowing which revision/commit is on the target server? Or are you just interested in checking the differences between what you have in source control and the target server? Thanks, Diogo / comments
Hi @pporter,Can you give us a bit more detail about what you mean by "version of a stored procedure". Would you be interested in knowing which revision/commit is on the target server? Or are you ju...
Hi @pporter I think you can use the SQL Compare command line then. There is some documentation on this page http://https//documentation.red-gate.com/sc13/using-the-command-line I think you may want something like sqlcompare.exe /scr1:YourScriptsFolder /s2:YourDatabaseServer /db2:YourDatabaseName /u2:YourUsernameToConnectToTheDatabase /p2:YourPasswordToConnectToTheDatabase /Include:storedprocedure:\[YourStoredProcedureName\] /verbose / comments
Hi @pporter I think you can use the SQL Compare command line then. There is some documentation on this page http://https//documentation.red-gate.com/sc13/using-the-command-line I think you may want...
I've raised this problem with the support team. / comments
I've raised this problem with the support team.
Hi valthordruzin which version of SQL Source Control are you using? If you're not on the latest version (6.0.2) I'd suggest trying to update and see if that solves your problem. / comments
Hi valthordruzin which version of SQL Source Control are you using? If you're not on the latest version (6.0.2) I'd suggest trying to update and see if that solves your problem.