Thanks Justin. One of our queries ran for 599 seconds, so probably the deadlock timeout was the only reason it died. Aside from optimizing app groups and such, is there a way to timeout queries after say 60 seconds? I'm just thinking worst-case scenario, where we are not able to optimize 100% of our queries. Of course, we are always striving to optimize as much as possible, but there's always something that sneaks through! So the timeout would be our catch-all.
Since most clients typically timeout after 60 seconds anyway, a database query should take no longer than that.