January 16, 2003 at 6:26 am
--- Anyone ever seen this??? ---
I created an index with a pound sign as the first character, thinking to designate as a temporary index. I was only using this index for some perfomance testing. Anyway, when I was done with the index, I tried dropping it, using the index name. Didn't work. Said unrecognized object name... Tried putting square brackets around the name. Same thing... Tried double quotes. Same thing... I looked in Enterprise Manager, and sure enough, there was my new (now not so temporary) index tied to my table. Tried dropping it through Enterprise Manager. Same error in a dialog box. I even went to the system tables and found the object, but it refused to let me delete the index, even after updating options to allow editing systables...
What happened!!!???
January 16, 2003 at 6:49 am
I couldn't re-produce this. The statement
drop index
.[£indexname] executed successfully.
Regards,
Andy Jones
.
January 16, 2003 at 6:53 am
quote:
I couldn't re-produce this. The statementdrop index
.[£indexname] executed successfully.
Regards,
Andy Jones
Sorry, my british friend. I should have specified, the American pound sign (#). 🙂 Next pint's on me...
Cheers.
January 16, 2003 at 7:00 am
Sorry for the error in translation!!
Same thing with the statement: -
drop index
.[#indexname] - this works.
This is on SQL2K what version are you using?
P.S. I'll buy the double cheeseburgers to go with your pint!
Regards,
Andy Jones
.
January 16, 2003 at 7:02 am
This script ran fine on my SQL 2K machine:
create table c (c int)
go
CREATE INDEX #c
ON test.dbo.c
(c)
GO
sp_helpindex c
go
drop index c.#c
go
sp_helpindex c
go
drop table c
[/quote]
Gregory Larsen, DBA
If you looking for SQL Server Examples check out my website at http://www.geocities.com/sqlserverexamples
Gregory A. Larsen, MVP
January 16, 2003 at 7:05 am
I'm on SQL7. Perhaps that's the issue?
January 16, 2003 at 10:25 am
Tried it in SQL 7 and does seem to be an issue there when using # for the name of an index. It looks for it in the table as is treating table.index as owner.temptable instead. However adjusting for that does not fix the problem. In addition found that Dropping the table does release the index and that _ will work without issue.
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply