未归入特定类别的其他 SQL Server 功能和主题
Hi @eric zhao ,
Thanks for reaching out to SQL Q&A Forum
Even though SELECT queries don’t modify data, they can still participate in deadlocks in SQL Server. This happens because SELECT acquires shared locks under the default isolation level, which may conflict with exclusive locks from concurrent UPDATE or INSERT operations. When multiple transactions hold locks that the other needs, SQL Server detects a cycle and chooses one query as the deadlock victim — often the SELECT. To reduce these conflicts, you can consider options like adding appropriate indexes, using snapshot isolation (row versioning), or reviewing query design to ensure consistent access order across tables. Capturing a deadlock graph will help identify the exact queries and resources involved.
Thanks,
Lakshmi.