12.4.476: Messages Pane doesn't show all errors?

12.4.476: Messages Pane doesn't show all errors?

I'm seeing an oddity with the SQL Asssistant messages pane versus the SSMS messages pane.

I'm working with some temporary tables and occasionally if I am working with a subset of my script and miss the create table part of the script

SSMS's pane will tell me invalid object name 'tablename'
SA's messages pane just gives me a success message.

See image:

If you use both of them to execute the queries, it may result in out of sequence internal code execution

	SysOp wrote:
	If you use both of them to execute the queries, it may result in out of sequence internal code execution

I'm only using the SSMS results pane and execution if I get back a dubious execution result from SQL Assistants execution. Such as the example above, where SQL Assistant didn't warn me about the non existent object.

SQL Editor does as one might expect (gives proper errors).

I closed out SSMS, re-opened it and tried to select * from no_table; and ONLY executed SQL Asisstant's results (Ctrl+Shift+F9) and still got back no error.

Can you please try executing
SELECT SERVERPROPERTY('ServerName'), DB_NAME()

query using both methods? Same result?

	SysOp wrote:
	Can you please try executing SELECT SERVERPROPERTY('ServerName'), DB_NAME() query using both methods? Same result?

Both come back with the appropriate results.

I can also confirm that my laptop at home, VPN connected to the same Server/DB gives me the same results as my desktop at work. Where the SSMS Execution will throw an error but the SQL Assistant one will not.

exec non_existent_stored_procedure; also comes back clean executing with SA, but errors with SSMS.

I suppose SELECT 1/0 too returns no error?

	SysOp wrote:
	I suppose SELECT 1/0 too returns no error?

Correct. But this one also shows me a data tab with a no name column with no result.

I managed to reproduce the same results with 12.4 and SSMS 19. It only occurs within SSMS.

	SysOp wrote:
	I managed to reproduce the same results with 12.4 and SSMS 19. It only occurs within SSMS.

Okay I’m on SSMS 19.3 and the latest sql assistant. I guess there’s some incompatibility?

FYI, I opened an internal ticket to investigate this issue, will keep you posted on the progress.

It turns out the error message firing event regressed after SSMS 19.0 Preview 4 version, after SA add-on for SSMS 19 was already developed.
Fixing that compatibility issue requires code changes in the addon. The issue applies to not yet released add-on for SSMS 20.0 as well.

Last edited by SysOp on Mon Apr 01, 2024 8:49 am; edited 1 time in total

	SysOp wrote:
	It turns out the error message firing event regressed after SSMS 19.0 Preview 4 version, after SA add-on for SSMS 19 was already developed. Fixing that compatibility issue requires code changes in the addon. The issue applies to not yet released add-on for SSMS 20.0.

Thanks for the update. I wonder if I experienced it before because it totally felt like deja-vu when I was trying to figure out what the heck was going on at first.