title: SQL Server: VIEW with NO LOCK but called without NO LOCK
body: <p>I am on Microsoft SQL Server 2016 and I have the following (simplified) query that references a view:</p>
  <pre><code>SELECT Column1
  FROM dbo.myView
  </code></pre>
  <p>The view looks as follows:</p>
  <pre><code>CREATE VIEW dbo.myView
  AS
  SELECT Column1
  FROM dbo.SomeOtherTable WITH (NOLOCK)
  </code></pre>
  <p><strong>My question now is:</strong> Does the fact that the outer SELECT does <em>not</em> use the NOLOCK table hint imply that the NOLOCK inside the VIEW is irrelevant? Or will the NOLOCK still be relevant when executing the outer SELECT?</p>
  <p>The bigger context of my question is that I had a case where I was analyzing a blocking situation on a server. I found a query such as the SELECT described above: A SELECT query was using a VIEW. The VIEW was using a NOLOCK table hint, but the outer SELECT did not. Still, the query was a head blocker and I am trying to identify the reason for this.</p>
  <p>I already did some research and the only confirmation I could find is for the questions where people want to know if a <code>NOLOCK</code> is propagated down to the inner tables.</p>