Feature requests - checkbox for "use"

Petro

Hi all

updates are sometimes for more than one database. in oure case, we often make separated scripts (files) to make sure the script runs on the correct db. so we use a "use". but multiscript does not change back the db-context, witch is not the db that is shown in multiscript.

for us, the need for "use" is imported, because we do not use multiscript to update productive dbs (yet).

Possibilities:
- option for "check for 'use' and mark at import"
- checkbox on each script for "set back the db before run the script"

thanks for thinking about

see ya
petro

HJoyce

I have logged this as a feature request to be considered in the next release. Thanks for the feedback.

Regards,
Helen

shadowbob

A feature similar to this would probably be considered my "#1" productivity booster. Basically, I'd love an option to "Override USE statements in script" so that if any USE statements happen to be in the script, they go away and the script actually runs on the database which Multi Script intends it to. This would literally shave minutes off of every single work day for me. Thanks a bunch!

Roust_m

But what if you have something like this:
USE MyDB
[do some schema changes here]
USE msdb
[create some jobs here]

if you ignore all USE statements your script may fail.

I would rather have an ability to do automatic replacements like this:
USE {database name}
[do some schema changes here]
USE msdb
[create some jobs here]
So {database name} would automaticaly be replaces to the database the script runs against.

Colin Millerchip

Hi,

Thanks for the suggestion, I've logged this request and we'll consider it for the next release.

Best regards,


Colin.