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 |
|
cmareco
Starting Member
1 Post |
 Posted - 2007-07-31 : 20:23:12
|
| I've this error in my event viewer but I'm not experiencing any known hardware problemsError: 8908, Severity: 22, State: 6Table error: Database ID 7, object ID 1162356547, index ID 0. Chain linkage mismatch. (1:810502)->next = (1:810503), but (1:810503)->prev = (1:290710).After run dbcc checkdb on my database the final result isCHECKDB found 0 allocation errors and 48 consistency errors in database 'HOSP001'.repair_rebuild is the minimum repair level for the errors found by DBCC CHECKDB (HOSP001 ).Running dbcc checkdb repair_rebuild the result isServer: Msg 1505, Level 16, State 1, Line 1CREATE UNIQUE INDEX terminated because a duplicate key was found for index ID 2. Most significant primary key is 'type 6a, len 9'.DBCC results for 'hosp001'.I'm not a pro on SQL so, any help is welcome.I'd like to solve the problem but need to know the cause. |
|
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2007-07-31 : 22:41:32
|
| Find out table name and which column the unique index is on, then check values in that column to ensure there is no dup value. |
 |
|
|
eyechart
Master Smack Fu Yak Hacker
3575 Posts |
Posted - 2007-08-01 : 00:51:43
|
quote:
Originally posted by rmiao
Find out table name and which column the unique index is on, then check values in that column to ensure there is no dup value.
then fix dupe value and rebuild index. :)-ec |
|
|
|
|
|
|
Error: 8908