title: Proving that a query is a blocking issue
body: <p>When running this query, so far there are 4 different results that can occur, but with the most frequency the main result is that it runs for over 10 minutes before I kill it, but around 1% of the time it will return either 2 records or 3 records or no records:</p>
  
  <pre><code>select *
  from [master] as [p]( nolock )
       inner join eddd(nolock) as [e]
       on [p].[guid] = [e].pggg
       inner join stppp as [s]( nolock )
       on [e].[guid] = [s].evggg
       inner join [edddex] as [x]( nolock )
       on [e].[guid] = [x].[guid]
  where [p].[guid] = '370ECB0F-6222-4D02-86DD-336BAAA49B81'
    and ( CAST([s].rddd as date) = '20150821'
       or CAST([s].rddd as date) = '20150821' )
    and [s].[st111num] = 4
    and [e].[ev111type] = 6
    and [x].[l11105] = 6;
  </code></pre>
  
  <p>My friend argues that because removing this filter:</p>
  
  <pre><code>  and ( CAST([s].rddd as date) = '20150821'
       or CAST([s].rddd as date) = '20150821' )
  </code></pre>
  
  <p>causes the query to respond immediately, that this proves this is not a blocking/locking issue. </p>
  
  <p><strong>When having only SELECT access against a specific database and not having the ability to audit or view system tables, how does one find out whether a specific query is returning different results due to locking?</strong></p>