Comments
4 comments
-
Hi ivopld,
Thanks for the post. Could you provide a bit more details regarding what you're trying to do, and why you'd want to save this information, please? Is it as a way of recording changes, eg, for audit needs?
Thanks,
Colin. -
Hi Colin,
In a way it is for "audit" purposes.. it would be helpful for our organization to track issues related to 'missing scripts' or scripts that haven't been run on particular databases.
So a way to log the execution history of scripts on databases, would be very helpful. -
Or, if there's a button to export the contents of the 'Scripts Executed' and 'Exectued Against' fields into some type of external file.. that would also be very useful.
-
Hi ivopld,
Thanks for the further information. It isn't something that SQL Multi Script does at the moment, but I'll add this as a request for consideration for a future release.
Best regards,
Colin.
Add comment
Please sign in to leave a comment.
The 'Save Results' features doesn't really help as it doesn't specify exactly what script was run on what database and when.
Is there are some type of patch that can be dowloaded, which would allow for this data to be saved in a similar way the 'Messages' are saved?