rather than running a drop statement, call a stored procedure which does the drop. Inside the stored procedure check table exists before it drops it. If you have table to be dropped as a parameter passed into procedure you can re-use the procedure to drop other tables if needed in future.
I’m newbie enough that I can’t use either of those tips without some deep study and invention.
Numerous examples are in the Programming: SQL topic of the Information Center.
It's difficult to give useful examples -- a normal assumption would be that someone hired as a developer should already know SQL.
Giving SQL examples without including the fundamentals can be risky. It's impossible to know how long an answer should be. Technically, the answer ought to be as long as a reference manual.
But perhaps you're not a developer. You might be a user trying to get a task done without benefit of a development staff. Then how much should an answer about DROP TABLE include?
Or perhaps you are experienced in what Microsoft refers to as "SQL"? If so, then pointing you to the reference manuals and the Information Center is the answer that you need for now.
Tom
Free Guide: Managing storage for virtual environments
Complete a brief survey to get a complimentary 70-page whitepaper featuring the best methods and solutions for your virtual environment, as well as hypervisor-specific management advice from TechTarget experts. Don’t miss out on this exclusive content!
23,730 pts.
Discuss This Question: 4 Replies