Comments on: Temp Table Performance Tuning Tips http://www.sql-server-performance.com/2004/temp-table-tuning/ SQL Server Performance Tuning Fri, 14 Jun 2013 19:09:55 +0000 hourly 1 http://wordpress.org/?v=3.5.1 By: Dariusz Spiewak http://www.sql-server-performance.com/2004/temp-table-tuning/#comment-1399 Dariusz Spiewak Tue, 21 Feb 2012 23:10:27 +0000 http://www.sql-server-performance.com/?=1021#comment-1399 Louis, if you let the table stay in tempdb for the duration of the procedure and if this procedure takes some considerable time to run to completion, all the data in the table will be stored in tempdb and taking space for no reason. Easy as that. Dropping it as soon as possible at least releases space. This probably doesn’t matter if the proc runs within seconds or less but might be a problem otherwise.

]]> By: Louis R. http://www.sql-server-performance.com/2004/temp-table-tuning/#comment-440 Louis R. Thu, 07 Jul 2011 19:11:12 +0000 http://www.sql-server-performance.com/?=1021#comment-440 A lot of the tips in this page are actually pretty bad.

As an example, a SELECT INTO will usually offer a better performance because it is a bulk operation. I would be curious to know exactly what “system objects” are locked during this operation.

Also in order to maximize performance it is better NOT to drop a temporary table and to just let it run out of scope. The end result will be the same (table won’t exist anymore) but if you drop it inside your session then the transaction stays open until the delete is completed, while letting the table run out of scope will just flag it for removal and let the engine deal with it without holding the transaction.

]]>