How to delete a local temp table

Question

Post reply

How to delete a local temp table

Ryan-209402

Hall of Fame

Points: 3707
More actions
June 20, 2007 at 10:06 am

#174098

I'm creating a local temp table for storing data like this:
CREATE TABLE #fileexist ([File Exists] int, [File is a Directory] int, [Parent Directory Exists] int)
However, I often get an error stating "There is already an object named '#fileexist' in the database". Therefor, I would like to do a IF EXISTS statement prior to creating the table to to drop it and suppress any error message, like this:
IF EXISTS (SELECT whatever...)
DROP TABLE #fileexist
CREATE TABLE #fileexist ([File Exists] int, [File is a Directory] int, [Parent Directory Exists] int)
Is there a way to do something like this? The actual table is virtual and only is visible to the current scope (doesn't show up in tempdb). Thanks for any advice you can offer!

Viewing 5 posts - 1 through 4 (of 4 total)

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

Ken McKelvey SSCoach Points: 18856 More actions · Answer 1

IF OBJECT_ID('tempdb..#TableExist') IS NOT NULL

TRUNCATE TABLE #TableExist

Ryan-209402 Hall of Fame Points: 3707 More actions · Answer 2

Thanks for your response. I'm getting some weird error messages. When I try to drop the table I get "Cannot drop the table '#fileexist', because it does not exist or you do not have permission" I am logged in as SA.

When I try to create the table I still get the error "There is already an object named '#fileexist' in the database".

So I'm getting contradicting messages. Any ideas? Thanks.

Mark Shvarts 1 SSCertifiable Points: 5702 More actions · Answer 3

begin try

drop table #test

end try

begin catch

end catch

create table #test(c1 int)

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

IF OBJECT_ID('TempDB..#FileExist') IS NOT NULL

DROP TABLE #FileExist

Make sure the name of the table is correct.

--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)