title: #Table in SQL server data integrity?
body: <blockquote>
    <p><strong>Possible Duplicate:</strong><br>
    <a href="https://stackoverflow.com/questions/2920836/local-and-global-temporary-table-in-sql-server">Local and Global temporary table in SQL SERVER</a>  </p>
  </blockquote>
  
  
  
  <p>I would like to know if anyone out there can give me a better explanation on the workings of #tables in SQL.</p>
  
  <p>In one of our stored procedures, we create a temp table (#table), wherein data is stored by the currently active stored procedure. Lets call this <strong>Sproc1</strong> for arguments sake.</p>
  
  <p>Sproc1 is called by <strong>sproc2</strong>. After the call, sproc2 collects the data from the #table and then drops the #table, since it will no longer be needed.</p>
  
  <p>That all works well in theory, but what if two or twenty people were to call / execute sproc2 at the exact same time? </p>
  
  <p>So, I'd like to know whether SQL will create a new instance (linked by connection) of the #table for every caller using sproc2 or will there be a conflict?</p>