Database Corruption (Please help!)

Hi,
I created a nonclustered index on sysobjects table. After that, when I
create a new object and sysobjects is modified, the database does not work
properly. I used DBCC CHECKDB to repair it. It works but as soon as a new
object is created, again database get corrupted (CHECKDB reports error). I
cannot drop this index with DROP INDEX command.
I'm wondered if an index on system table cannot be dropped, why it can be
created? If it is allowed to create index, why it corrupts the database?
I found this link:
http://support.microsoft.com/kb/106122
Although it mentions SP_FixIndex can drop such indexes but there are no description about it.
Any help would be greatly appreciated.
LeilaToday's lesson: "Don't f*** with system tables."|||Any solution?!..|||You may be able to drop the index if you run the SET OPTION command to allow changed to system objects.
Make sure you execute the command to disallow changes when you are done!|||It doesn't allow to drop index from system tables|||Did you try the SET OPTION command?
Otherwise, create a new blank database and copy your production tables to it, and then drop the old database with its corrupted system table.