You can pick the database you wish to run the script against by clicking the small + next the the server in the "configure database distribution list" dialog. This should show you a list of the database on that server. These can then be added to your distribution list.
We are already considering added your 2nd piece of feedback to SQL Multi Script in a future release.
The feature you describe has definitely been 'approved', in that it's something we want to do. We don't currently have a date for the next release of SQL Multi Script, but as soon as we have one we'll update the public roadmap here.
Note that SQL Multi Script research is on-going, and I'll be running a survey shortly on this, which will hopefully confirm my findings to date.
Hi I agree, the tool is definitely a good start in the right direction.
One thing I would like to see is better file management.
eg. when the files get modified from another source, I would like the tool to pick up on these, and ask to apply or ignore these changes. (as I usually use a different editor)
Or a way to revert all files.
Also some statistics in running time would be nice.
We have come to use Multiscript a lot in the past 6 months and its turned into a lifesaver for our larger bundled projects. The only thing I'd like to see in a future build is timestamps for executions. We run a lot of migration scripts and we have a plethora of test environments and in order to gauge our outage times, it would be nice to timestamp the start and end of the script executions individually.