When not to use a temporary table?

Question

When not to use a temporary table?

Viewing 4 posts - 16 through 18 (of 18 total)

You must be logged in to reply to this topic. Login to reply

Dan.Humphries SSChampion Points: 12125 More actions · Answer 1

I was not so much disagreeing with you as much as I was challenging my own belief. The tempdb is a very useful tool and I am guilty of using it more than I probably should but the idea of filling my tempdb with 20 million records makes me break out in a cold sweat. I was not 100% sure though if that was my paranoid personality kicking in or if that was a justified sweat.

Great discussion though thanks for tolerating my rantings.

Dan

If only I could snap my figures and have all the correct indexes apear and the buffer clean and.... Start day dream here.

velsy.thomas Newbie Points: 7 More actions · Answer 2

Hi All,

Iam using a global temporary table and iam facing performance issue.

Please let me know how to solve the performance issue with teh global temporary table.

Please help me..

Viva

Gail Shaw SSC Guru Points: 1004504 More actions · Answer 3

Please post new questions in a new thread. Thank you.

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Jeff Moden SSC Guru Points: 1004340 More actions · Answer 4

velsy.thomas (8/2/2010)
Hi All,
Iam using a global temporary table and iam facing performance issue.
Please let me know how to solve the performance issue with teh global temporary table.
Please help me..
Viva

I second Gail's recommendation and I'll also add that you should read the article at the 2nd link in my signature below before you ask a performance question because the way you asked the question will likely only get you the simple answer of "fix your slow code" or a link to how to post performance problems. 😉

--Jeff Moden

RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

Change is inevitable... Change for the better is not.

Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)