Comments
Sort by recent activity
Hi, Apologies for the delayed response. This is currently a limitation of SQL Change Automation programmable object handling (See permission handling under https://documentation.red-gate.com/sca/developing-databases/concepts/migrations/programmable-objects). You can manually alter the programmable object but it is then liable to be overwritten if you are not careful. I have raised an internal ticket for this and we will see if there are any improvements that can be made here. We will get back to you when we know. Kind Regards, Ivo Miller / comments
Hi,Apologies for the delayed response. This is currently a limitation of SQL Change Automation programmable object handling (See permission handling under https://documentation.red-gate.com/sca/dev...
Hi, Apologies for the delayed response. This is currently a limitation of SQL Change Automation programmable object handling (See permission handling under https://documentation.red-gate.com/sca/developing-databases/concepts/migrations/programmable-objects). You can manually alter the programmable object but it is then liable to be overwritten if you are not careful. I have raised an internal ticket for this and we will see if there are any improvements that can be made here. We will get back to you when we know. Kind Regards, Ivo Miller / comments
Hi,Apologies for the delayed response. This is currently a limitation of SQL Change Automation programmable object handling (See permission handling under https://documentation.red-gate.com/sca/dev...
Hi, Apologies for the delayed response. This is currently a limitation of SQL Change Automation programmable object handling (See permission handling under https://documentation.red-gate.com/sca/developing-databases/concepts/migrations/programmable-objects). You can manually alter the programmable object but it is then liable to be overwritten if you are not careful. I have raised an internal ticket for this and we will see if there are any improvements that can be made here. We will get back to you when we know. Kind Regards, Ivo Miller / comments
Hi,Apologies for the delayed response. This is currently a limitation of SQL Change Automation programmable object handling (See permission handling under https://documentation.red-gate.com/sca/dev...
Hi, Apologies for the delayed response. This is currently a limitation of SQL Change Automation programmable object handling (See permission handling under https://documentation.red-gate.com/sca/developing-databases/concepts/migrations/programmable-objects). You can manually alter the programmable object but it is then liable to be overwritten if you are not careful. I have raised an internal ticket for this and we will see if there are any improvements that can be made here. We will get back to you when we know. Kind Regards, Ivo Miller / comments
Hi,Apologies for the delayed response. This is currently a limitation of SQL Change Automation programmable object handling (See permission handling under https://documentation.red-gate.com/sca/dev...
Hi, Apologies for the delayed response. This is currently a limitation of SQL Change Automation programmable object handling (See permission handling under https://documentation.red-gate.com/sca/developing-databases/concepts/migrations/programmable-objects). You can manually alter the programmable object but it is then liable to be overwritten if you are not careful. I have raised an internal ticket for this and we will see if there are any improvements that can be made here. We will get back to you when we know. Kind Regards, Ivo Miller / comments
Hi,Apologies for the delayed response. This is currently a limitation of SQL Change Automation programmable object handling (See permission handling under https://documentation.red-gate.com/sca/dev...
We have pushed a new version of the ReadyRoll.MsBuild package, 3.2.19150.8056, where the behaviour change has been reverted. Apologies again for the inconvenience caused. / comments
We have pushed a new version of the ReadyRoll.MsBuild package, 3.2.19150.8056, where the behaviour change has been reverted. Apologies again for the inconvenience caused.
Hi. Many apologies for your issue. The old behaviour can be restored by setting environment variable "RG_UseExecuteStatementsInPackageScript" to "true". We will look to release an update fixing the issue soon. / comments
Hi. Many apologies for your issue.The old behaviour can be restored by setting environment variable "RG_UseExecuteStatementsInPackageScript" to "true".We will look to release an update fixing the i...
Also, if you are using the ReadyRoll.MsBuild nuget package via the ReadyRoll AzureDevOps plugin you can make the plugin target the last working version (3.2.19141.7818) by selecting "specific" under ReadyRoll version and specifying that version number. / comments
Also, if you are using the ReadyRoll.MsBuild nuget package via the ReadyRoll AzureDevOps plugin you can make the plugin target the last working version (3.2.19141.7818) by selecting "specific" unde...
SQL Change Automation executes scripts using sqlcmd, so it definitely sounds like that is the source of the issue. / comments
SQL Change Automation executes scripts using sqlcmd, so it definitely sounds like that is the source of the issue.
Hi @ducman, This sounds like the expected behaviour - when you click "Deploy Project", the local development database will be updated to match the stored procedure in the project, which in this case will be the change made by Developer A. If Developer B wants to preserve the change they made, they should import the change into the project before doing a pull. If the changes conflict, git will prompt the developer to address the conflicts. / comments
Hi @ducman,This sounds like the expected behaviour - when you click "Deploy Project", the local development database will be updated to match the stored procedure in the project, which in this case...