How can we help you today? How can we help you today?
TheMaskedData
Thanks Simon - no problem, thanks for clarifying!  It's a tough problem, in the past I've used SQL Clone to get round this because you can integrate SCA with it and it does builds on top of the cloned DB, which gets around the "deploying the full DB in the build problem" - if you have access to that, it could potentially help? Although I think if you're using SQL Source Control as the method for source controlling this wouldn't help. The other option is I believe asking the question "do we even need to do a full build?" - whilst there is obviously value to a full clean build, invalid objects and unfixable problems mean that it's really just a blocker to the rest of the process. Is there any reason why, instead of a build, you couldn't just zip up the files as part of the pipeline and pass the zip file along instead of the build artifact? Once pushed down the pipeline for release you can then just carry on as normal and pass it to the New-DatabaseReleaseArtifact cmdlet (Docs: https://documentation.red-gate.com/sca/reference/powershell-cmdlets/new-databasereleaseartifact) - I'm running off of my older knowledge here as it's been a while since I used SCA specifically but I think (and it looks like) it might accept a zip folder of the files from your GitHub repo instead of the NuGet specifically... I'm sure one of the tech folks from Redgate's side, or maybe their support team would be able to give an even better answer than me, but it might be something to explore initially if it helps you get started [image] / comments
Thanks Simon - no problem, thanks for clarifying! It's a tough problem, in the past I've used SQL Clone to get round this because you can integrate SCA with it and it does builds on top of the clon...
0 votes