Main Topics
Browse All TopicsI need to drop a table inside a stored procedure in Sybase and then re-create the table, populate it and then build indexes on it. This table needs to be present after the stored procedure finishes. I have the test code below which runs fine during the first pass, but the second time it is invoked I get the following error:
There is already an object named 'myTable' in the database.
It seems that the table is not dropped when the procedure is invoked. I'm quite new to databases field and would appreciate any help on getting this to work. Thanks.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Alternatively, you can put the create and drop in dynamic SQL; viz:
create proc myProc
as begin
declare @sql varchar(1000)
select @sql = "if object_id('myTable') != null drop table myTable"
exec (@sql)
select @sql = "create table myTable (a int null, b char null, c flat null)"table myTable"
exec (@sql)
select @sql = "create index ix_a on myTable (a)"
exec (@sql)
end -- proc
go
Business Accounts
Answer for Membership
by: Jan_FranekPosted on 2009-09-03 at 06:24:58ID: 25250383
Yes, this is how it works, but I'm not quite sure why. Probably compiler checks for existency of used object before running the procedure.
Try to put your create table statement into separate procedure a call this new procedure from your mySP. This should work around your problem.