Comments
Sort by recent activity
I would also like to vote for this! / comments
I would also like to vote for this!
MayaMalakova said:
TheoL said:
Does this mean those on Toolbelt Essentials essentially lose this functionality completely (for new projects)?
We left a backdoor for those that really want to continue using it - you can set AlwaysEnableMigrationsPage to True in the UI options in %LOCALAPPDATA%\Red Gate\SQL Source Control 7\RedGate_SQLSourceControl_CommonUI_UIOptions.xml
I tried this and the backdoor appears to have been deprecated. The setting didn't exist in the xml file, so I added it, but it is automatically removed when I open ssms and I cannot access migration scripts. So has Red Gate basically removed the ability to use migration scripts with a state-based deployment method? It is now not possible to use the "instead of" migration scripts for changes which require a script, such as adding mandatory columns to tables... These can't be resolved using before/after scripts, along with loads of other changes (e.g. setting up Change Data Capture on tables, with an auditing job). Bit of a nuclear change there, don't you think Red Gate? Can you reinstate the backdoor so we can have a bit of time to consider moving to a migrations-based deployment approach (required to use SQL Change Automation)? Edit: I tried the backdoor approach again and it seems to have worked (it didn't delete the setting from the xml file this time)! Hopefully this backdoor will be around for a while though, as we might not have time to move to a migration-based approach for a while. Still seems like a shame to force users to adopt one deployment approach, after providing flexibility in previous versions.
/ comments
MayaMalakova said:
TheoL said:
Does this mean those on Toolbelt Essentials essentially lose this functionality completely (for new projects)?
We left a backdoor for those that reall...