Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

ERR 605 - DATABASE CORRUPTION - NO VALID BACKUP!!! Expand / Collapse
Author
Message
Posted Sunday, October 5, 2008 8:53 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Monday, March 21, 2011 2:12 AM
Points: 1, Visits: 29
Hi,

The DB server is a virtual machine running on VM Ware ESX cluster.
OS: WIN 2003 R2
SQL: SQL 2000 SP4



I'm facing the following errors when I run DBCC CHECKDB on user data base 021:

DBCC results for 'amutas'.
Server: Msg 2533, Level 16, State 1, Line 1
Table error: Page (1:1692994) allocated to object ID 423672557, index ID 0 was not seen. Page may be invalid or have incorrect object ID information in its header.
Server: Msg 2533, Level 16, State 1, Line 1
Table error: Page (1:1692997) allocated to object ID 423672557, index ID 0 was not seen. Page may be invalid or have incorrect object ID information in its header.
Server: Msg 2533, Level 16, State 1, Line 1
Table error: Page (1:1692998) allocated to object ID 423672557, index ID 0 was not seen. Page may be invalid or have incorrect object ID information in its header.
Server: Msg 2533, Level 16, State 1, Line 1
Table error: Page (1:1692999) allocated to object ID 423672557, index ID 0 was not seen. Page may be invalid or have incorrect object ID information in its header.
Server: Msg 2533, Level 16, State 1, Line 1
Table error: Page (1:1693154) allocated to object ID 423672557, index ID 0 was not seen. Page may be invalid or have incorrect object ID information in its header.
Server: Msg 2533, Level 16, State 1, Line 1
Table error: Page (1:1693157) allocated to object ID 423672557, index ID 0 was not seen. Page may be invalid or have incorrect object ID information in its header.
Server: Msg 2533, Level 16, State 1, Line 1
Table error: Page (1:1693336) allocated to object ID 423672557, index ID 0 was not seen. Page may be invalid or have incorrect object ID information in its header.
Server: Msg 2533, Level 16, State 1, Line 1
Table error: Page (1:1693337) allocated to object ID 423672557, index ID 0 was not seen. Page may be invalid or have incorrect object ID information in its header.
Server: Msg 2533, Level 16, State 1, Line 1
Table error: Page (1:1693338) allocated to object ID 423672557, index ID 0 was not seen. Page may be invalid or have incorrect object ID information in its header.
Server: Msg 2533, Level 16, State 1, Line 1
Table error: Page (1:1693339) allocated to object ID 423672557, index ID 0 was not seen. Page may be invalid or have incorrect object ID information in its header.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 423672557, index ID 1. Page (1:1692994) was not seen in the scan although its parent (1:1692191) and previous (1:1692993) refer to it. Check any previous errors.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 423672557, index ID 1. Page (1:1692995) is missing a reference from previous page (1:1692994). Possible chain linkage problem.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 423672557, index ID 1. Page (1:1692997) was not seen in the scan although its parent (1:1692191) and previous (1:1692996) refer to it. Check any previous errors.
Server: Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 423672557, index ID 1. Index node page (1:1692191), slot 123 refers to child page (1:1692998) and previous child (1:1692997), but they were not encountered.
Server: Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 423672557, index ID 1. Index node page (1:1692191), slot 124 refers to child page (1:1692999) and previous child (1:1692998), but they were not encountered.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 423672557, index ID 1. Page (1:1693152) is missing a reference from previous page (1:1692999). Possible chain linkage problem.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 423672557, index ID 1. Page (1:1693154) was not seen in the scan although its parent (1:1692191) and previous (1:1693153) refer to it. Check any previous errors.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 423672557, index ID 1. Page (1:1693155) is missing a reference from previous page (1:1693154). Possible chain linkage problem.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 423672557, index ID 1. Page (1:1693157) was not seen in the scan although its parent (1:1692191) and previous (1:1693156) refer to it. Check any previous errors.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 423672557, index ID 1. Page (1:1693158) is missing a reference from previous page (1:1693157). Possible chain linkage problem.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 423672557, index ID 1. Page (1:1693336) was not seen in the scan although its parent (1:1692191) and previous (1:1693159) refer to it. Check any previous errors.
Server: Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 423672557, index ID 1. Index node page (1:1692191), slot 134 refers to child page (1:1693337) and previous child (1:1693336), but they were not encountered.
Server: Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 423672557, index ID 1. Index node page (1:1692191), slot 135 refers to child page (1:1693338) and previous child (1:1693337), but they were not encountered.
Server: Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 423672557, index ID 1. Index node page (1:1692191), slot 136 refers to child page (1:1693339) and previous child (1:1693338), but they were not encountered.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 423672557, index ID 1. Page (1:1693340) is missing a reference from previous page (1:1693339). Possible chain linkage problem.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 423672557, index ID 11. Page (1:1692297) is missing a reference from previous page (1:1692296). Possible chain linkage problem.
There are 1653028 rows in 206890 pages for object 'amutas'.
CHECKDB found 0 allocation errors and 26 consistency errors in table 'amutas' (object ID 423672557).

DBCC results for 'gbkmut'.
Server: Msg 2533, Level 16, State 1, Line 1
Table error: Page (1:1693075) allocated to object ID 2075870462, index ID 0 was not seen. Page may be invalid or have incorrect object ID information in its header.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 2075870462, index ID 1. Page (1:1693075) was not seen in the scan although its parent (1:1693729) and previous (1:1693074) refer to it. Check any previous errors.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 2075870462, index ID 1. Page (1:1693076) is missing a reference from previous page (1:1693075). Possible chain linkage problem.
Server: Msg 8934, Level 16, State 1, Line 1
Table error: Object ID 2075870462, index ID 1. The high key value on page (1:1693144) (level 0) is not less than the low key value in the parent (0:1), slot 0 of the next page (1:1693145).
Server: Msg 8933, Level 16, State 1, Line 1
Table error: Object ID 2075870462, index ID 1. The low key value on page (1:1693145) (level 0) is not >= the key value in the parent (1:1693729) slot 174.
Server: Msg 8937, Level 16, State 1, Line 1
Table error: Object ID 2075870462, index ID 91. B-tree page (1:1588093) has two parent nodes (1:1710570), slot 31 and (1:1680262), slot 1.
Server: Msg 8937, Level 16, State 1, Line 1
Table error: Object ID 2075870462, index ID 91. B-tree page (1:1588094) has two parent nodes (1:1710570), slot 33 and (1:1680262), slot 1.
Server: Msg 8937, Level 16, State 1, Line 1
Table error: Object ID 2075870462, index ID 91. B-tree page (1:1588095) has two parent nodes (1:1710570), slot 34 and (1:1680262), slot 1.
Server: Msg 8937, Level 16, State 1, Line 1
Table error: Object ID 2075870462, index ID 91. B-tree page (1:1588096) has two parent nodes (1:1710570), slot 35 and (1:1680262), slot 1.
Server: Msg 8937, Level 16, State 1, Line 1
Table error: Object ID 2075870462, index ID 91. B-tree page (1:1588097) has two parent nodes (1:1710570), slot 36 and (1:1680262), slot 1.
Server: Msg 8937, Level 16, State 1, Line 1
Table error: Object ID 2075870462, index ID 91. B-tree page (1:1588098) has two parent nodes (1:1710570), slot 38 and (1:1680262), slot 1.
Server: Msg 8937, Level 16, State 1, Line 1
Table error: Object ID 2075870462, index ID 91. B-tree page (1:1588099) has two parent nodes (1:1710570), slot 39 and (1:1680262), slot 1.
Server: Msg 8937, Level 16, State 1, Line 1
Table error: Object ID 2075870462, index ID 91. B-tree page (1:1588100) has two parent nodes (1:1710570), slot 40 and (1:1680262), slot 1.
Server: Msg 8937, Level 16, State 1, Line 1
Table error: Object ID 2075870462, index ID 91. B-tree page (1:1588101) has two parent nodes (1:1710570), slot 41 and (1:1680262), slot 1.
Server: Msg 8937, Level 16, State 1, Line 1
Table error: Object ID 2075870462, index ID 91. B-tree page (1:1588102) has two parent nodes (1:1710570), slot 43 and (1:1680262), slot 1.
Server: Msg 8937, Level 16, State 1, Line 1
Table error: Object ID 2075870462, index ID 91. B-tree page (1:1588103) has two parent nodes (1:1710570), slot 44 and (1:1680262), slot 1.
Server: Msg 8937, Level 16, State 1, Line 1
Table error: Object ID 2075870462, index ID 91. B-tree page (1:1588104) has two parent nodes (1:1710570), slot 45 and (1:1680262), slot 1.
Server: Msg 8937, Level 16, State 1, Line 1
Table error: Object ID 2075870462, index ID 91. B-tree page (1:1588105) has two parent nodes (1:1710570), slot 47 and (1:1680262), slot 1.
Server: Msg 8937, Level 16, State 1, Line 1
Table error: Object ID 2075870462, index ID 91. B-tree page (1:1588106) has two parent nodes (1:1710570), slot 48 and (1:1680262), slot 1.
Server: Msg 8937, Level 16, State 1, Line 1
Table error: Object ID 2075870462, index ID 91. B-tree page (1:1588107) has two parent nodes (1:1710570), slot 50 and (1:1680262), slot 1.
Server: Msg 8937, Level 16, State 1, Line 1
Table error: Object ID 2075870462, index ID 91. B-tree page (1:1588108) has two parent nodes (1:1710570), slot 51 and (1:1680262), slot 1.
Server: Msg 8937, Level 16, State 1, Line 1
Table error: Object ID 2075870462, index ID 91. B-tree page (1:1588109) has two parent nodes (1:1710570), slot 52 and (1:1680262), slot 1.
Server: Msg 8937, Level 16, State 1, Line 1
Table error: Object ID 2075870462, index ID 91. B-tree page (1:1588110) has two parent nodes (1:1710570), slot 53 and (1:1680262), slot 1.
Server: Msg 8937, Level 16, State 1, Line 1
Table error: Object ID 2075870462, index ID 91. B-tree page (1:1588111) has two parent nodes (1:1710570), slot 55 and (1:1680262), slot 1.
Server: Msg 8937, Level 16, State 1, Line 1
Table error: Object ID 2075870462, index ID 91. B-tree page (1:1588112) has two parent nodes (1:1710570), slot 56 and (1:1680262), slot 1.
Server: Msg 8937, Level 16, State 1, Line 1
Table error: Object ID 2075870462, index ID 91. B-tree page (1:1588113) has two parent nodes (1:1710570), slot 57 and (1:1680262), slot 1.
Server: Msg 8937, Level 16, State 1, Line 1
Table error: Object ID 2075870462, index ID 91. B-tree page (1:1588114) has two parent nodes (1:1710570), slot 59 and (1:1680262), slot 1.
Server: Msg 8937, Level 16, State 1, Line 1
Table error: Object ID 2075870462, index ID 91. B-tree page (1:1588115) has two parent nodes (1:1710570), slot 60 and (1:1680262), slot 1.
Server: Msg 8937, Level 16, State 1, Line 1
Table error: Object ID 2075870462, index ID 91. B-tree page (1:1588116) has two parent nodes (1:1710570), slot 61 and (1:1680262), slot 1.
Server: Msg 8937, Level 16, State 1, Line 1
Table error: Object ID 2075870462, index ID 91. B-tree page (1:1588117) has two parent nodes (1:1710570), slot 63 and (1:1680262), slot 1.
Server: Msg 8937, Level 16, State 1, Line 1
Table error: Object ID 2075870462, index ID 91. B-tree page (1:1588118) has two parent nodes (1:1710570), slot 64 and (1:1680262), slot 1.
Server: Msg 8937, Level 16, State 1, Line 1
Table error: Object ID 2075870462, index ID 91. B-tree page (1:1588119) has two parent nodes (1:1710570), slot 65 and (1:1680262), slot 1.
Server: Msg 8937, Level 16, State 1, Line 1
Table error: Object ID 2075870462, index ID 91. B-tree page (1:1588120) has two parent nodes (1:1710570), slot 66 and (1:1680262), slot 1.
Server: Msg 8937, Level 16, State 1, Line 1
Table error: Object ID 2075870462, index ID 91. B-tree page (1:1588121) has two parent nodes (1:1710570), slot 68 and (1:1680262), slot 1.
Server: Msg 8937, Level 16, State 1, Line 1
Table error: Object ID 2075870462, index ID 91. B-tree page (1:1588122) has two parent nodes (1:1710570), slot 69 and (1:1680262), slot 1.
Server: Msg 8937, Level 16, State 1, Line 1
Table error: Object ID 2075870462, index ID 91. B-tree page (1:1588123) has two parent nodes (1:1710570), slot 70 and (1:1680262), slot 1.
Server: Msg 8937, Level 16, State 1, Line 1
Table error: Object ID 2075870462, index ID 91. B-tree page (1:1588124) has two parent nodes (1:1710570), slot 71 and (1:1680262), slot 1.
Server: Msg 8937, Level 16, State 1, Line 1
Table error: Object ID 2075870462, index ID 91. B-tree page (1:1588125) has two parent nodes (1:1710570), slot 73 and (1:1680262), slot 1.
Server: Msg 8937, Level 16, State 1, Line 1
Table error: Object ID 2075870462, index ID 91. B-tree page (1:1588126) has two parent nodes (1:1710570), slot 74 and (1:1680262), slot 1.
Server: Msg 8937, Level 16, State 1, Line 1
Table error: Object ID 2075870462, index ID 91. B-tree page (1:1588127) has two parent nodes (1:1710570), slot 75 and (1:1680262), slot 1.
Server: Msg 8937, Level 16, State 1, Line 1
Table error: Object ID 2075870462, index ID 91. B-tree page (1:1588136) has two parent nodes (1:1710570), slot 77 and (1:1680262), slot 1.
Server: Msg 8937, Level 16, State 1, Line 1
Table error: Object ID 2075870462, index ID 91. B-tree page (1:1588137) has two parent nodes (1:1710570), slot 78 and (1:1680262), slot 1.
Server: Msg 8937, Level 16, State 1, Line 1
Table error: Object ID 2075870462, index ID 91. B-tree page (1:1588138) has two parent nodes (1:1710570), slot 79 and (1:1680262), slot 1.
Server: Msg 8937, Level 16, State 1, Line 1
Table error: Object ID 2075870462, index ID 91. B-tree page (1:1588139) has two parent nodes (1:1710570), slot 81 and (1:1680262), slot 1.
Server: Msg 8937, Level 16, State 1, Line 1
Table error: Object ID 2075870462, index ID 91. B-tree page (1:1588140) has two parent nodes (1:1710570), slot 82 and (1:1680262), slot 1.
Server: Msg 8937, Level 16, State 1, Line 1
Table error: Object ID 2075870462, index ID 91. B-tree page (1:1588141) has two parent nodes (1:1710570), slot 83 and (1:1680262), slot 1.
Server: Msg 8937, Level 16, State 1, Line 1
Table error: Object ID 2075870462, index ID 91. B-tree page (1:1659500) has two parent nodes (1:1710570), slot 30 and (1:1680262), slot 1.
Server: Msg 8937, Level 16, State 1, Line 1
Table error: Object ID 2075870462, index ID 91. B-tree page (1:1689161) has two parent nodes (1:1693168), slot 0 and (1:1680262), slot 1.
Server: Msg 8937, Level 16, State 1, Line 1
Table error: Object ID 2075870462, index ID 91. B-tree page (1:1689162) has two parent nodes (1:1693168), slot 1 and (1:1680262), slot 1.
Server: Msg 8937, Level 16, State 1, Line 1
Table error: Object ID 2075870462, index ID 91. B-tree page (1:1689163) has two parent nodes (1:1693168), slot 2 and (1:1680262), slot 1.
Server: Msg 8937, Level 16, State 1, Line 1
Table error: Object ID 2075870462, index ID 91. B-tree page (1:1689164) has two parent nodes (1:1693168), slot 3 and (1:1680262), slot 1.
Server: Msg 8937, Level 16, State 1, Line 1
Table error: Object ID 2075870462, index ID 91. B-tree page (1:1689165) has two parent nodes (1:1693168), slot 4 and (1:1680262), slot 1.
Server: Msg 8937, Level 16, State 1, Line 1
Table error: Object ID 2075870462, index ID 91. B-tree page (1:1689166) has two parent nodes (1:1693168), slot 5 and (1:1680262), slot 1.
Server: Msg 8937, Level 16, State 1, Line 1
Table error: Object ID 2075870462, index ID 91. B-tree page (1:1689167) has two parent nodes (1:1693168), slot 6 and (1:1680262), slot 1.
Server: Msg 8937, Level 16, State 1, Line 1
Table error: Object ID 2075870462, index ID 91. B-tree page (1:1690560) has two parent nodes (1:1693168), slot 7 and (1:1680262), slot 1.
Server: Msg 8937, Level 16, State 1, Line 1
Table error: Object ID 2075870462, index ID 91. B-tree page (1:1690561) has two parent nodes (1:1693168), slot 8 and (1:1680262), slot 1.
Server: Msg 8937, Level 16, State 1, Line 1
Table error: Object ID 2075870462, index ID 91. B-tree page (1:1690562) has two parent nodes (1:1693168), slot 9 and (1:1680262), slot 1.
Server: Msg 8937, Level 16, State 1, Line 1
Table error: Object ID 2075870462, index ID 91. B-tree page (1:1690563) has two parent nodes (1:1693168), slot 10 and (1:1680262), slot 1.
Server: Msg 8937, Level 16, State 1, Line 1
Table error: Object ID 2075870462, index ID 91. B-tree page (1:1690564) has two parent nodes (1:1693168), slot 11 and (1:1680262), slot 1.
Server: Msg 8937, Level 16, State 1, Line 1
Table error: Object ID 2075870462, index ID 91. B-tree page (1:1690565) has two parent nodes (1:1693168), slot 12 and (1:1680262), slot 1.
Server: Msg 8937, Level 16, State 1, Line 1
Table error: Object ID 2075870462, index ID 91. B-tree page (1:1690566) has two parent nodes (1:1693168), slot 13 and (1:1680262), slot 1.
Server: Msg 8937, Level 16, State 1, Line 1
Table error: Object ID 2075870462, index ID 91. B-tree page (1:1690567) has two parent nodes (1:1693168), slot 14 and (1:1680262), slot 1.
Server: Msg 8937, Level 16, State 1, Line 1
Table error: Object ID 2075870462, index ID 91. B-tree page (1:1691920) has two parent nodes (1:1693168), slot 15 and (1:1680262), slot 1.
Server: Msg 8937, Level 16, State 1, Line 1
Table error: Object ID 2075870462, index ID 91. B-tree page (1:1691921) has two parent nodes (1:1693168), slot 16 and (1:1680262), slot 1.
Server: Msg 8937, Level 16, State 1, Line 1
Table error: Object ID 2075870462, index ID 91. B-tree page (1:1691922) has two parent nodes (1:1693168), slot 17 and (1:1680262), slot 1.
Server: Msg 8937, Level 16, State 1, Line 1
Table error: Object ID 2075870462, index ID 91. B-tree page (1:1691923) has two parent nodes (1:1693168), slot 18 and (1:1680262), slot 1.
Server: Msg 8937, Level 16, State 1, Line 1
Table error: Object ID 2075870462, index ID 91. B-tree page (1:1691924) has two parent nodes (1:1693168), slot 19 and (1:1680262), slot 1.
Server: Msg 8937, Level 16, State 1, Line 1
Table error: Object ID 2075870462, index ID 91. B-tree page (1:1691925) has two parent nodes (1:1693168), slot 20 and (1:1680262), slot 1.
Server: Msg 8937, Level 16, State 1, Line 1
Table error: Object ID 2075870462, index ID 91. B-tree page (1:1691926) has two parent nodes (1:1693168), slot 21 and (1:1680262), slot 1.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 2075870462, index ID 91. Page (1:1693168) is missing a reference from previous page (1:1680262). Possible chain linkage problem.
There are 2194768 rows in 315966 pages for object 'gbkmut'.
CHECKDB found 0 allocation errors and 70 consistency errors in table 'gbkmut' (object ID 2075870462).


I already tried the following things:

1.) DBCC REINDEX the corrupt table gbkmut raises the following error:

Server: Msg 1505, Level 16, State 1, Line 1
CREATE UNIQUE INDEX terminated because a duplicate key was found for index ID 1. Most significant primary key is '3992936'.
The statement has been terminated.



2.) Then I tried to script table as CREATE SQL with Indexes, Keys, etc. Then rename gbkmut to xgbkmut. Then drop all indexes in table xgbkmut. Raises this error

'xgbkmut' table
- Unable to delete index 'PK_gbkmut'.
ODBC error: [Microsoft][ODBC SQL Server Driver][SQL Server]CREATE UNIQUE INDEX terminated because a duplicate key was found for index ID 3. Most significant primary key is 'type 24, len 16'.
[Microsoft][ODBC SQL Server Driver][SQL Server]Could not drop constraint. See previous errors.
[Microsoft][ODBC SQL Server Driver][SQL Server]The statement has been terminated.


3.) Run DBCC CHECKDB with REPAIR_ALLOW_DATA_LOSS but that was also not working. As this is last resort I’m really running out of options.
I also know that page 1:680262 is pointing to wrong page. I know the page it should point to but I have no clue if it’s possible to edit page header information. Maybe you know how to do that.
How can I identify the index name when I only have the index ID? If I would have the name I can drop index over the GUI. Or can someone provide a SQL statement that drops index with ID x?`
Main problem is that there is no valid backup. I have one backup, but that is already corrupted. So at least I can restore the corrupted database at any time. So I can run any test/recovery you would suggest.

4.) I also tried to attache the DB on a different server using a different storage. But the errors are the same.


Any suggestions or tipps how I can resolve the error?

Thanks in advance and best regards,

Markus Purker

Post #580861
Posted Monday, October 6, 2008 7:29 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 3:14 AM
Points: 42,460, Visits: 35,520
Why no good backup?

If checkDB with repair is not working, then your only remaining option is to script out the DB, bcp out what data you can (some won't export because of the corruptions) and recreate the database.

It's very likely that the two tables with corruption won't export at all. You can try querying them in QA, but there are no guarantees. You may be able to get some of the data back though.

Do you have a much earlier backup that you can salvage some data from?



Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #581081
Posted Monday, October 6, 2008 8:36 AM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Friday, April 25, 2014 9:08 AM
Points: 1,190, Visits: 364
You could try this if you haven't yet.

Script out all Primary Keys, Foreign Keys and Indexes.

Backup the actual Database files (stop SQL Server, copy data files and log files, restart SQL Server)

Drop all Foreign Keys;
Drop all Primary Keys;
Drop all Indexes;

Create all Primary Keys;
Create all Foreign Keys;
Create all Indexes;

Run DBCC CHECKDB to see if there are still errors.
Post #581112
Posted Monday, October 6, 2008 8:45 AM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Friday, April 25, 2014 9:08 AM
Points: 1,190, Visits: 364
If my previous post doesn't work, I think you have no choice but to rebuild the entire database.

You can do to the following in replacement of bcp in/out.

Create a new database with all the TABLE STRUCTURE ONLY, no PK, FK, Constraints, NO SP, no Triggers.....

This db is create in the same instance.

Copy over the data with T-SQL INSERT.. SELECT statements for all tables. Some table may not be able to copy if they are corrupted.

Create all PK, FK, Constraints, SP and all other database objects required to be the same as the original database.

Run DBCC CHECKDB to find errors.

Backup your database.
Post #581118
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse