We are having issues with deadlocks and I am trying to isolate what database object is causing the problem.
I found Deadlock error isn't returning the deadlock SQL to be very helpful and I read through a lot of the MSDN stuff. I set up a trace and now have a deadlock graph but I am having a hard time reading it. I know it's a page lock, and in the page lock box on the graph I have a DB_ID (great! told me the database), File ID, Page ID, and associated objid. I can't seem to use these IDs to dig any deeper.
My sense is that simple SELECT queries are getting victimized by our replication process (as appropriate), but I need to know the specifics in order to fix the problem - the majority of our queries relies upon views that may need to be modified.
EDIT: I should have kept looking... SQL Server Deadlock Graph - Table, Page or Row Lock? may solve my issue. I'm going to continue to work on it - and might remove this question...