Help: Can't drop corrup table (error 1117)

Help: Can't drop corrup table (error 1117)

Post by Martij » Tue, 18 Nov 1997 04:00:00

[SQL server 6.5 sp3  NT 4 sp3]

When I try to drop a corrupt table I get this message:

"Error 1117: [SQL Server] Extent chain for object 111827028 is not
correctly linked."

Is ther a other way to drop the table?

Thanks in advance...



Help: Can't drop corrup table (error 1117)

Post by steve Robinso » Tue, 18 Nov 1997 04:00:00


Yes but its very messy.

Can you rename the table and truncate/ delete the data from it.  You may be
better off just leaving it at that.  
The way around this though is

Remove all entries of the table from the system tables.
Run dbcc newalloc - this will tell you that there are space allocated but
not used.
Run Dbcc Fixal - This will reclaim the unused space and correct the problem

I would recommend doing a full dbcc check before any of this though and if
there are any other problems it may be better to stick with the rename or
restore from the last backup.

I hope this was of use.

Steve Robinson


1. SQL Server 6.5 - Table Index corrupt - Errors 1117 (2541, 2504, 2543)

Problem :
I have a table and one index seems to be corrupt (Production-DB)
("index-id in reservation-page does not correspond to index in sysindexes")

-> DBCC NEWALLOC  reports Errors 2541, 2504 and 2543
-> attempts to repair index with DBCC REINDEX or DBCC  FIX_AL fail
-> attempts to drop the index or the whole table fail with Error 1117
-> error is also in backup-copy

How can i correct this error ?

Thanks in advance
Alois Stoll

2. Informix DBAs, Developers

3. PRODUCTION EMERGENCY - Help with 605/1117 errors

4. GQL Date Format

5. Error 1117 - Extent chain not correctly linked

6. Setting up replication over the internet

7. System error 1117

8. Access Jet with Delphi 1.0?

9. Tape backup Error Status 1117

10. Error 1117

11. Error 1117 - Extent chain not correctly linked

12. Fatal Error 1117

13. Native SQL Server Backups using Tape - Error 1117