Feature Request: Single commands for each database migration action... #22
Description
Scenario: Multiple databases being part of the same application and some of them having procedures/views that reference the other databases. Schema objects being in the update folder and procedures/views being in the RunAlways/Everytime folders.
Problem: Procedures/Views from one database might be getting executed before the schema objects exist that they depend on.
I can currently work around this by duplicating the folder structure for each database, but it would be nice if I could just execute the Update scripts for each db, then run all the RunAlways/Everytime scripts for each one Update has been ran on each one.
If you have any other suggestions(aside from only using one database, this is out of my control) I'm open to suggestions.