Thank you for your responses. We will look into the suggestions posted above to see if there is a way to recode this, and will come back to you.

Jonathan AC Reports - is HOLDLOCK not equivalent to the highest isolation level of SERIALIZABLE?

https://bobpusateri.com/2023/08/holdlock-serializable/

Fair point on the ROLLBACK, although it would close the BEGIN TRANSACTION (rather than leaving it open). @ReferenceNumber is used lower down.

SELECT @ReferenceNumber = ISNULL(@ReferenceNoPrefix, N'') +...

I am pleased to confirm that the solution provided by Jeffrey Williams has solved the issue for us. The modified code has been live for a few days now, and...

Thank you all very much for your suggestions. We are reviewing this to see how best to proceed. Will provide feedback on how this progresses.

@scottpletcher - correct, no missing indexes were identified. Only the second query returned results.

Thanks all. I can confirm that the code is not being called in a loop, or in an explicit transaction. The parent procedure sproc_ValidateUser just performs some basic...

Removing duplicate comment. See below.

• This reply was modified 1 year ago by  zoggling.
• This reply was modified 1 year ago by  zoggling.

@scottpletcher - apologies for the delay in responding to your post. Please find the requested results of running your script attached. Please let me know what you think,...

Many thanks Steve, this does appear to have been resolved in the latest patches that were pushed out by Microsoft this month.

I am struggling to identify which specific KB or...

• This reply was modified 1 year, 1 month ago by  zoggling.

Thanks all. I can confirm that the code is not being called in a loop, or in an explicit transaction. The parent procedure sproc_ValidateUser just performs some basic validation and...

I have already tried all of the above against one of our DEV servers (including multiple versions of ODBC DLLs).

There is currently no solution, and no word from Microsoft on...

• This reply was modified 1 year, 1 month ago by  zoggling.

At the start of this ticket, we were on ODBC driver 13.3.6430.49 and had had all the latest cumulative updates installed in sequence.

The Microsoft "Security Vulnerability" pages themselves state that...

@ken McKelvey - this has not solved the issue for us unfortunately.

We already had ODBC 17.10.4.1 installed, and upgraded from ODBC 18.2.2.1 to ODBC 18.3.1.1 as suggested in...

• This reply was modified 1 year, 2 months ago by  zoggling.
• This reply was modified 1 year, 2 months ago by  zoggling.

Is there anyone from Microsoft who can please add this to the bug list as a high priority?