This morning my database went into suspect mode. I reverted back to last night's full backup to get it back online. I went through the error log and found the last command that appeared to cause the suspect mode was on a
MERGE on a particular table. I ran
DBCC CHECKTABLE on the table and got back the following
Msg 2511, Level 16, State 1, Line 1 Table error: Object ID 1253579504, index ID 7, partition ID 72057594230341632, alloc unit ID 72057594364887040 (type In-row data). Keys out of order on page (1:14254237), slots 184 and 185. There are 366539002 rows in 3425599 pages for object "PJM_Prices". CHECKTABLE found 0 allocation errors and 1 consistency errors in table 'PJM_Prices' (object ID 1253579504). repair_rebuild is the minimum repair level for the errors found by DBCC CHECKTABLE (CaisoAnalyzer.dbo.PJM_Prices). DBCC execution completed. If DBCC printed error messages, contact your system administrator.
Internal database snapshot has split point LSN = 001935ad:00001bf6:0001 and first LSN = 001935ad:00001bf5:0001
Is there possibly a way to put just that table in single user mode or some other trick where I don't have to go into single user mode for the whole database?