[13.0.53 Beta] - Query Error resulting in SA Error

	SysOp wrote:
	I recommend disabling the SQL Assistant's automatic Syntax Check and Automatic Performance Analysis features for SSMS target, because they do lead to collisions. these features are best used with SQL Assistant IDE.

IF Vitaly, posting above has disabled the auto syntax checker and still gets script errors percolating up to the .net exception bubbles, I can't say I'm expecting this to fix it.

Why was this not an issue in v12?

I turned off automatic syntax checking and can still get errors to bubble up to the .NET level from SSMS.

Quick video:

https://youtu.be/EuJRNrYHnFo

Code:

4/10/2025 8:24:34 AM SnippingTool.exe SA=13.0.56; Exe=C:\Program Files\WindowsApps\Microsoft.ScreenSketch_11.2502.18.0_x64__8wekyb3d8bbwe\SnippingTool\SnippingTool.exe; Cmd="C:\Program Files\WindowsApps\Microsoft.ScreenSketch_11.2502.18.0_x64__8wekyb3d8bbwe\SnippingTool\SnippingTool.exe" ; LogLvl=1; MsgLvl=0; Module=C:\Program Files (x86)\SQL Assistant 13\bin64\SqlAssist.dll; ImageBase=0000000008080000
4/10/2025 8:24:34 AM SnippingTool.exe Client: Attach
4/10/2025 8:24:58 AM Ssms.exe Error: Msg 102, Level 15, State 1, Incorrect syntax near '.'.: .NET Exception

IF (@@version LIKE '%SQL Server 20%' AND @@version NOT LIKE '%SQL Server 2000%')
or @@version like '%SQL Azure%'
EXEC ('select
SERVERPROPERTY(''ServerName''),
SYSTEM_USER,
DB_NAME(),
ISNULL(SCHEMA_NAME(), ''dbo'')')
else
EXEC ('select
SERVERPROPERTY(''ServerName''),
SYSTEM_USER,
DB_NAME(),
ISNULL(USER_NAME(), ''dbo'')')
Msg 102, Level 15, State 1, Incorrect syntax near '.'.: .NET Exception

IF (@@version LIKE '%SQL Server 20%' AND @@version NOT LIKE '%SQL Server 2000%')
or @@version like '%SQL Azure%'
EXEC ('select
SERVERPROPERTY(''ServerName''),
SYSTEM_USER,
DB_NAME(),
ISNULL(SCHEMA_NAME(), ''dbo'')')
else
EXEC ('select
SERVERPROPERTY(''ServerName''),
SYSTEM_USER,
DB_NAME(),
ISNULL(USER_NAME(), ''dbo'')')
Msg 102, Level 15, State 1, Incorrect syntax near '.'.: .NET Exception

IF (@@version LIKE '%SQL Server 20%' AND @@version NOT LIKE '%SQL Server 2000%')
or @@version like '%SQL Azure%'
EXEC ('select
SERVERPROPERTY(''ServerName''),
SYSTEM_USER,
DB_NAME(),
ISNULL(SCHEMA_NAME(), ''dbo'')')
else
EXEC ('select
SERVERPROPERTY(''ServerName''),
SYSTEM_USER,
DB_NAME(),
ISNULL(USER_NAME(), ''dbo'')')
Msg 102, Level 15, State 1, Incorrect syntax near '.'.: .NET Exception

IF (@@version LIKE '%SQL Server 20%' AND @@version NOT LIKE '%SQL Server 2000%')
or @@version like '%SQL Azure%'
EXEC ('select
SERVERPROPERTY(''ServerName''),
SYSTEM_USER,
DB_NAME(),
ISNULL(SCHEMA_NAME(), ''dbo'')')
else
EXEC ('select
SERVERPROPERTY(''ServerName''),
SYSTEM_USER,
DB_NAME(),
ISNULL(USER_NAME(), ''dbo'')')
Msg 102, Level 15, State 1, Incorrect syntax near '.'.: .NET Exception

IF (@@version LIKE '%SQL Server 20%' AND @@version NOT LIKE '%SQL Server 2000%')
or @@version like '%SQL Azure%'
EXEC ('select
SERVERPROPERTY(''ServerName''),
SYSTEM_USER,
DB_NAME(),
ISNULL(SCHEMA_NAME(), ''dbo'')')
else
EXEC ('select
SERVERPROPERTY(''ServerName''),
SYSTEM_USER,
DB_NAME(),
ISNULL(USER_NAME(), ''dbo'')')
Msg 102, Level 15, State 1, Incorrect syntax near '.'.: .NET Exception

IF (@@version LIKE '%SQL Server 20%' AND @@version NOT LIKE '%SQL Server 2000%')
or @@version like '%SQL Azure%'
EXEC ('select
SERVERPROPERTY(''ServerName''),
SYSTEM_USER,
DB_NAME(),
ISNULL(SCHEMA_NAME(), ''dbo'')')
else
EXEC ('select
SERVERPROPERTY(''ServerName''),
SYSTEM_USER,
DB_NAME(),
ISNULL(USER_NAME(), ''dbo'')')
4/10/2025 8:25:20 AM SqlAssist.exe fmPrefs: Release
4/10/2025 8:25:20 AM SqlAssist.exe fmPrefs: Destroy

There is also background performance analyzer option that you can turn off.
DB Options tab -> SQL Server -> Performance Analysis section -> all 3 analysis options can be changed to No.

But please be aware this is not by target editor, turning them off impacts all targets, and disable its working in SQL Assistant IDE and other editors too.

	SysOp wrote:
	There is also background performance analyzer option that you can turn off. DB Options tab -> SQL Server -> Performance Analysis section -> all 3 analysis options can be changed to No. But please be aware this is not by target editor, turning them off impacts all targets, and disable its working in SQL Assistant IDE and other editors too.

One of those is already turned off (Analyze Query Performance).

I don't recall this being an issue with SQL Assistant 12 to this extent. I really feel like something got changed and a bug has manifested itself.

Do you have a link where I can snag the last version of 12.x? I might reload it just to see if I can get it to behave.

edit: I turned off the other two performance analyzers and still can get a .NET bubble.

ALSO: It seems I lose my SQLA toolbar in SSMS when these exceptions occur.

Well, there might be other differences too. Perhaps you no longer use the same old SSMS, the same old ADO.NET SQL client, or the same old .NET. Perhaps the SQL Server has been upgraded as well. The database may also be slower today than it was a few years ago as it grows in size. And in SQL Assistant v13, there are additional internal moving parts too. The underlying issue lies in multithreading and a lack of coordination. The add-on shares the database connection with its host. It runs a few background processes when the user appears idle. A collision occurs if SSMS is awakened during that time and sends a query to the database. That results in a collision, as multiple threads cannot use the same connection simultaneously. Slowness in the background processes can lead to more frequent collisions.

Unlike SSMS and few other tools, SQL Assistant's addons don't share connections with their hosts, and its not an issue for them. In SQL Assistant IDE its not an issue too, all processes work together and able to communicate with each other, wait if needed, queue requests if needed.

All fair points, it just seems something can be done about it.

I'll try to use the SQLA Editor more next week so I can reproduce the exceptions. The database server hasn't changed, growth is moderate. SSMS is newer, from memory....