Comments
Sort by recent activity
Thanks, @Ivo_Miller and @Sergio R. It seems that if we made a baseline from prod, then it should still know that only programmable objects modified since the baseline should be included in the deployment, regardless of the existence of the __MigrationLog table and a row for the programmable objects. I will go ahead an "re-deploy" all 6000+ programmable objects to the dev integration DB, but it doesn't feel good. [image] I'll make some more comments here when it's time to go to prod. Hmmm. I just looked at prod, and it doen't have a __MigrationLog table, so I'm assuming it will want to redeploy all 6000+ objects there, too. Wondering why there is no __MigrationLog table in the prod DB that we used for the baseline/target when I created the project? What if I hacked it by creating a __MigrationLog table and copying the data over from the dev DB? / comments
Thanks, @Ivo_Miller and @Sergio R. It seems that if we made a baseline from prod, then it should still know that only programmable objects modified since the baseline should be included in the dep...
I also had to do some adjustments in the pre-deployment script for the project validation using the powershell cmdlets. Apparently that doesn't use '%_shadow', so I brute-forced the check to look to see if the DB was on my local host. I imagine that will break if I move the build to CI server, but it's working for now. I wasn't able to actually see a build validation DB on my local host - curious as to where (which instance) that is being built on and how the DB is named? / comments
I also had to do some adjustments in the pre-deployment script for the project validation using the powershell cmdlets. Apparently that doesn't use '%_shadow', so I brute-forced the check to look ...
After resolving the installation issue , which required a second update to vs 2019 ent (v 16.4.4) and uninstalling and reinstalling sca, I am up and able to "refresh" the project in VS. I was able to use a pre-deployment script to set the compatibility level of the shadow DB to 100. It still seems that this is a bug , though, unless I'm misunderstanding the concept of setting the target platform to "sql server 2008" in the project settings. / comments
After resolving the installation issue , which required a second update to vs 2019 ent (v 16.4.4) and uninstalling and reinstalling sca, I am up and able to "refresh" the project in VS. I was able ...
Thanks, @Sergio R. I think that is probably a valid solution, although somewhat heavy. I was going to try to use a pre-deployment script to just set the compatibility level if the '$(DatabaseName)' LIKE N'%_shadow', but my VS SCA is now broken - I believe from an VS Ent 2019 update. I submitted a support ticket for that one. The journey continues. / comments
Thanks, @Sergio R. I think that is probably a valid solution, although somewhat heavy. I was going to try to use a pre-deployment script to just set the compatibility level if the '$(DatabaseName...
I hear ya, @David Atkinson - re: full clones. Just not sure we have the $ for SQL Clone/Provision at this time. Ergo, looking into PSDatabaseClone. Meanwhile, I'm going to mark @Sergio R 's last one as the answer even though I have not tested it again since the fix. I have confidence in the team. [image] / comments
I hear ya, @David Atkinson - re: full clones. Just not sure we have the $ for SQL Clone/Provision at this time. Ergo, looking into PSDatabaseClone. Meanwhile, I'm going to mark @Sergio R 's last...
That article is helpful - thanks. I want to explore the idea of a pre-deploy script making stubs. I'm still a bit confused on how to best ignore certain objects and programmable object scripts without having to redo the entire baseline generation that takes so long. I do realize I'm hacking away in SCA at this point. Just want to get this puppy into source so I can develop some new objects. [image] / comments
That article is helpful - thanks. I want to explore the idea of a pre-deploy script making stubs. I'm still a bit confused on how to best ignore certain objects and programmable object scripts wi...
Thanks, @David Atkinson. I've been working that angle, too. It worked for one simple DB; I just created a shell for it. The other DBs have the same kind of problems - cross refs, and are too large to restore onto my laptop. Considering a cloning tech like SQL Clone/PSDatabaseClone. / comments
Thanks, @David Atkinson. I've been working that angle, too. It worked for one simple DB; I just created a shell for it. The other DBs have the same kind of problems - cross refs, and are too lar...
Much appreciated, @Sergio R . I will want to strategize with the support team on how best to handle some other issues with baselining this DB. It has programmable objects that have linked server refs, cross DB refs, etc. Getting a deploy to my dev DB has been a challenge. / comments
Much appreciated, @Sergio R . I will want to strategize with the support team on how best to handle some other issues with baselining this DB. It has programmable objects that have linked server r...
Short answer: I don't think so. SCA v3 requires Windows Powershell per https://documentation.red-gate.com/sca3/getting-started/requirements/powershell-component-requirements SCA v4 isn't super clear: https://documentation.red-gate.com/display/sca4/PowerShell+component+requirements But, since it says ".NET Framework 4.7.2 or later" and not .NET core, I would say windows only. / comments
Short answer: I don't think so.SCA v3 requires Windows Powershell per https://documentation.red-gate.com/sca3/getting-started/requirements/powershell-component-requirementsSCA v4 isn't super clear:...
No, @Mgtow, I had to stick with "I am just not raising a medium alert unless the severity is >=21 (it was 20). That keeps us from getting spammed when the scanner runs, but does not give us alerts from "real" error log entries that are sev 20. " / comments
No, @Mgtow, I had to stick with "I am just not raising a medium alert unless the severity is >=21 (it was 20). That keeps us from getting spammed when the scanner runs, but does not give us alerts...