Activity overview
Latest activity by Sumanta
1. developer A develops a migration script to update a row of data (NOT Static) 2. developer B changes removes, say, a trigger. 3. B's code is merged. 4. Release synced. 5. A's code is merged. 6. Release synced. / comments
1. developer A develops a migration script to update a row of data (NOT Static)2. developer B changes removes, say, a trigger.3. B's code is merged.4. Release synced.5. A's code is merged.6. Releas...
That is good advice indeed. But @Sergio R that does not save us from the issue of stale migration scripts. How do you overcome the issues posed by delay between developer committing the code and some time later the merge happens and might happen and out of order. / comments
That is good advice indeed. But @Sergio R that does not save us from the issue of stale migration scripts. How do you overcome the issues posed by delay between developer committing the code and so...
Thank you fo your help so far by the way @Tianjiao_Li / comments
Thank you fo your help so far by the way @Tianjiao_Li
Thank you for your reply @Eddie D . Not sure what kind of details are you looking for. The change was a migration script that queries a value from a different DB and based on the result deletes some rows in a table. The .patch file is clean (only shows dependency on the recently upgraded tool, and the table that the script deletes rows from). Does that answer your question? / comments
Thank you for your reply @Eddie D . Not sure what kind of details are you looking for. The change was a migration script that queries a value from a different DB and based on the result deletes som...
Unfortunately we have two versions of RedGate SQL Source Control (calling it RGSSC below) being used by devs. 6.1.8.7184 is one of them As per the repro steps we are fairly certain of the original repro steps as our workarounds to ask developers to ensure they have no unresolved conflicts in RGSSC before they create migration scripts is working so far. / comments
Unfortunately we have two versions of RedGate SQL Source Control (calling it RGSSC below) being used by devs. 6.1.8.7184 is one of themAs per the repro steps we are fairly certain of the original r...
DevOps process solutions: Stale migrations scripts are biting us
Due to some issues that we cannot solve for about 6 months, we have a delay between developers creating migration scripts and the code getting merged into master. Further, we are using the SQL scri...
Collation error in 'build' step does not get ignored by 'IgnoreCollation'
If I pass IgnoreCollations, I get:WARNING: The error 'Cannot resolve the collation conflict between "SQL_Latin1_General_CP1_CS_AS" and "SQL_Latin1_General_CP1_CI_AS" in the equal to operation.' occ...
@Russell D @lfreijo any ideas? This is blocking a release now. / comments
@Russell D @lfreijo any ideas? This is blocking a release now.
And really its not a warning, as the build breaks at Build step with that error. / comments
And really its not a warning, as the build breaks at Build step with that error.
@DanSniderman How did you get past it... I am in the same boat. If I pass IgnoreCollations, I get: WARNING: The error 'Cannot resolve the collation conflict between "SQL_Latin1_General_CP1_CS_AS" and "SQL_Latin1_General_CP1_CI_AS" in the equal to operation.' occurred when executing the following SQL If I do NOT pass IgnoreCollations, I get: WARNING: The error 'Cannot resolve the collation conflict between "Latin1_General_CI_AS" and "SQL_Latin1_General_CP1_CI_AS" in the equal to operation.' occurred when executing the following SQL: Clearly I am missing some core concept here. Can anyone help? / comments
@DanSniderman How did you get past it...I am in the same boat.If I pass IgnoreCollations, I get:WARNING: The error 'Cannot resolve the collation conflict between "SQL_Latin1_General_CP1_CS_AS" and ...