Corruption in sysindexes for table 'syslogs' 2

[SantaMufasa]

When I search for guidance on this error, the remedies sound rather risky when 'sysindexes' for 'syslogs' is concerned:

Checking syslogs
Msg 2578, Level 16, State 1:
Line 1:
The first page 126268 in sysindexes for table 'syslogs' has previous page # 126267 in its page h
eader. The previous page # should be NULL. Please check sysindexes.
Msg 2503, Level 16, State 1:
Line 1:
Table Corrupt: Page linkage is not consistent; check the following pages: (current page#=126268;
page# pointing to this page=0; previous page# indicated in this page=126267)

What remedies do you suggest? If you can offer actual SQL commands for the remedy, I would be very appreciative.


Mufasa
(aka Dave of Sandy, Utah, USA)
[I provide low-cost, remote Database Administration services: www.dasages.com]

 

[Jamfool]

you can find correct this with DBCC CHECKDB

http://msdn2.microsoft.com/en-us/library/ms176064.aspx

 

[ptheriault]

Dave,
You can run CHECKDB with repair options. However, the best fix for this is to restore from a backup. That way you don't risk the loss of any data.

- Paul
- If at first you don't succeed, find out if the loser gets anything.

 

[mrdenny]

What repair level does DBCC CHECKDB tell you to use to fix the problem?

Denny
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / Microsoft Windows SharePoint Services 3.0: Configuration / Microsoft Office SharePoint Server 2007: Configuration)
MCITP Database Administrator (SQL 2005) / Database Developer (SQL 2005)

--Anything is possible. All it takes is a little research. (Me)

http://www.mrdenny.com

 

[SantaMufasa]

Denny (et. al.),

Strangely, when I have re-run the process during which this error occurred, it did not throw any errors; I have done nothing remedial, so, at this point, the entire scenario appears to be an anomaly.

Due to my relative ignorances on this topic, can you (or another) post o/s-level command(s) that I can run to confirm that 'sysindexes'/'syslogs' are healthy now?

I appreciate Jamfool's, PTheriault's, and MrDenny's willingness to help thus far.

Mufasa
(aka Dave of Sandy, Utah, USA)
[I provide low-cost, remote Database Administration services: www.dasages.com]

 

[mrdenny]

Try doing a checkdisk on the disk and see if that reports any issues. If that shows nothing and the DBCC CHECKDB shows nothing in the database then you should be fine.

Denny
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / Microsoft Windows SharePoint Services 3.0: Configuration / Microsoft Office SharePoint Server 2007: Configuration)
MCITP Database Administrator (SQL 2005) / Database Developer (SQL 2005)

--Anything is possible. All it takes is a little research. (Me)

http://www.mrdenny.com

 

[SantaMufasa]

Thanks, folks, for your assistance! Have some stars.

Mufasa
(aka Dave of Sandy, Utah, USA)
[I provide low-cost, remote Database Administration services: www.dasages.com]

 

[mrdenny]

Oh, yummy. Little purple stars. My favorite.

Thanks Dave

Denny
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / Microsoft Windows SharePoint Services 3.0: Configuration / Microsoft Office SharePoint Server 2007: Configuration)
MCITP Database Administrator (SQL 2005) / Database Developer (SQL 2005)

--Anything is possible. All it takes is a little research. (Me)

http://www.mrdenny.com