Activity overview
Latest activity by tigmars
Generated migration script doesn't include statement to create a new schema
I did this in 2 different databases, each of which has its own SCA project:CREATE SCHEMA fooCREATE TABLE foo.bar(id INT)In one project, SCA generated statements to create foo and also to create foo...
I see what's happening. SCA generates a .sql file (Databasename_DeployPackage.sql) that's part of the build artifact created by the ADO build pipeline. It contains the definition of every sproc. During deployment, this script does one SELECT for every sproc to see if it has been deployed. (Right?) SELECT * from sys.procedures says we have over 1,500 in one of the databases. That particular database deploy takes 2 1/2 minutes. The _DeployPackage.sql script is about 1MB. I still have the same question: Am I going about this the wrong way? Any advice? Should I be concerned about a 2 1/2 minute transaction? / comments
I see what's happening. SCA generates a .sql file (Databasename_DeployPackage.sql) that's part of the build artifact created by the ADO build pipeline. It contains the definition of every sproc. ...
Oh, I should add... When I'm using the SCA project in visual studio, I'll pull down latest changes from git and then SCA spends only a few seconds deploying latest changes to my local database. It appears to start a transaction, then run only the new stuff, and then quit. It's just when I'm deploying to the production and test environments, that it takes so long. / comments
Oh, I should add... When I'm using the SCA project in visual studio, I'll pull down latest changes from git and then SCA spends only a few seconds deploying latest changes to my local database. It...
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...
Thank you for getting back to me. Your question about the log pointed me in the right direction. I needed to start with an empty database but I was using one that already had tables in it. / comments
Thank you for getting back to me. Your question about the log pointed me in the right direction. I needed to start with an empty database but I was using one that already had tables in it.
Diagnose: "Unable to deploy. Ensure package to deploy is a '.ps1' file."
I've set up a ReadyRoll build in VSTS and it reports success. I set up a ReadyRoll deployment in VSTS alsoI selected the package to deploy using the "..." however the release always fails with this...