0

When Azure function is scaled up to multiple instances, it starts throwing a deadlock exception:

Exception: ('40001', '[40001] [Microsoft][ODBC Driver 17 for SQL Server][SQL Server]Transaction (Process ID 878) was deadlocked on lock | communication buffer resources with another process and has been chosen as the deadlock victim. Rerun the transaction. (1205) (SQLExecDirectW)')

marc_s
  • 732,580
  • 175
  • 1,330
  • 1,459
Akhilesh Jaiswal
  • 227
  • 2
  • 14
  • See if this article will help you create a question with enough details to be answered: https://sqljana.wordpress.com/2020/03/17/sql-server-fix-transaction-process-id-was-deadlocked-on-lock-communication-buffer-resources-with-another-process-and-has-been-chosen-as-the-deadlock-victim-rerun-the-transaction/ – John Hanley Nov 24 '21 at 20:16

1 Answers1

0

In SQL Server, Try with this command. set transaction isolation level read uncommitted;. This isolation level allows dirty reads. One transaction may see uncommitted changes made by some other transaction.

Please check this answer by @Daniel for more details on same.

Also consider this official document1, document2.

Utkarsh Pal
  • 4,079
  • 1
  • 5
  • 14