Open CobusKruger opened 5 years ago
Here's a repro test script and example of the behavior:
print 1.0/(floor(cast(datepart(ms,getutcdate()) as int)) / 100) raiserror('Some sort of status message here',0,1) with nowait; raiserror('*** Blah blah',0,1) with nowait; waitfor delay '00:00:00.3' go 60
In SSMS you can see that there are errors somewhere in there even if they're not visible:
Then you can scroll to find them:
But in Azure Data Studio you can't tell there are errors in the mix:
I think there's 2 asks here; @CobusKruger is asking for discoverability on existing errors (that are shown in red in the message output). I think this needs ux/ui input. @yualan
What @vickyharp showed seems to be a different issue that we aren't recognizing "raiseerror" as an error.
Steps to Reproduce: When you run a big script with lots of output, the errors are printed okay, but only in the middle of the output. Unless you either stare at the messages window while it executes or carefully scroll through afterwards, there is actually no hint that there were errors. In SSMS, the message at the bottom says something along the lines of "Completed with errors". That would be good enough already. What would be really excellent, is a list of errors with links to the editor.