[13.0.53 Beta] - Messages filtering issues

[13.0.53 Beta] - Messages filtering issues

I am having trouble understanding how the filtering in the Messages pane is supposed to work. It seems a bit chaotic to me.

Check out this short video >>>here<<<. I attempt to filter various entries using different filters with varying degrees of success. Some filters work as expected, while others do not work at all.

It appears that the filter is case-sensitive and I've failed to find a way to turn that off. For example, when I type the filter "UPDATE," it works as expected until I mistype "SET." After entering "SEt," the list becomes empty. However, when I try to filter on "DELETE," the list is empty when I type "DE." Strangely, on the next execution, filtering on "DELETE" works correctly.

In addition, some messages are simply missing. The messages in the video were generated by a stored procedure that uses a cursor to perform various tasks and reports its progress using RAISERROR. At the end of each iteration of the cursor, there is a "commit transaction" message for successful execution or an error message for failure. Despite there being no errors, the expected message for the commit is missing for every execution I've tried (5 times), but only for the last iteration of the cursor. The preceding message with the status update on the number of rows deleted is also missing. When I execute the same query in SQL Server Management Studio without SA, the Messages pane contains all the expected messages in plain text. However, these messages are in plain text, and unfilterable, so that's as useless as it gets. Yet everything is there.

Thank you very much. We investigated this issue. Turns out it's not the filtering function finding wrong or not finding correct items. The weird behavior is caused by the display issue. For performance reasons, the rendering of messages and similar things is optimized to show only messages it calculates visible based on the pane's scroll position and the view port. Filtering upsets that calculation performed earlier in the process, as a result not all expected messages get rendered in the visible area of the pain. To see that impact, scroll the Messages pane scroll it to the very top and then try the same filter. What will appear on the screen is going to change, and after a few of filter changes, it 's going to difficult to explain the results.

We are certainly going to fix this issue, but it's unlikely the fix is going to make to v13 initial release expected next week.

A quick update, it looks like the fix for this issue is going to make to the release version expected on Monday

Thanks, that's great news!