Closed tophallen closed 4 years ago
I have the fix for this in my fork and would be happy to make a pull request for this fix. https://github.com/crimdon/SQLToolkit/compare/master...tophallen:master
The other change in that PR solves the issue of when a script file for some reason starts with a GO
statement. Since SSMS handles that scenario, it would make sense that this extension should too, even if it shouldn't be there.
Hi Allan
I don't mind putting the try catch in but I'm going away for 2 weeks so I'd rather leave it till I get back. Also the last time I implemented your PR for the GO issue, I was forced to revert it as a load of people complained it broke their builds.
Andrew
Interesting, I had tested it on a different scenarios - I'll isolate the try/catch logging and make a PR.
https://github.com/crimdon/SQLToolkit/compare/master...tophallen:master
If that looks agreeable, I'll create the PR
Hi there...sorry for delay in replying but I've just got back to work this week after a break. Yeah that looks fine to me
any chance this can get released?
Hi there, I need to check this as I thought I had. Will get back to you
Thats released now
When running many SQL scripts in the Run Sql Scripts task there is a lack of error information.
Most other tasks in this library have an appropriate catch block:
But this task does nothing to identify the actual error that occurred:
Simple proposal, we need to capture the error that occurred on each script, even if continuing after error.