Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>try this query to see blocking processes, including the actual SQL query text:</p> <pre><code>SELECT r.session_id AS spid ,r.cpu_time,r.reads,r.writes,r.logical_reads ,r.blocking_session_id AS BlockingSPID ,LEFT(OBJECT_NAME(st.objectid, st.dbid),50) AS ShortObjectName ,LEFT(DB_NAME(r.database_id),50) AS DatabaseName ,s.program_name ,s.login_name ,OBJECT_NAME(st.objectid, st.dbid) AS ObjectName ,SUBSTRING(st.text, (r.statement_start_offset/2)+1,( (CASE r.statement_end_offset WHEN -1 THEN DATALENGTH(st.text) ELSE r.statement_end_offset END - r.statement_start_offset )/2 ) + 1 ) AS SQLText FROM sys.dm_exec_requests r JOIN sys.dm_exec_sessions s ON r.session_id = s.session_id CROSS APPLY sys.dm_exec_sql_text (sql_handle) st --WHERE r.session_id!=@@SPID --uncomment to not see this query </code></pre> <p>deadlocks are easily trapped with the profiler:</p> <p>Try running the run a trace in the profiler (pick the blank template), select the "deadlock graph event", and on the new tab that appears (Events Extraction Settings), save each (check "save deadlock XML events separately") in its own file. Open this file in an xml viewer and it will be easy to tell what is happening. Each process is contained, with an execution stack of procedure/trigger/etc calls, etc. and all locks are in there too.</p> <p>Look at the "resource list" section of the file, it will show what is being locked and held by each process causing the deadlock. Figure out how to not have one of these locked and the deadlock will be resolved.</p> <p>Let this trace run until the deadlock happens again, info is only recorded when a deadlock happens, so there isn't much overhead. If it never happens again, good it is solved, if not you have captured all the info.</p>
    singulars
    1. This table or related slice is empty.
    1. POSQl statement to monitor Sql Server Locks
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USKM.
    1. USKM.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload