Comments
Sort by recent activity
Thanks, Dan B. Yes, it does exist but I tried to add a filter to the project to exclude objects that begin with '_' but the filter doesn't load up in Visual Studio 2017. The instructions are simply to drop the filter file into the root of the project (same folder where the project file exists) and then unload and load the project and the filter should load up in the project. But this isn't working (the filter file loads up in VS 2015 but not VS 2017). Have the filter instructions changed? I'm not understanding the logic of removing the migration_log from the target database to stop the baseline script from running. The objective of the baseline script is to run against an empty target database. If the migration_log exists on the target database doesn't that mean that the target database is NOT empty? BTW - I'm just using a simple 3 step CI/CD method: 1 build task = "build the sql change automation project" & 2 release tasks 1) PeformCreate & 2 ) PerformDeployFromResources. Thanks for any help; much appreciated. / comments
Thanks, Dan B. Yes, it does exist but I tried to add a filter to the project to exclude objects that begin with '_' but the filter doesn't load up in Visual Studio 2017. The instructions are simply...
@SERVERNAME = 'NOTHING'" and the condition does not stop the baseline from executing. What can I do to ensure that the baseline does NOT execute. Once it's created, I can't delete it. The documentation states that the condition will restrict the baseline from executing even on the first release. Should I un-comment the baseline header? / comments
@SERVERNAME = 'NOTHING'" and the condition does not stop the baseline from executing. What can I do to ensure that the baseline does NOT execute. Once it's created, I can't delete it. The document...
We decided to create the target DB before we create the SCA package. / comments
We decided to create the target DB before we create the SCA package.
Follow on note: The target DB is set in the release environment to the target server and same DB name is used. / comments
Follow on note: The target DB is set in the release environment to the target server and same DB name is used.
we set our SCA test project without a target DB and when the release runs it errors because the agent can't login to the SQL Server database. But the database doesn't exist, yet in the failed step our agent has SA so it can do whatever it needs to do).. / comments
we set our SCA test project without a target DB and when the release runs it errors because the agent can't login to the SQL Server database. But the database doesn't exist, yet in the failed step ...