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 |
|
Kristen
Test
22859 Posts |
 Posted - 2007-03-06 : 06:56:36
|
| Any advice on this lot please?Server: Msg 8944, Level 16, State 16, Line 1Table error: Object ID 3, index ID 2, page (1:412), row 0. Test (VarColOffsets + (int)(sizeof (class VarColOffset) * nVarCols) <= (nextRec - pRec)) failed. Values are 1549 and 119.Server: Msg 8928, Level 16, State 1, Line 1Object ID 6, index ID 0: Page (1:412) could not be processed. See other errors for details.CHECKDB found 0 allocation errors and 1 consistency errors in table 'syscolumns' (object ID 3).CHECKDB found 0 allocation errors and 1 consistency errors in table 'syscomments' (object ID 6).CHECKDB found 0 allocation errors and 2 consistency errors in database 'master'.repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (master ).I'll have a go at restoring the Backup to a Temp DB and seeing what it looks likeKristen |
|
|
paulrandal
Yak with Vast SQL Skills
899 Posts |
Posted - 2007-03-07 : 04:33:42
|
| Restore from your backup... work out what went wrong... You know the drill :-)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 |
 |
|
|
Kristen
Test
22859 Posts |
Posted - 2007-03-07 : 06:27:09
|
"You know the drill"Yeah, well you'd think so wouldn't you ....  I do know what went wrong however:The server had a disk failure in the middle of January. I was on holiday .... standard procedures were used to DBCC the application databases, those that were damaged were restored and so on. Life looked fine ....Master took a hit at the same time and it now turns out that Tape backups are a 45-day-only-deal. That means I've got the first (weekly) full backup from after the disk failure, but not before.We don't use Master for much, so its really only sysdatabases and the logins (I'll probably think of something else! but there won't be much)However, from my perspective, MASTER is a bit unknown, so its hard for me to know if I "got everything" - whereas I'm much more confident and at-home with my own data of course.Scripting master gives me "No user objects" and just a few Logins and Roles, so that sounds like not too much work.Within a couple of weeks this server will be SQL 2005 (fresh install route ...)... my inclination is to do nothing to Master - I doubt any new data is going to be added ... and the move to SQL 2005 can then solve the problem for me.Do you think that is risky??P.S. I have added to my Jobs List to fix the bug that caused DBCC to be skipped - it turns out that DBCC is getting run as part of the backup process on FULL Recovery Model databases only :-(Kristen |
|
|
|
paulrandal
Yak with Vast SQL Skills
899 Posts |
Posted - 2007-03-07 : 06:36:21
|
| It sounds a little risky but may be the best route, especially if no user data is involved and at risk. That's probably what I'd choose to do...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 |
|
|
|
Kristen
Test
22859 Posts |
Posted - 2007-03-07 : 06:51:15
|
| Cheers Paul. The corruption in master doesn't seem to have caused a problem since mid January ... so I'll keep my fingers crossed!Kristen |
|
|
|
|
|
|
|
|
Corruption in Master