The enclosing transaction seems really long
We've been using SCA + Visual Studio successfully for a few years now. We also use git and Azure Dev Ops for deployments. I understand SCA automatically wraps everything in a transaction during a deployment. But the elapsed time between the beginning and the end of the deployment is pretty long. The log file says it was 55 seconds last time. I'm concerned about what happens if an SCA-generated migration script modifies a frequently-used table. Won't that lock applications out? (Ordinarily we shut off the super sensitive parts of the app during a deployment but that's not always an option.) I must be missing something. Any ideas? Thanks.
0 · Share on Twitter