title: Order of (nolock) and table aliases on SQL Server
body: <p>So I've got a SQL statement that pared down looks something like this:</p>
  
  <pre><code>SELECT column
  FROM table t (nolock)
  LEFT OUTER JOIN table2 (nolock) t2 on t.id = t2.id
  </code></pre>
  
  <p>This statement works on my SQL 2005 and SQL 2008 environments. It does not on a remote SQL 2005 environment. I've switched the last line to:</p>
  
  <pre><code>LEFT OUTER JOIN table2 t2 (nolock) on t.id = t2.id
  </code></pre>
  
  <p>This works in the remote environment.</p>
  
  <p>Putting aside issues of whether (nolock) is appropriate and that the syntax should remain internally consistent, any ideas why this happens? I attempted to search for hotfixes/KBs that dealt with this and came up with nothing. Is there a setting on SQL server that could cause this behavior?</p>