Comments
Sort by recent activity
I agree, refreshing may not cause issue. But an accidental drop/delete/truncate of this migration on my target DBs is what I am worried about. / comments
I agree, refreshing may not cause issue. But an accidental drop/delete/truncate of this migration on my target DBs is what I am worried about.
also , what is the use of Deployed status=2... what am I gaining by marking a script "Mark it deployed" on my source DB? / comments
also , what is the use of Deployed status=2... what am I gaining by marking a script "Mark it deployed" on my source DB?
I agree, that the table should not be dropped. But we are still evaluating the tool, so we are weighing in possible accidents. The table may not be dropped, but could be refreshed when we do data refresh from higher environements to lower. For Eg : if we refresh out UAT DB with Prod DB, then the migrationlog table would also get refreshed, so there is always a chance that the data in table gets messed. So I am finding ways to manipulate it, esp finding a way to skip a Change script from being deployed on a target DB. / comments
I agree, that the table should not be dropped. But we are still evaluating the tool, so we are weighing in possible accidents. The table may not be dropped, but could be refreshed when we do data r...
I guess let me put my question in a different way. Lets say I have a baseline script and couple of change scripts in project. And they were succesfully deployed on my Target DB. So I assume the migrationlog table would show 0 for baseline script and 1 for the change scripts. Is that right? Now, lets say, my migrationlog table got dropped by accident on my target DB. Now If I run my release pipeline, since there is no migrationlog and also since it finds a baselinescript, it safely skips running the baseline script. But it always try to run the other two change scripts on my target DB. The question is, how can i skip the other two change scripts from being run on my target DB? I tried setting them as "Mark them as deployed" from VS, but still the release pipeline is trying to execute it on my target DB, / comments
I guess let me put my question in a different way. Lets say I have a baseline script and couple of change scripts in project. And they were succesfully deployed on my Target DB. So I assume the mig...
What should I mark a script's deployed column value in my source DB so that it doesnt get executed on my target DB? I tried 0,1,2...none of them worked...i dont want to delete the script from my VS project. / comments
What should I mark a script's deployed column value in my source DB so that it doesnt get executed on my target DB? I tried 0,1,2...none of them worked...i dont want to delete the script from my VS...
so if I set a script's deployed status to 0 in my source DB, then that script would not be run even in my target DBs, but they would be set as "Marked as deployed" on target DB's as well...is that right? / comments
so if I set a script's deployed status to 0 in my source DB, then that script would not be run even in my target DBs, but they would be set as "Marked as deployed" on target DB's as well...is that ...
What should I mark a script's deployed column value in my source DB so that it doesnt get executed on my target DB? I tried 0,1,2...none of them worked...i dont want to delete the script from my VS project. / comments
What should I mark a script's deployed column value in my source DB so that it doesnt get executed on my target DB? I tried 0,1,2...none of them worked...i dont want to delete the script from my VS...
This is SQL Change Automation project in VS. / comments
This is SQL Change Automation project in VS.
Did you get a chance to look into this? / comments
Did you get a chance to look into this?
I tried using it in my Deployment step, but it gave a warning saying [warning]Cmdlet parameter SQLCompareOptions is not supported for SQL Change Automation projects. This option will be ignored. [warning]Cmdlet parameter AbortOnWarningLevel is not supported for SQL Change Automation projects. This option will be ignored. I am attaching a screen shot of my Deployment step and attaching release log.[image]
/ comments
I tried using it in my Deployment step, but it gave a warning saying [warning]Cmdlet parameter SQLCompareOptions is not supported for SQL Change Automation projects. This option will be ignored.[w...