Bug: Multiple sql statements randomly fails

[mikegreen]

Describe the bug

Describe the bug
When I run the below, which is valid SQL, I get an error.

To Reproduce
This sql:

UPDATE tblDocuments SET DocumentTypeID = 3047 WHERE DocumentID = 5296445;
UPDATE tblDocuments SET DocumentTypeID = 3047 WHERE DocumentID = 5294620;
UPDATE tblDocuments SET DocumentTypeID = 3036 WHERE DocumentID = 5275406;
UPDATE tblDocuments SET DocumentTypeID = 3047 WHERE DocumentID = 5268630;
UPDATE tblDocuments SET DocumentTypeID = 3047 WHERE DocumentID = 5608449;
UPDATE tblDocuments SET DocumentTypeID = 3047 WHERE DocumentID = 5608450;
UPDATE tblDocuments SET DocumentTypeID = 3047 WHERE DocumentID = 5608493;
UPDATE tblDocuments SET DocumentTypeID = 3047 WHERE DocumentID = 5611079;

Select it all, hit run selected.

Returns:

Initializing connection...
Connection ready. Took 0.026 seconds.

Statement completed successfully. (1 rows affected). 0.000 seconds. (Line 1).
Statement completed successfully. (1 rows affected). 0.000 seconds. (Line 2).
Statement completed successfully. (1 rows affected). 0.000 seconds. (Line 3).
Statement completed successfully. (1 rows affected). 0.000 seconds. (Line 4).
Statement completed successfully. (1 rows affected). 0.000 seconds. (Line 5).
Statement completed successfully. (1 rows affected). 0.000 seconds. (Line 6).
Msg 102, Level 15, State 1.
Incorrect syntax near '='. 0.000 seconds. (Line 7).

Finished. Total time: 0.077 seconds.

If I run them one by one, or in blocks of 6 it works. But over 7 it fails...

Expected behavior
It would run all of them.

Screenshots
If applicable, add screenshots to help explain your problem.

Additional details
Enter any additional details we should know about.

Product

SQLPro Studio

App version

Version 2025.91 (Build 115613.5)

Platform

macOS

Installation source

App Store

[hankinsoft]

Sorry for the issue. A couple of questions:

Which type of database are you running against? MySQL, Postgres, etc?
If you run that line on its own, does it error out or work properly?

[mikegreen]

Its a Azure SQL Server DB.

When run on their own, or in chunks of less than 5 rows, it works fine.

Also the entire block works in SSMS... really odd..

[hankinsoft]

Hmm, ok and if you open preferences and switch 'Execute query in cursor range' to 'Enabled (default)', then move your cursor around through the different queries does it light up each query individually as expected?

As shown here:

Or does it partially select those last queries?

Also:

App version
Version 2025.91 (Build 115613.5)

Could you update to the latest version (2026.05) as that may sort the issue itself.