Re: Restore of DB Backup gave some errors

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Ok, turns out the problem is at night durring the maintenance plan, whewn rebuilding indexes on a specific table

Here is the problem and solution

http://support.microsoft.com/kb/301292

Thanks

JIM



"Tibor Karaszi" <tibor_please.no.email_karaszi@xxxxxxxxxxxxxxxxxx> wrote in message news:%239022x5KKHA.1492@xxxxxxxxxxxxxxxxxxxxxxx
I would walk backwards checking the results of DBCC CHECKDB (assuming you do regular CHECKDB, of course) and see if that can help you pinpoint when in time this happened.

--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi


"JPK" <james@xxxxxxxx> wrote in message news:A797C08D-F83D-4109-992E-0620B6096A9D@xxxxxxxxxxxxxxxx
Ok, thanks,


I will get back to you with results


thanks,

JIM


"Russell Fields" <russellfields@xxxxxxxxxx> wrote in message news:e03OVDxKKHA.1492@xxxxxxxxxxxxxxxxxxxxxxx
JPK,

Yes, I would be alarmed at getting a lot of messages. My main question would be: Why? Are you having disk / array problems that might be causing corruption? Did you have a hard crash of the server? Et cetera.

With many messages I would recommend checking the entire database using:
DBCC CHECKDB

For interpreting ObjectIDs, you can:

SELECT OBJECT_NAME(155199653) -- returns object name

Since these are indexes, you can also determine which index by (what version of SQL Server are you using?) something like:

SELECT OBJECT_NAME(id), name
FROM sysindexes -- deprecated from 2000, but still works
WHERE id = 155199653 and indid = 2

For non-clustered indexes (basically indid > 1), you can drop and recreate them, which will resolve a problem with the index. However, until the underlying problem is understood and resolved, I would remain concerned.

RLF


"JPK" <james@xxxxxxxx> wrote in message news:5C4AD26D-6FB0-4600-8F59-CC005D485EF7@xxxxxxxxxxxxxxxx
Hello, I have a database that I have managed for many years now. I have done many backups and restores with no problems. Today I did a restore and got these;

Warning: A column nullability inconsistency was detected in the metadata of index "PK_Company" (index_id = 2) on object ID 155199653 in database "xxx". The index may be corrupt. Run DBCC CHECKTABLE to verify consistency.

Warning: A column nullability inconsistency was detected in the metadata of index "_WA_Sys_classType_094028A5" (index_id = 7) on object ID 155199653 in database "xxx". The index may be corrupt. Run DBCC CHECKTABLE to verify consistency.

Warning: A column nullability inconsistency was detected in the metadata of index "_WA_Sys_name_094028A5" (index_id = 8) on object ID 155199653 in database "xxx". The index may be corrupt. Run DBCC CHECKTABLE to verify consistency.

Warning: A column nullability inconsistency was detected in the metadata of index "_WA_Sys_eoVersion_094028A5" (index_id = 11) on object ID 155199653 in database "xxx". The index may be corrupt. Run DBCC CHECKTABLE to verify consistency.

several more clipped out ...

Q1. How do I get the actual table from the Object ID e.g. object ID 155199653
Q2. How serious are these messages

Anything else you may suggest that you would do if this were your db??

thanks,

JIM






.

Relevant Pages

  • Re: Restore of DB Backup gave some errors
    ... With many messages I would recommend checking the entire database using: ... A column nullability inconsistency was detected in the ... The index may be corrupt. ... Run DBCC CHECKTABLE to verify consistency. ...
    (microsoft.public.sqlserver.programming)
  • Re: Restore of DB Backup gave some errors
    ... With many messages I would recommend checking the entire database using: ... A column nullability inconsistency was detected in the ... The index may be corrupt. ... Run DBCC CHECKTABLE to verify consistency. ...
    (microsoft.public.sqlserver.programming)
  • Restore of DB Backup gave some errors
    ... I have a database that I have managed for many years now. ... A column nullability inconsistency was detected in the metadata ... The index may be corrupt. ... Run DBCC CHECKTABLE to verify consistency. ...
    (microsoft.public.sqlserver.programming)
  • Re: Form does no longer bind to table
    ... The symptoms you describe indicate that the form has become corrupt, ... Then compact the database to get completely rid of this stuff. ... > I'm only using VBA code and no macros. ... > The form does not bind without filter either. ...
    (microsoft.public.access.forms)
  • Re: There isnt enough memory? -- cannot open form
    ... When you tried the SaveAsText where were you? ... Try this - close the database then reopen it and open the VB Editor. ... > I've now tried "decompile" with no success. ... >> and keep a backup of the corrupt database. ...
    (microsoft.public.access.forms)