SA: 13.5.73 - Messages pane

SA: 13.5.73 - Messages pane

I've brought this up before, but something is really amiss here.

I can have a query in SSMS:

	Code:
	SELECT ,,

Pressing Ctrl+F9 will say the syntax check is complete. (no errors)

Executing that same code in SSMS
tells me

	Code:
	Msg 102, Level 15, State 1, Line 1 Incorrect syntax near ','.

The same code in SQL Editor tells me:

	Code:
	Msg 102, Level 15, State 1, Incorrect syntax near ','....

No matter if it's executing the code OR running a syntax check.

Code:

SQL Server Management Studio                21.5.14+6.36429.23
SQL Server Management Objects (SMO)                17.100.73.0+e183799e249c9bb0ba9f7e74c4e23007e11dabd7
Microsoft T-SQL Parser                17.2.22.0+0df7893883f565f6d690e7272ae7e1b5e7872b2b.0df7893883f565f6d690e7272ae7e1b5e7872b2b
Microsoft Analysis Services Client Tools                21.0.52.0
Microsoft Data SqlClient (MDS)                5.1.6
Microsoft SQL Server Data-Tier Application Framework (DacFX)                170.0.96.2+38131d374cd6c4991a9ada0c74d79de3392fda0b
Microsoft .NET Framework                4.0.30319.42000
Operating System                10.0.26100

I think still related to this:

https://www.softtreetech.com/support/phpBB2/viewtopic.php?t=26000&postdays=0&postorder=asc&start=0

But regardless if I just use CTRL+SHIFT+F9 without ever using F5 in SSMS, the errors never get printed. SELECT 1/0 and CTRL+SHIFT+F9 produces:

	Code:
	Executing selected queries... Please wait or close this tab to cancel execution. 0 rows fetched (1.94 ms). The command(s) completed successfully at 1:13:11 PM (1.95 ms).

Could you please share which SQL Client version is used in SSMS? Version can be found in the Help/About.

	SysOp wrote:
	Could you please share which SQL Client version is used in SSMS? Version can be found in the Help/About.

Is that in the last codeblock I posted in the first post?

Tested with SSMS 18.12.1 bundled with MDAC 10.0. Result: Line 1 Incorrect syntax near ','.

Tested with SSMS 19.1.56 bundled with MDAC 10.0. Result: Line 1 Incorrect syntax near ','.

Tested with SSMS 20.2.37 bundled with MS SqlClient (MDS) 5.1.5. Result: Line 1 Incorrect syntax near ','.

Tested with SSMS 21.5.14 bundled with MS SqlClient (MDS) 5.1.6: Result: The Syntax Check is Complete - message box, which is shown when no issues detected.

SASE 64-bit appears to utilize SQLClient 5.1.6 too, .NET finds the latest version installed, while SASE 32-bit gets 5.1.5. I can't explain why (that's inside .NET, not explicitly specified). But at least it matches SSMS 20/21, which is what important for us here. In both cases SASE executes SQL code directly with syntax-check option in syntax check mode, and receives responses from the SQL Server directly. In case of SSMS add-on, the mechanism is different because the connection is shared and owned by SSMS. The add-on subscribes to internal message notifications mechanism from SQLNet client and expects to be notified on all such messages. It looks like something is different in MDS 5.1.6 that impacts the add-on, it doesn't get the syntax check messages as that used to work in the previous versions. That impacts code execution too, in case of errors the add-on doesn't get notified of errors. If there are no errors, everything seems to work the same, code is executed and results are returned without a visible difference. This requires more investigations to find out what has changed in 5.1.6.

Our internal investigation has found out that one of the functions which we haven't updated in SSMS 2025 add-on version still depends indirectly on System.Data.SqlClient assemblies while in SSMS 2025 Microsoft switched internally to Microsoft.Data.SqlClient. We will have that fixed in SQL Assistant 14.

	SysOp wrote:
	Our internal investigation has found out that one of the functions which we haven't updated in SSMS 2025 add-on version still depends indirectly on System.Data.SqlClient assemblies while in SSMS 2025 Microsoft switched internally to Microsoft.Data.SqlClient. We will have that fixed in SQL Assistant 14.

Thank you. Is there an ETA on v14?

Tentatively before end of the year. No specific date is known yet.

I know you've been struggling with the SqlClient.

Microsoft just released SSMS 22.3 with a note about SqlClient changes breaking many third party tools:
https://techcommunity.microsoft.com/blog/sqlserver/announcing-database-instructions-and-a-lot-of-fixes-in-sql-server-management-stu/4494468

Have you had a chance to test this out yet?

Quote:

In this release we also updated to later releases of Microsoft.Data.SqlClient (MDS) and SQL Management Objects (SMO). While these updates are invisible and foundational to core SSMS functionality, they are quite impactful to components like third-party extensions that have dependencies on them. We are aware that SSMS 22.3 does not work when certain third-party extensions are installed, and we are following up with extension owners based on feedback items that have already been opened. If you use a third-party extension, be aware this could happen. If you uninstall the third-party extension and the problem no longer occurs in SSMS 22.3, please file a ticket with the extension owner. Have questions about extensions in SSMS, please check out our FAQ.

It looks like that has been fixed in SSMS 22 / SQLClient 5.1.7. Here is my screenshot. Note that this requires SQL Assistant v14 addon for SSMS 22. Tested with beta version.