Comments
Sort by recent activity
Yes, but what about the schema changes? I presume that is what you still need to commit to make the repos match the database. Or are there other differences? Did you run the SQL in your migration script on your development database to change its schema? If you did I think it should show your schema changes on the commit tab. / comments
Yes, but what about the schema changes? I presume that is what you still need to commit to make the repos match the database. Or are there other differences?Did you run the SQL in your migration sc...
Is it the case that you need to commit the schema changes that were in your migration? Are they not showing on your commit tab? / comments
Is it the case that you need to commit the schema changes that were in your migration? Are they not showing on your commit tab?
Hi @babothe You should be able to choose a SQL Source Control project on the "Operation" dropdown. [image] And in order to have the builds starting automation you should also enable the continuous integration trigger. [image] There's also some information about the setup in our documentation https://documentation.red-gate.com/display/SCA3/Use+the+VSTS+Build+extension+with+SQL+Source+Control+Project / comments
Hi @babothe You should be able to choose a SQL Source Control project on the "Operation" dropdown.And in order to have the builds starting automation you should also enable the continuous integrati...
Hi @WillC, that version should be available now. Hope it helps. / comments
Hi @WillC, that version should be available now.Hope it helps.
Hi @WillC does that still happen on version 3.2.19162? / comments
Hi @WillC does that still happen on version 3.2.19162?
@samssb82 you might need to update the Build and Release extensions to the versions I mentioned earlier today. If that does not work please contact support so that we can have a closer look. / comments
@samssb82 you might need to update the Build and Release extensions to the versions I mentioned earlier today.If that does not work please contact support so that we can have a closer look.
@ChrisKaczor I can only apologize for any problems we may have caused you. We've released version 3.0.19080.6206 which should solve your problem. / comments
@ChrisKaczor I can only apologize for any problems we may have caused you.We've released version 3.0.19080.6206 which should solve your problem.
@samssb82 each cmdlet outputs the version of the module. For example
Invoke-DatabaseBuild, SQL Change Automation 3.1.10.3430, Copyright © Red Gate Software Ltd 2014-2019
If you have SQL Change Automation locally installed on your agents I think it will still use the installed version.
/ comments
@samssb82 each cmdlet outputs the version of the module. For example
Invoke-DatabaseBuild, SQL Change Automation 3.1.10.3430, Copyright © Red Gate Software Ltd 2014-2019
If you have SQL Change Aut...
samssb82 I'm afraid that version is not exposed by the error message. Are you still getting this problem with version 3.1.10.3430 of SQL Change Automation? / comments
samssb82 I'm afraid that version is not exposed by the error message.Are you still getting this problem with version 3.1.10.3430 of SQL Change Automation?
Hi @GurpreetGill There might be a problem with our latest Powershell module then. Could you please try to change your tasks to use version 3.1.10.3430? You can do that on your task definitions if you go to "SQL Change Automation version", pick "Specific" and enter 3.1.10.3430 on the specific version to be used and Save. Does it help? / comments
Hi @GurpreetGill There might be a problem with our latest Powershell module then.Could you please try to change your tasks to use version 3.1.10.3430? You can do that on your task definitions if yo...