http://blogs.msdn.com/b/sqlserverfaq/archive/2012/03/15/an-interesting-find-about-temp-tables-in-sql-server.aspxI ran into a very interesting issue with temp tables recently, when working on a case. The issue description goes something like this. We have an application preparing some SQL statements, and sending them to the SQL Database engine for execution. Howeveren-USTelligent Evolution Platform Developer Build (Build: 5.6.50428.7875)http://blogs.msdn.com/b/sqlserverfaq/archive/2012/03/15/an-interesting-find-about-temp-tables-in-sql-server.aspx#10328668Wed, 11 Jul 2012 02:56:18 GMT91d46819-8472-40ad-a661-2c78acb4018c:10328668Hugh<p>I found the same thing with normal tables.</p> <p>It only applies to 2005, not 2008.</p> <p>It&#39;s simple enough to recreate.</p> <p>With a table which is already defined, in a batch</p> <p>drop table</p> <p>create table -- with different/new columns</p> <p>insert values.</p> <p>Once I create the original table in the same batch, the error goes away and even if I remove the create table for that batch, it still works.</p> <div style="clear:both;"></div><img src="http://blogs.msdn.com/aggbug.aspx?PostID=10328668" width="1" height="1">http://blogs.msdn.com/b/sqlserverfaq/archive/2012/03/15/an-interesting-find-about-temp-tables-in-sql-server.aspx#10291139Thu, 05 Apr 2012 15:16:49 GMT91d46819-8472-40ad-a661-2c78acb4018c:10291139Manish<p>Thanks for sharing this detailed information Harsh.</p> <p>Thanks</p> <p>Manish</p> <div style="clear:both;"></div><img src="http://blogs.msdn.com/aggbug.aspx?PostID=10291139" width="1" height="1">