Hello Jason:
Although Temp tables might come handy sometimes. However, I knew recently that using a table declared as a TABLE Type is much better, especially that you don't need to make sure the temp table is deleted or not, since it will be automatically deleted, here is an example:

DECLARE @TempTable TABLE
(
Id INT,
Name VARCHAR(50)
)

Then you can deal with the table @TempTable similar to any other table, with some limitations, but at least it does what is required from a temp table.

Hope that helps,
Regards

Sometimes a temp table is necessary.  For example, if you are inserting data from executing a sproc.

Example:

INSERT INTO #job_status

EXECUTE master.dbo.xp_sqlagent_enum_jobs 1,'sa', @jobid

Declared table variables suffer a performance hit when dealing with larger (1k records+) datasets in my experience.

Temp tables are still king when dealing with temporary data sets for performance.

Hey, it works gr8!!

Thanks!!

Cheers!!

that was useful! thanks!

I like in memory tables too. If you need to use it in a loop with an identity column where you want to repopulate the in memory table each time thru the loop. Truncate table will not work, and Delete table, doesn't reset the identity. I guess you can calculate it.

thanks dude it works i was finding a lot in server 2000 books.

but i found over here.

again thanks for the help

Cool tip, works a treat, thanks :)

oh, thats what i looking for. thanks alot !