Dave Ballantyne (6/14/2010)

---

Best advice would be to get SQL2008 internals

http://www.amazon.co.uk/Microsoft-SQL-Server-2008-Internals/dp/0735626243

Rob44 (3/8/2010)

---

Let's suppose the command returns 0! What's the next step if the rebuild of the index in the maintenance plan is unsuccessful?

GilaMonster (6/5/2010)

---

Please run the following and post the full and complete output:

DBCC CHECKDB (<Database Name>) WITH NO_INFOMSGS, ALL_ERRORMSGS

What's the exact version of SQL that you're running?

SELECT @@Version

Jeff Moden (6/6/2010)

---

It is possible that someone disabled the unique constraint, added data, and then reenabled the constraint with WITH NOCHECK activated (IIRC).

Rob44 (3/8/2010)

---

Let's suppose the command returns 0! What's the next step if the rebuild of the index in the maintenance plan is unsuccessful?

magasvs (6/5/2010)

---

Try to recreate index with option IGNORE_DUP_KEY = ON (CREATE INDEX ... WITH DROP_EXISTING = ON, IGNORE_DUP_KEY = ON )

GilaMonster (6/5/2010)

---

Please run the following and post the full and complete output:

DBCC CHECKDB (<Database Name>) WITH NO_INFOMSGS, ALL_ERRORMSGS

What's the exact version of SQL that you're running?

SELECT @@Version

Brandie Tarvin (6/3/2010)

---

All,

This is a duplicate thread. Responses can be found at Fatal Error.

Brandie Tarvin (6/2/2010)

---

Check your server's Event Viewer for errors and warnings from around the time of this error.

Steve Jones - Editor (5/28/2010)

---

Lowell's summarized things well. You need a parsing application to strip out the HTML and get the data.