Both Read Uncommitted and Deadlock Priority Low

Transact-SQL
1

I've seen this code a lot in our department

SET TRANSACTION ISOLATION LEVEL READ UNCOMMITTED
SET DEADLOCK_PRIORITY LOW

SELECT ...

If we're in Read Uncommitted doing a Select, aren't Deadlocks impossible? Aside from schema changes of course.

These are for adhoc selects on a Prod DB. So the Read Uncommitted is OK, but having both of these statements doesn't make sense to me.

2

Other task could still hold table locks too. Deadlocks are possible, although extremely rare. The LOW priority still makes perfect sense, since if a deadlock did come up, you would still want to make absolutely sure this is the task that gets killed.