Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
cgunner
Yak Posting Veteran
95 Posts |
 Posted - 2007-02-01 : 10:40:08
|
| I have ran a DBCC CHECKDB on a database that was suspect because of a drive space issue. I am getting these errors:DBCC results for 'SC_Table'.There are 79 rows in 2 pages for object 'SC_Table'.Server: Msg 8978, Level 16, State 1, Line 1Table error: Object ID 1755153298, index ID 1. Page (1:6107122) is missing a reference from previous page (1:6107110). Possible chain linkage problem.Server: Msg 8978, Level 16, State 1, Line 1Table error: Object ID 1755153298, index ID 1. Page (1:6107124) is missing a reference from previous page (1:6107121). Possible chain linkage problem.DBCC results for 'SC_Table'.I have tried to run DBCC DBREINDEX on the table and the problem was not corrected. I also ran DBCC CHECKDB ('SCDB', REPAIR_REBUILD) with no luck due due to the .mdf filling the entire drive before failing. Does anyone have any suggestions? |
|
|
paulrandal
Yak with Vast SQL Skills
899 Posts |
Posted - 2007-02-01 : 11:54:01
|
| What was the sequence of events that led to the corruption? Running out of space on a drive shouldn't cause a database to become corrupt.If you don't have any space in the database and no room for the database files to grow then the rebuild operation is going to fail.. is this the case?Paul RandalPrincipal Lead Program Manager, Microsoft SQL Server Core Storage Engine(Legalese: This posting is provided "AS IS" with no warranties, and confers no rights.)http://blogs.msdn.com/sqlserverstorageengine/default.aspx |
 |
|
|
cgunner
Yak Posting Veteran
95 Posts |
Posted - 2007-02-01 : 11:57:15
|
| We ran out of space on the drive and the database went suspect. We moved the DB to another drive and got it some space but the checkdb came up with the errors. I tried to reindex the table and than tried to run the REPAIR_REBUILD. The REPAIR_REBUILD grew the DB and we ran out of space again. |
|
|
|
paulrandal
Yak with Vast SQL Skills
899 Posts |
Posted - 2007-02-01 : 13:19:08
|
| ok - so I think the corruption already existed in the database and the running out of space is a red herring. When was the last time you ran checkdb before running out of space?The rebuild will continue to fail until you give the database enough disk space - to rebuild a 100GB index, you need 120GB of *extra* database file space because we need to build the new index before dropping the old index (the extra 20% of space is for the sort operation).ThanksPaul RandalPrincipal Lead Program Manager, Microsoft SQL Server Core Storage Engine(Legalese: This posting is provided "AS IS" with no warranties, and confers no rights.)http://blogs.msdn.com/sqlserverstorageengine/default.aspx |
|
|
|
cgunner
Yak Posting Veteran
95 Posts |
Posted - 2007-02-01 : 13:59:06
|
| Thanks Paul. |
|
|
|
|
|
|
|
|
Linkage Problem