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 |
|
mddba
Starting Member
4 Posts |
 Posted - 2005-11-02 : 15:21:09
|
| A rouge 6.5 DB was brought to my attention a few weeks ago. We can't upgrade until we solve some corruption issues. We're receiving the listed message after running a DBCC NEWALLOC. We're not sure but we believe the corruption is with a primary key. We can't drop the primary key without of course, first dropping all the foreign keys. ALLOW_DATA_LOSS wasn't introduced until 7.0. Rebuilding the indexes doesn't fix the problem. Does anyone have any suggestion on how to fix this corruption? Any help is appreciated. Restoring isn't an option as this corruption exists in the oldest backup we have...thanks in advance************TABLE: ABS_PAT_INSURANCES OBJID = 204527762INDID=1 FIRST=4041968 ROOT=4039657 DPAGES=14304 SORT=0Msg 2525, Level 16, State 1Table Corrupt: Object id wrong; tables: alloc page 4036864 extent id=4036880 l page#=4036880 objid in ext=204527762 (name = ABS_PAT_INSURANCES) objid in page=348528275 (name = ABS_PAT_MAIN)objid in sysindexes=204527762 (name = ABS_PAT_INSURANCES) Data level: 1. 0 Data Pages in 1789 extents.INDID=2 FIRST=3926064 ROOT=3917574 DPAGES=4305 SORT=1Msg 2525, Level 16, State 1Table Corrupt: Object id wrong; tables: alloc page 3926016 extent id=3926064 l page#=3926064 objid in ext=204527762 (name = ABS_PAT_INSURANCES) objid in page=348528275 (name = ABS_PAT_MAIN)objid in sysindexes=204527762 (name = ABS_PAT_INSURANCES)TOTAL # of extents = 1789 |
|
|
Michael Valentine Jones
Yak DBA Kernel (pronounced Colonel)
7020 Posts |
Posted - 2005-11-02 : 15:42:30
|
| You might want to post this on the Data Corruption Issues forum. That forum is monitored by people that have very good knowledge of these issues.CODO ERGO SUM |
 |
|
|
eyechart
Master Smack Fu Yak Hacker
3575 Posts |
|
|
|
|
|
SQL 6.5 Corruption (Yes...6.5)