Error  3414 
Severity Level  10 
Message Text
Database '%.*ls' (database ID %d) could not recover. Contact Technical Support for further instructions.

Explanation
During startup, Microsoft® SQL Server™ could not complete the recovery of the specified database.

Action
To determine why recovery failed, examine the error log for any errors prior to error  3414 . It is important to examine errors that occurred before the first occurrence of error  3414  because subsequent attempts to start the server might not give the detailed error information you need to diagnose the problem. If you do not have sufficient information to recover from the previous errors, you can recover from known clean backups, or you can contact your primary support provider for assistance. Note that you cannot use the database until whatever caused the error has been corrected.

Error  2511 
Severity Level  16  
Message Text
Table Corrupt: Object ID %d, Index ID %d. Keys out of order on page %S_PGID, slots %d and %d.

Table error: Object ID %d, Index ID %d. Keys out of order on page %S_PGID, slots %d and %d.

Explanation
This error occurs when an index is not ordered correctly. The %S_PGID variable can be a data page (for clustered indexes), an index page, or a leaf page.

Action
The fastest way to resolve this problem is to execute DBCC CHECKDB with the REPAIR_REBUILD clause. This fixes any index corruption in the entire database. If the database is so large that you do not want to run DBCC CHECKDB, use these instructions to locate the specific table that is corrupt. Then, execute DBCC CHECKTABLE with the REPAIR_REBUILD clause for that table.



Important  If executing DBCC CHECKDB or DBCC CHECKTABLE with the REPAIR_REBUILD clause does not correct the index problem or if you are unsure what effect either of these DBCC statements with the REPAIR_REBUILD clause has on your data, contact your primary support provider.


Follow these steps: 

Note the object ID.


If the object with the error is not a system table (its object ID is more than  100 ), continue with the next step.


If the object with the error is a system table (its object ID is less than  100 ), you cannot drop the index. Restore the database from a known clean backup. 


Find the name of the index involved, as follows: 
USE master
GO
SELECT name 
FROM sysindexes
WHERE indid = index_id
    AND id = object_id

Drop and re-create the index.


Run DBCC CHECKTABLE on the affected table to verify that all problems have been resolved at the table level. 
If problems persist, contact your primary support provider. Have the output from either DBCC CHECKDB or DBCC CHECKTABLE available for review.