DBCC Problem with syscolumns - SQL Server Forums

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.

All Forums

General SQL Server Forums

Data Corruption Issues

DBCC Problem with syscolumns

Author

Topic

DaveShaw
Starting Member

3 Posts

Posted - 2005-12-19 : 06:10:49

Hi, I have run a DBCC CHECKDB and it found 2 Errors in syscolumns. I have run a CHECKTABLE and found the following Error:

Server: Msg 8928, Level 16, State 1, Line 1
Object ID 3, index ID 2: Page (1:266) could not be processed. See other errors for details.
Server: Msg 8944, Level 16, State 1, Line 1
Table Corrupt: Object ID 3, index ID 2, page (1:266), row 12. Test (VarColOffsets + (int)(sizeof (class VarColOffset) * nVarCols) <= (nextRec - pRec)) failed. Values are 178 and 72.
DBCC results for 'syscolumns'.
There are 6963 rows in 144 pages for object 'syscolumns'.
CHECKTABLE found 0 allocation errors and 2 consistency errors in table 'syscolumns' (object ID 3).
repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKTABLE (EMIS.dbo.syscolumns ).

Can anyone suggest the best way to proceed with this problem. I am a little dubious about running REPAIR_ALLOW_DATALOSS on syscolumns, I am unsure of what will happen if sections of syscolumns go missing. I have run DBCC PAGE ('EMIS',1,266,1) but this has given me nothing to work with.

Thanks in Advance,

Dave Shaw.

DaveShaw
Starting Member

3 Posts

Posted - 2005-12-19 : 07:08:39

Hi,
I also posted on google and was given this as a guide.

http://www.windowsitpro.com/Articles/Index.cfm?ArticleID=14051&DisplayTab=Article

Hope it helps any else out there with sys table problems.

I will let you know if I have any problems

Thanx!

Dave Shaw

History Admires the Wise, but Elevates the Brave - Edmund Morris.

paulrandal
Yak with Vast SQL Skills

899 Posts

Posted - 2005-12-19 : 16:06:14

You're fine with either method - its only a bad page in a non-clustered index so you won't lose any data - the index will simply be rebuilt. If it was a bad page in the clustered index, that's unrepairable - do you have a sound backup strategy?

Have you checked for h/w problem in the errorlog and Windows event logs? Did any unusual event occur before this error happened (e.g power loss)?

Thanks

Paul Randal
Lead Program Manager, Microsoft SQL Server Storage Engine
(Legalese: This posting is provided "AS IS" with no warranties, and confers no rights.)

Subscribe to SQLTeam.com

SQLTeam.com Articles via RSS

SQLTeam.com Weblog via RSS

- Advertisement -

Resources