﻿<?xml version='1.0' encoding='UTF-8'?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>SQLServerCentral / SQL Server 2005 / Data Corruption  / checkdb error on index ID 0 / Latest Posts</title><generator>InstantForum.NET v2.9.0</generator><description>SQLServerCentral</description><link>http://www.sqlservercentral.com/Forums/</link><webMaster>notifications@sqlservercentral.com</webMaster><lastBuildDate>Thu, 23 May 2013 06:19:10 GMT</lastBuildDate><ttl>20</ttl><item><title>RE: checkdb error on index ID 0</title><link>http://www.sqlservercentral.com/Forums/Topic1392105-266-1.aspx</link><description>Thanks both.After I ran the checkDB with allow data loss, there were 100 rows are missing on REQ_ITEM table.Since it was only affected single table, I was restore from last good backup and re-inserted missing data back to REQ_ITEM table.Thanks again,David.</description><pubDate>Mon, 10 Dec 2012 13:15:30 GMT</pubDate><dc:creator>David Kang</dc:creator></item><item><title>RE: checkdb error on index ID 0</title><link>http://www.sqlservercentral.com/Forums/Topic1392105-266-1.aspx</link><description>Since you're on SQL 2000 you do not have the option of doing page restores. As Gail outlined, you can restore from backup that do not include the corruption (including tail-log) to bring the database to current or look into bringing up a parallel copy of the database that does not include the corruption to recover the data manually, or do the repair allowing for data loss.</description><pubDate>Wed, 05 Dec 2012 23:13:21 GMT</pubDate><dc:creator>opc.three</dc:creator></item><item><title>RE: checkdb error on index ID 0</title><link>http://www.sqlservercentral.com/Forums/Topic1392105-266-1.aspx</link><description>Now a Days, when you search on the Google, many companies providing a data recovery services as well as recovery software. In such types of software one is recoveryfix for sql repair software, this company offering a free trial version software, with the help of this trial version you can see the preview of recoverable data.Thanks</description><pubDate>Wed, 05 Dec 2012 00:15:27 GMT</pubDate><dc:creator>jonmichel72</dc:creator></item><item><title>RE: checkdb error on index ID 0</title><link>http://www.sqlservercentral.com/Forums/Topic1392105-266-1.aspx</link><description>If you have a clean backup (one without any corruption) and an unbroken chain of log backups up to present, you can do a page restore. Or you can restore the full backup over the DB followed by all log backups to bring the DB back to current time with no corruption (take a tail-log backup first).If the DB is not in full recovery or you don't have the necessary log backups, then you're looking at either losing data by restoring to the last good backup or by repairing. You can, in that case, try to repair then restore a copy of the DB elsewhere and sync in the missing data.</description><pubDate>Mon, 03 Dec 2012 15:33:10 GMT</pubDate><dc:creator>GilaMonster</dc:creator></item><item><title>RE: checkdb error on index ID 0</title><link>http://www.sqlservercentral.com/Forums/Topic1392105-266-1.aspx</link><description>Gail! Thanks for quick response.So, can I run page level restore for this? or restore the whole DB to temp location then extract the 'REQ_ITEM' table?Thanks again,David.</description><pubDate>Mon, 03 Dec 2012 13:10:54 GMT</pubDate><dc:creator>David Kang</dc:creator></item><item><title>RE: checkdb error on index ID 0</title><link>http://www.sqlservercentral.com/Forums/Topic1392105-266-1.aspx</link><description>[quote][b]David Kang (12/3/2012)[/b][hr]repair_allow_data_loss is the [b]minimum [/b]repair level for the errors found by DBCC CHECKDB (PMM ).[/quote]Since repair allow data loss is the minimum repair level necessary, running checkDB with any lesser repair level will be a waste of time. Minimum repair level is exactly that.You will lose data. Four pages of data from the table REQ_ITEM.I assume there's no good backup available...</description><pubDate>Mon, 03 Dec 2012 12:51:13 GMT</pubDate><dc:creator>GilaMonster</dc:creator></item><item><title>checkdb error on index ID 0</title><link>http://www.sqlservercentral.com/Forums/Topic1392105-266-1.aspx</link><description>I need help on fixing checkdb error.Here's the output of checkdb:Server: Msg 8909, Level 16, State 1, Line 1Table error: Object ID -1627389056, index ID 0, page ID (1:611861). The PageId in the page header = (14131:894586624).Server: Msg 8909, Level 16, State 1, Line 1Table error: Object ID 0, index ID 0, page ID (1:611862). The PageId in the page header = (0:0).Server: Msg 8909, Level 16, State 1, Line 1Table error: Object ID 0, index ID 0, page ID (1:611863). The PageId in the page header = (0:0).Server: Msg 8928, Level 16, State 1, Line 1Object ID 226099846, index ID 0: Page (1:611860) could not be processed. See other errors for details.Server: Msg 8939, Level 16, State 1, Line 1Table error: Object ID 226099846, index ID 0, page (1:611860). Test (IS_ON (BUF_IOERR, bp-&amp;gt;bstat) &amp;&amp;	bp-&amp;gt;berrcode) failed. Values are 2057 and -1.Server: Msg 8928, Level 16, State 1, Line 1Object ID 226099846, index ID 0: Page (1:611861) could not be processed. See other errors for details.Server: Msg 8928, Level 16, State 1, Line 1Object ID 226099846, index ID 0: Page (1:611862) could not be processed. See other errors for details.Server: Msg 8928, Level 16, State 1, Line 1Object ID 226099846, index ID 0: Page (1:611863) could not be processed. See other errors for details.CHECKDB found 0 allocation errors and 1 consistency errors in table '(Object ID -1627389056)' (object ID -1627389056).CHECKDB found 0 allocation errors and 2 consistency errors not associated with any single object.CHECKDB found 0 allocation errors and 5 consistency errors in table 'REQ_ITEM' (object ID 226099846).CHECKDB found 0 allocation errors and 8 consistency errors in database 'PMM'.repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (PMM ).It's running on SQL 2000 SP3.Can I repair these errors with 'REPAIR_REBUILD'?Thanks in advance,David.</description><pubDate>Mon, 03 Dec 2012 12:10:22 GMT</pubDate><dc:creator>David Kang</dc:creator></item></channel></rss>