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 |
carparks
Starting Member
11 Posts |
Posted - 2010-12-20 : 08:47:19
|
Can someone please let me know how severe this is. TIADBCC results for 'i3_eic'.Service Broker Msg 9675, State 1: Message Types analyzed: 14.Service Broker Msg 9676, State 1: Service Contracts analyzed: 6.Service Broker Msg 9667, State 1: Services analyzed: 3.Service Broker Msg 9668, State 1: Service Queues analyzed: 3.Service Broker Msg 9669, State 1: Conversation Endpoints analyzed: 0.Service Broker Msg 9674, State 1: Conversation Groups analyzed: 0.Service Broker Msg 9670, State 1: Remote Service Bindings analyzed: 0.Msg 8966, Level 16, State 2, Line 1Unable to read and latch page (1:5354592) with latch type SH. 23(Data error (cyclic redundancy check).) failed. Msg 8966, Level 16, State 2, Line 1Unable to read and latch page (1:5366519) with latch type SH. 23(Data error (cyclic redundancy check).) failed. Msg 8966, Level 16, State 2, Line 1Unable to read and latch page (1:5489079) with latch type SH. 23(Data error (cyclic redundancy check).) failed. Msg 8966, Level 16, State 2, Line 1Unable to read and latch page (1:5610478) with latch type SH. 23(Data error (cyclic redundancy check).) failed. Msg 8966, Level 16, State 2, Line 1Unable to read and latch page (1:5610486) with latch type SH. 23(Data error (cyclic redundancy check).) failed. Msg 8966, Level 16, State 2, Line 1Unable to read and latch page (1:5611752) with latch type SH. 23(Data error (cyclic redundancy check).) failed. Msg 8966, Level 16, State 2, Line 1Unable to read and latch page (1:5616599) with latch type SH. 23(Data error (cyclic redundancy check).) failed. Msg 8966, Level 16, State 2, Line 1Unable to read and latch page (1:5623037) with latch type SH. 23(Data error (cyclic redundancy check).) failed. Msg 8966, Level 16, State 2, Line 1Unable to read and latch page (1:5623045) with latch type SH. 23(Data error (cyclic redundancy check).) failed. CHECKDB found 0 allocation errors and 9 consistency errors not associated with any single object.DBCC results for 'sys.sysrowsetcolumns'.There are 2539 rows in 23 pages for object "sys.sysrowsetcolumns".DBCC results for 'sys.sysrowsets'.There are 354 rows in 3 pages for object "sys.sysrowsets".DBCC results for 'sysallocunits'.There are 370 rows in 7 pages for object "sysallocunits".DBCC results for 'sys.sysfiles1'.There are 2 rows in 1 pages for object "sys.sysfiles1".DBCC results for 'sys.syshobtcolumns'.There are 2539 rows in 25 pages for object "sys.syshobtcolumns".DBCC results for 'sys.syshobts'.There are 354 rows in 3 pages for object "sys.syshobts".DBCC results for 'sys.sysftinds'.There are 0 rows in 0 pages for object "sys.sysftinds".DBCC results for 'sys.sysserefs'.There are 370 rows in 3 pages for object "sys.sysserefs".DBCC results for 'sys.sysowners'.There are 23 rows in 1 pages for object "sys.sysowners".DBCC results for 'sys.sysprivs'.There are 179 rows in 1 pages for object "sys.sysprivs".DBCC results for 'sys.sysschobjs'.There are 1227 rows in 28 pages for object "sys.sysschobjs".DBCC results for 'sys.syscolpars'.There are 7024 rows in 223 pages for object "sys.syscolpars".DBCC results for 'sys.sysnsobjs'.There are 1 rows in 1 pages for object "sys.sysnsobjs".DBCC results for 'sys.syscerts'.There are 0 rows in 0 pages for object "sys.syscerts".DBCC results for 'sys.sysxprops'.There are 9 rows in 1 pages for object "sys.sysxprops".DBCC results for 'sys.sysscalartypes'.There are 27 rows in 1 pages for object "sys.sysscalartypes".DBCC results for 'sys.systypedsubobjs'.There are 0 rows in 0 pages for object "sys.systypedsubobjs".DBCC results for 'sys.sysidxstats'.There are 759 rows in 12 pages for object "sys.sysidxstats".DBCC results for 'sys.sysiscols'.There are 1290 rows in 7 pages for object "sys.sysiscols".DBCC results for 'sys.sysbinobjs'.There are 23 rows in 1 pages for object "sys.sysbinobjs".DBCC results for 'sys.sysobjvalues'.There are 1590 rows in 618 pages for object "sys.sysobjvalues".DBCC results for 'sys.sysclsobjs'.There are 16 rows in 1 pages for object "sys.sysclsobjs".DBCC results for 'sys.sysrowsetrefs'.There are 0 rows in 0 pages for object "sys.sysrowsetrefs".DBCC results for 'sys.sysremsvcbinds'.There are 0 rows in 0 pages for object "sys.sysremsvcbinds".DBCC results for 'sys.sysxmitqueue'.There are 0 rows in 0 pages for object "sys.sysxmitqueue".DBCC results for 'sys.sysrts'.There are 1 rows in 1 pages for object "sys.sysrts".DBCC results for 'sys.sysconvgroup'.There are 0 rows in 0 pages for object "sys.sysconvgroup".DBCC results for 'sys.sysdesend'.There are 0 rows in 0 pages for object "sys.sysdesend".DBCC results for 'sys.sysdercv'.There are 0 rows in 0 pages for object "sys.sysdercv".DBCC results for 'sys.syssingleobjrefs'.There are 451 rows in 4 pages for object "sys.syssingleobjrefs".DBCC results for 'sys.sysmultiobjrefs'.There are 6510 rows in 75 pages for object "sys.sysmultiobjrefs".DBCC results for 'sys.sysdbfiles'.There are 2 rows in 1 pages for object "sys.sysdbfiles".DBCC results for 'sys.sysguidrefs'.There are 0 rows in 0 pages for object "sys.sysguidrefs".DBCC results for 'sys.sysqnames'.There are 91 rows in 1 pages for object "sys.sysqnames".DBCC results for 'sys.sysxmlcomponent'.There are 93 rows in 1 pages for object "sys.sysxmlcomponent".DBCC results for 'sys.sysxmlfacet'.There are 97 rows in 1 pages for object "sys.sysxmlfacet".DBCC results for 'sys.sysxmlplacement'.There are 17 rows in 1 pages for object "sys.sysxmlplacement".DBCC results for 'sys.sysobjkeycrypts'.There are 0 rows in 0 pages for object "sys.sysobjkeycrypts".DBCC results for 'sys.sysasymkeys'.There are 0 rows in 0 pages for object "sys.sysasymkeys".DBCC results for 'sys.syssqlguides'.There are 0 rows in 0 pages for object "sys.syssqlguides".DBCC results for 'sys.sysbinsubobjs'.There are 0 rows in 0 pages for object "sys.sysbinsubobjs".DBCC results for 'IndivType'.There are 8 rows in 1 pages for object "IndivType".DBCC results for 'InteractionAttribute'.There are 0 rows in 0 pages for object "InteractionAttribute".DBCC results for 'IAChangeLog'.There are 9015 rows in 125 pages for object "IAChangeLog".DBCC results for 'IntxAnnotation'.There are 30 rows in 3 pages for object "IntxAnnotation".DBCC results for 'IWrkgrpQueueStats'.There are 1257494 rows in 65617 pages for object "IWrkgrpQueueStats".DBCC results for 'IVRInterval'.There are 170950 rows in 2338 pages for object "IVRInterval".DBCC results for 'IntxSegment'.Msg 8978, Level 16, State 1, Line 1Table error: Object ID 114099447, index ID 1, partition ID 288952598069248, alloc unit ID 288952598069248 (type In-row data). Page (1:5354174) is missing a reference from previous page (1:5354592). Possible chain linkage problem.Msg 2533, Level 16, State 1, Line 1Table error: page (1:5354592) allocated to object ID 114099447, index ID 1, partition ID 288952598069248, alloc unit ID 288952598069248 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.Msg 8976, Level 16, State 1, Line 1Table error: Object ID 114099447, index ID 1, partition ID 288952598069248, alloc unit ID 288952598069248 (type In-row data). Page (1:5354592) was not seen in the scan although its parent (1:5355234) and previous (1:5354173) refer to it. Check any previous errors.Msg 2533, Level 16, State 1, Line 1Table error: page (1:5366519) allocated to object ID 114099447, index ID 1, partition ID 288952598069248, alloc unit ID 288952598069248 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.Msg 8976, Level 16, State 1, Line 1Table error: Object ID 114099447, index ID 1, partition ID 288952598069248, alloc unit ID 288952598069248 (type In-row data). Page (1:5366519) was not seen in the scan although its parent (1:5367641) and previous (1:5366545) refer to it. Check any previous errors.Msg 8978, Level 16, State 1, Line 1Table error: Object ID 114099447, index ID 1, partition ID 288952598069248, alloc unit ID 288952598069248 (type In-row data). Page (1:5366547) is missing a reference from previous page (1:5366519). Possible chain linkage problem.There are 5546193 rows in 1058871 pages for object "IntxSegment".CHECKDB found 0 allocation errors and 6 consistency errors in table 'IntxSegment' (object ID 114099447).DBCC results for 'IVRHistory'.There are 4414463 rows in 45631 pages for object "IVRHistory".DBCC results for 'IntxType'.There are 7 rows in 1 pages for object "IntxType".DBCC results for 'IStatsGroup'.There are 389068 rows in 16760 pages for object "IStatsGroup".DBCC results for 'Intx_Participant'.There are 11091749 rows in 416038 pages for object "Intx_Participant".DBCC results for 'IWrapUpStats'.There are 1759351 rows in 19933 pages for object "IWrapUpStats".DBCC results for 'LocAddress'.There are 0 rows in 0 pages for object "LocAddress".DBCC results for 'IAgentQueueStats'.Msg 2533, Level 16, State 1, Line 1Table error: page (1:5623037) allocated to object ID 245575913, index ID 1, partition ID 297569039745024, alloc unit ID 297569039745024 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.Msg 8976, Level 16, State 1, Line 1Table error: Object ID 245575913, index ID 1, partition ID 297569039745024, alloc unit ID 297569039745024 (type In-row data). Page (1:5623037) was not seen in the scan although its parent (1:5623798) and previous (1:5623036) refer to it. Check any previous errors.Msg 8978, Level 16, State 1, Line 1Table error: Object ID 245575913, index ID 1, partition ID 297569039745024, alloc unit ID 297569039745024 (type In-row data). Page (1:5623038) is missing a reference from previous page (1:5623037). Possible chain linkage problem.Msg 2533, Level 16, State 1, Line 1Table error: page (1:5623045) allocated to object ID 245575913, index ID 2, partition ID 579044016455680, alloc unit ID 579044016455680 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.Msg 8976, Level 16, State 1, Line 1Table error: Object ID 245575913, index ID 2, partition ID 579044016455680, alloc unit ID 579044016455680 (type In-row data). Page (1:5623045) was not seen in the scan although its parent (1:6562039) and previous (1:5697474) refer to it. Check any previous errors.Msg 8978, Level 16, State 1, Line 1Table error: Object ID 245575913, index ID 2, partition ID 579044016455680, alloc unit ID 579044016455680 (type In-row data). Page (1:5662705) is missing a reference from previous page (1:5623045). Possible chain linkage problem.There are 22526268 rows in 1321706 pages for object "IAgentQueueStats".CHECKDB found 0 allocation errors and 6 consistency errors in table 'IAgentQueueStats' (object ID 245575913).DBCC results for 'AgentQueueActivationHist'.There are 1844 rows in 35 pages for object "AgentQueueActivationHist".DBCC results for 'Location'.There are 1 rows in 1 pages for object "Location".DBCC results for 'CallDetail'.Msg 2533, Level 16, State 1, Line 1Table error: page (1:5489079) allocated to object ID 325576198, index ID 1, partition ID 302811938422784, alloc unit ID 302811938422784 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.Msg 8976, Level 16, State 1, Line 1Table error: Object ID 325576198, index ID 1, partition ID 302811938422784, alloc unit ID 302811938422784 (type In-row data). Page (1:5489079) was not seen in the scan although its parent (1:5490327) and previous (1:5489078) refer to it. Check any previous errors.Msg 8978, Level 16, State 1, Line 1Table error: Object ID 325576198, index ID 1, partition ID 302811938422784, alloc unit ID 302811938422784 (type In-row data). Page (1:5489152) is missing a reference from previous page (1:5489079). Possible chain linkage problem.Msg 8978, Level 16, State 1, Line 1Table error: Object ID 325576198, index ID 1, partition ID 302811938422784, alloc unit ID 302811938422784 (type In-row data). Page (1:5610408) is missing a reference from previous page (1:5610478). Possible chain linkage problem.Msg 2533, Level 16, State 1, Line 1Table error: page (1:5610478) allocated to object ID 325576198, index ID 1, partition ID 302811938422784, alloc unit ID 302811938422784 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.Msg 8976, Level 16, State 1, Line 1Table error: Object ID 325576198, index ID 1, partition ID 302811938422784, alloc unit ID 302811938422784 (type In-row data). Page (1:5610478) was not seen in the scan although its parent (1:5611679) and previous (1:5610413) refer to it. Check any previous errors.There are 9963553 rows in 947669 pages for object "CallDetail".CHECKDB found 0 allocation errors and 6 consistency errors in table 'CallDetail' (object ID 325576198).DBCC results for 'LocAttribute'.There are 0 rows in 0 pages for object "LocAttribute".DBCC results for 'LocConnection'.There are 0 rows in 0 pages for object "LocConnection".DBCC results for 'LineConfig'.There are 267 rows in 4 pages for object "LineConfig".DBCC results for 'OrphanedRecordings'.There are 0 rows in 0 pages for object "OrphanedRecordings".DBCC results for 'LineGroupConfig'.There are 6 rows in 1 pages for object "LineGroupConfig".DBCC results for 'OrgAddress'.There are 0 rows in 0 pages for object "OrgAddress".DBCC results for 'ArchiveWork'.There are 0 rows in 0 pages for object "ArchiveWork".DBCC results for 'LineGroupLines'.There are 147 rows in 3 pages for object "LineGroupLines".DBCC results for 'ArchiveWorkTmp'.There are 0 rows in 0 pages for object "ArchiveWorkTmp".DBCC results for 'Organization'.There are 93 rows in 2 pages for object "Organization".DBCC results for 'AgentActivityLog'.There are 1461107 rows in 22709 pages for object "AgentActivityLog".DBCC results for 'Archive_Category'.There are 0 rows in 0 pages for object "Archive_Category".DBCC results for 'IO_DayClassification'.There are 10 rows in 1 pages for object "IO_DayClassification".DBCC results for 'AttributeName'.There are 18 rows in 1 pages for object "AttributeName".DBCC results for 'IO_ShiftRotation'.There are 0 rows in 1 pages for object "IO_ShiftRotation".DBCC results for 'ILineGroupStats'.There are 243780 rows in 2230 pages for object "ILineGroupStats".DBCC results for 'IO_ActivityType'.There are 10 rows in 1 pages for object "IO_ActivityType".DBCC results for 'OrgAttribute'.There are 0 rows in 0 pages for object "OrgAttribute".DBCC results for 'AuditOperation'.There are 17 rows in 1 pages for object "AuditOperation".DBCC results for 'IO_RotationShiftDefinition'.There are 0 rows in 1 pages for object "IO_RotationShiftDefinition".DBCC results for 'IO_Status'.There are 24 rows in 1 pages for object "IO_Status".DBCC results for 'OrgConnection'.There are 6 rows in 1 pages for object "OrgConnection".DBCC results for 'ILineStats'.There are 12747771 rows in 103708 pages for object "ILineStats".DBCC results for 'Category'.There are 1740 rows in 31 pages for object "Category".DBCC results for 'IO_SchedulingUnit'.There are 1 rows in 1 pages for object "IO_SchedulingUnit".DBCC results for 'AccountCodeMirror'.There are 0 rows in 0 pages for object "AccountCodeMirror".DBCC results for 'EmailFileAttachment'.There are 0 rows in 0 pages for object "EmailFileAttachment".DBCC results for 'OrgType'.There are 7 rows in 1 pages for object "OrgType".DBCC results for 'ImportRule'.There are 2 rows in 1 pages for object "ImportRule".DBCC results for 'IO_ShiftDefinition'.There are 42 rows in 1 pages for object "IO_ShiftDefinition".DBCC results for 'dtproperties'.There are 0 rows in 0 pages for object "dtproperties".DBCC results for 'Title'.There are 6 rows in 1 pages for object "Title".DBCC results for 'IRAudit'.There are 68109 rows in 1521 pages for object "IRAudit".DBCC results for 'UserObjectSecurity'.There are 8798 rows in 139 pages for object "UserObjectSecurity".DBCC results for 'RelationshipDescription'.There are 0 rows in 0 pages for object "RelationshipDescription".DBCC results for 'IRDataVersion'.There are 0 rows in 0 pages for object "IRDataVersion".DBCC results for 'LastRecording'.There are 0 rows in 0 pages for object "LastRecording".DBCC results for 'IO_Workgroup'.There are 4 rows in 1 pages for object "IO_Workgroup".DBCC results for 'Relationship'.There are 0 rows in 0 pages for object "Relationship".DBCC results for 'Object'.There are 2135 rows in 21 pages for object "Object".DBCC results for 'IO_Agent'.There are 177 rows in 6 pages for object "IO_Agent".DBCC results for 'Participant'.There are 2 rows in 1 pages for object "Participant".DBCC results for 'sys.queue_messages_919010355'.There are 0 rows in 0 pages for object "sys.queue_messages_919010355".DBCC results for 'Query'.There are 18 rows in 5 pages for object "Query".DBCC results for 'sys.queue_messages_951010469'.There are 0 rows in 0 pages for object "sys.queue_messages_951010469".DBCC results for 'sys.queue_messages_983010583'.There are 0 rows in 0 pages for object "sys.queue_messages_983010583".DBCC results for 'Question'.There are 120 rows in 5 pages for object "Question".DBCC results for 'IO_DailyConstraints'.There are 64 rows in 2 pages for object "IO_DailyConstraints".DBCC results for 'QuestionEnum'.There are 234 rows in 2 pages for object "QuestionEnum".DBCC results for 'Questionnaire'.There are 10 rows in 2 pages for object "Questionnaire".DBCC results for 'IO_TimeOffRequest'.There are 1264 rows in 43 pages for object "IO_TimeOffRequest".DBCC results for 'QuestionnaireForm'.There are 0 rows in 1 pages for object "QuestionnaireForm".DBCC results for 'IO_Activity'.Msg 8978, Level 16, State 1, Line 1Table error: Object ID 1200723330, index ID 1, partition ID 360165580865536, alloc unit ID 360165580865536 (type In-row data). Page (1:4408707) is missing a reference from previous page (1:5616599). Possible chain linkage problem.Msg 2533, Level 16, State 1, Line 1Table error: page (1:5616599) allocated to object ID 1200723330, index ID 1, partition ID 360165580865536, alloc unit ID 360165580865536 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.Msg 8976, Level 16, State 1, Line 1Table error: Object ID 1200723330, index ID 1, partition ID 360165580865536, alloc unit ID 360165580865536 (type In-row data). Page (1:5616599) was not seen in the scan although its parent (1:5425146) and previous (1:4149037) refer to it. Check any previous errors.There are 207436 rows in 7444 pages for object "IO_Activity".CHECKDB found 0 allocation errors and 3 consistency errors in table 'IO_Activity' (object ID 1200723330).DBCC results for 'QuestionnaireGroup'.There are 23 rows in 2 pages for object "QuestionnaireGroup".DBCC results for 'FaxEnvelopeHist'.There are 179530 rows in 7284 pages for object "FaxEnvelopeHist".DBCC results for 'Questionnaire_Answer'.There are 0 rows in 0 pages for object "Questionnaire_Answer".DBCC results for 'IO_NamedSchedule'.There are 91 rows in 3 pages for object "IO_NamedSchedule".DBCC results for 'RankDefn'.There are 3 rows in 2 pages for object "RankDefn".DBCC results for 'IO_Schedule'.There are 33430 rows in 919 pages for object "IO_Schedule".DBCC results for 'RankGroup'.There are 3 rows in 1 pages for object "RankGroup".DBCC results for 'IO_ScheduleInterval'.There are 577467 rows in 13429 pages for object "IO_ScheduleInterval".DBCC results for 'RecIntxParticipant'.There are 9568061 rows in 100371 pages for object "RecIntxParticipant".DBCC results for 'IO_UtilizationSettings'.There are 24 rows in 1 pages for object "IO_UtilizationSettings".DBCC results for 'RecordingArchive'.There are 364 rows in 10 pages for object "RecordingArchive".DBCC results for 'ININ_APP_VERSION'.There are 141 rows in 2 pages for object "ININ_APP_VERSION".DBCC results for 'IO_ServiceLevelSettings'.There are 4 rows in 1 pages for object "IO_ServiceLevelSettings".DBCC results for 'RecordingCall'.There are 4739558 rows in 193390 pages for object "RecordingCall".DBCC results for 'RecordingChat'.There are 13 rows in 1 pages for object "RecordingChat".DBCC results for 'RecordingData'.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 102442769711104 (type In-row data). Parent node for page (1:159227) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 102442769711104 (type In-row data). Parent node for page (1:164382) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 102442769711104 (type In-row data). Parent node for page (1:456922) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 102442769711104 (type In-row data). Parent node for page (1:728376) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 102442769711104 (type In-row data). Parent node for page (1:742612) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 102442769711104 (type In-row data). Parent node for page (1:828614) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 102442769711104 (type In-row data). Parent node for page (1:883079) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 102442769711104 (type In-row data). Parent node for page (1:1037443) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 102442769711104 (type In-row data). Parent node for page (1:1143495) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 102442769711104 (type In-row data). Parent node for page (1:1146714) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 102442769711104 (type In-row data). Parent node for page (1:1218264) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 102442769711104 (type In-row data). Parent node for page (1:1225055) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 102442769711104 (type In-row data). Parent node for page (1:1258003) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 102442769711104 (type In-row data). Parent node for page (1:1331249) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 102442769711104 (type In-row data). Parent node for page (1:1386269) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 102442769711104 (type In-row data). Parent node for page (1:1419420) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 102442769711104 (type In-row data). Parent node for page (1:1420871) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 102442769711104 (type In-row data). Parent node for page (1:1422086) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 102442769711104 (type In-row data). Parent node for page (1:1423994) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 102442769711104 (type In-row data). Parent node for page (1:1445268) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 102442769711104 (type In-row data). Parent node for page (1:1450199) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 102442769711104 (type In-row data). Parent node for page (1:1495629) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 102442769711104 (type In-row data). Parent node for page (1:1499364) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 102442769711104 (type In-row data). Parent node for page (1:1665710) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 102442769711104 (type In-row data). Parent node for page (1:1706842) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 102442769711104 (type In-row data). Parent node for page (1:1793601) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 102442769711104 (type In-row data). Parent node for page (1:1801551) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 102442769711104 (type In-row data). Parent node for page (1:1806131) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 102442769711104 (type In-row data). Parent node for page (1:1807520) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 102442769711104 (type In-row data). Parent node for page (1:1816278) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 102442769711104 (type In-row data). Parent node for page (1:1822701) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 102442769711104 (type In-row data). Parent node for page (1:1853586) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 102442769711104 (type In-row data). Parent node for page (1:1857019) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 102442769711104 (type In-row data). Parent node for page (1:1863961) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 102442769711104 (type In-row data). Parent node for page (1:1890000) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:165211) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:283620) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:462759) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:1364386) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:1572136) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:1582560) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:1608596) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:1978218) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:1986616) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:2001963) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:2005247) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:2013703) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:2021499) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:2027000) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:2032180) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:2039419) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:2046111) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:2052496) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:2090172) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:2112529) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:2201224) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:2219323) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:2231167) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:2256309) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:2267086) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:2269854) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:2280122) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:2300411) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:2321014) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:2326533) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:2378540) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:2391129) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:2433613) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:2456692) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:2466277) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:2481906) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:2574212) was not encountered.Msg 8978, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Page (1:2613748) is missing a reference from previous page (1:5610486). Possible chain linkage problem.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:2675407) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:2700734) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:2857052) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:2909705) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:3094583) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:3115661) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:3125275) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:3143489) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:3180560) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:3184056) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:3231943) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:3250905) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:3281868) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:3342370) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:3360505) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:3423924) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:3424460) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:3455178) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:3501839) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:3518067) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:3526918) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:3664014) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:3675310) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:3713873) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:3752950) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:3759423) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:3773399) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:3812131) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:3857273) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:3900168) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:3903272) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:3917663) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:3939337) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:3968914) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:4033412) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:4042691) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:4097697) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:4140582) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:4217095) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:4281854) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:4290672) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:4294885) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:4326208) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:4347208) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:4382781) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:4440920) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:4475177) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:4511346) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:4617820) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:4624495) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:4812631) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:4829366) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:4903517) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:4925629) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:4930008) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:5101268) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:5101417) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:5230082) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:5238761) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:5265251) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:5305603) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:5363068) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:5427295) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:5461077) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:5482191) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:5495374) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:5514605) was not encountered.Msg 2533, Level 16, State 1, Line 1Table error: page (1:5610486) allocated to object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.Msg 8976, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Page (1:5610486) was not seen in the scan although its parent (1:2861743) and previous (1:1808617) refer to it. Check any previous errors.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:5610487) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:5622528) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:5668295) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:5699074) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:5778129) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:5807914) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:5823431) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:5842015) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:5897039) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:5913779) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:5925340) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:6084307) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:6111730) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:6117707) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:6122167) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:6158765) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:6250562) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:6267592) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:6276599) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:6398152) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:6475045) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:6479338) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:6479568) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:6480012) was not encountered.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:6496407) was not encountered.There are 4740364 rows in 311925 pages for object "RecordingData".CHECKDB found 0 allocation errors and 167 consistency errors in table 'RecordingData' (object ID 1563152614).DBCC results for 'IO_ForecastScheduleEntry'.There are 90 rows in 2 pages for object "IO_ForecastScheduleEntry".DBCC results for 'RecordingEmail'.There are 0 rows in 0 pages for object "RecordingEmail".DBCC results for 'IO_DayClassOverride'.There are 1 rows in 1 pages for object "IO_DayClassOverride".DBCC results for 'RecordingError'.There are 72 rows in 1 pages for object "RecordingError".DBCC results for 'IO_RTAException'.There are 346436 rows in 20952 pages for object "IO_RTAException".DBCC results for 'RecordingFax'.There are 792 rows in 37 pages for object "RecordingFax".DBCC results for 'IO_VolumeForecast'.There are 90 rows in 2 pages for object "IO_VolumeForecast".DBCC results for 'RecordedRule'.Msg 2533, Level 16, State 1, Line 1Table error: page (1:5611752) allocated to object ID 1691153070, index ID 0, partition ID 110831407595520, alloc unit ID 110831407595520 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.There are 6605032 rows in 85798 pages for object "RecordedRule".CHECKDB found 0 allocation errors and 1 consistency errors in table 'RecordedRule' (object ID 1691153070).DBCC results for 'RecordingWork'.There are 0 rows in 3 pages for object "RecordingWork".DBCC results for 'IO_DaySelection'.There are 2500 rows in 52 pages for object "IO_DaySelection".DBCC results for 'RecordingUserPref'.There are 0 rows in 0 pages for object "RecordingUserPref".DBCC results for 'IO_VolumeForecastStats'.There are 181800 rows in 5560 pages for object "IO_VolumeForecastStats".DBCC results for 'Recording_Attribute'.There are 17 rows in 4 pages for object "Recording_Attribute".DBCC results for 'ScreenRecordingData'.There are 0 rows in 0 pages for object "ScreenRecordingData".DBCC results for 'IO_HeadcountForecast'.There are 91 rows in 2 pages for object "IO_HeadcountForecast".DBCC results for 'ScreenRecParticipant'.There are 0 rows in 0 pages for object "ScreenRecParticipant".DBCC results for 'IO_HeadcountForecastStats'.There are 140959 rows in 6837 pages for object "IO_HeadcountForecastStats".DBCC results for 'AddrType'.There are 4 rows in 1 pages for object "AddrType".DBCC results for 'sysdiagrams'.There are 0 rows in 0 pages for object "sysdiagrams".DBCC results for 'ScreenRecParticipantHold'.There are 0 rows in 0 pages for object "ScreenRecParticipantHold".DBCC results for 'AttributeType'.There are 2 rows in 1 pages for object "AttributeType".DBCC results for 'TemplateParam'.There are 68 rows in 5 pages for object "TemplateParam".DBCC results for 'ConnectionType'.There are 7 rows in 1 pages for object "ConnectionType".DBCC results for 'ConnSubType'.There are 6 rows in 1 pages for object "ConnSubType".DBCC results for 'IndivAddress'.There are 0 rows in 0 pages for object "IndivAddress".DBCC results for 'UserQueryTemplateInfo'.There are 1 rows in 1 pages for object "UserQueryTemplateInfo".DBCC results for 'Contacts'.There are 373 rows in 15 pages for object "Contacts".DBCC results for 'IRChangeVersion'.There are 1418 rows in 25 pages for object "IRChangeVersion".DBCC results for 'IndivAttribute'.There are 8306 rows in 178 pages for object "IndivAttribute".DBCC results for 'SpeedDialList'.There are 21 rows in 1 pages for object "SpeedDialList".DBCC results for 'RecordingWorkControl'.There are 0 rows in 3 pages for object "RecordingWorkControl".DBCC results for 'IndivConnection'.There are 52518 rows in 905 pages for object "IndivConnection".DBCC results for 'SpeedDial'.There are 76 rows in 3 pages for object "SpeedDial".DBCC results for 'UnprocRecordingData'.There are 3238094 rows in 234956 pages for object "UnprocRecordingData".DBCC results for 'Individual'.There are 34409 rows in 1493 pages for object "Individual".DBCC results for 'UserWorkgroups'.There are 756 rows in 6 pages for object "UserWorkgroups".DBCC results for 'ICDirChangeLog'.There are 1909096 rows in 39933 pages for object "ICDirChangeLog".CHECKDB found 0 allocation errors and 198 consistency errors in database 'i3_eic'.repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (i3_eic).DBCC execution completed. If DBCC printed error messages, contact your system administrator. |
|
Swaynebell
Starting Member
8 Posts |
Posted - 2010-12-20 : 13:39:28
|
Hi,I'm confident that an expert such as Gail or Paul will be by shortly to help.They will likely ask if you have a restorable non-corrupted backup because many of these messages indicate issues with your base tables.The course of action suggested by DBCC CHECK DB of repair_allow_data_loss is consistent with this. However, do not run the repair before talking to an expert. If you have to, contact Microsoft instead of waiting for a reply here.Gail has an excellent article that shows some of the errors you are getting, along with explanations of what they mean.[url]http://www.sqlservercentral.com/articles/Corruption/65804/[/url] |
|
|
carparks
Starting Member
11 Posts |
Posted - 2010-12-20 : 13:54:00
|
Thanks for the info. I do have a good backup, but it is about a month old. I'll check out the link you sent and wait for a reply from the aforementioned experts. I'm hoping it can be fixed without having to do a restore, but I'm sure it won't be that easy. |
|
|
GilaMonster
Master Smack Fu Yak Hacker
4507 Posts |
Posted - 2010-12-20 : 15:57:51
|
You have two choices.1)Restore from a clean backup2)Repair and lose data from the following tables: IntxSegment, IAgentQueueStats, CallDetail, IO_Activity, RecordingData (lots of damage to this table), RecordedRule. It's difficult-impossible to say what or how much will be lost.You can also try something more complex like repair then restore the old DB alongside and sync the tables, but that's lots of work and there's always the chance of messing up.With no up-to-date clean backup you are losing data from this. Your choice (or maybe better your boss's choice) which data loss is preferred.Once you've got this sorted out, schedule regular consistency checks so that you have the option of restoring an d not losing a month's data.--Gail ShawSQL Server MVP |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
carparks
Starting Member
11 Posts |
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
carparks
Starting Member
11 Posts |
Posted - 2010-12-20 : 19:34:10
|
quote: Originally posted by GilaMonster You have two choices.1)Restore from a clean backup2)Repair and lose data from the following tables: IntxSegment, IAgentQueueStats, CallDetail, IO_Activity, RecordingData (lots of damage to this table), RecordedRule. It's difficult-impossible to say what or how much will be lost.You can also try something more complex like repair then restore the old DB alongside and sync the tables, but that's lots of work and there's always the chance of messing up.With no up-to-date clean backup you are losing data from this. Your choice (or maybe better your boss's choice) which data loss is preferred.Once you've got this sorted out, schedule regular consistency checks so that you have the option of restoring an d not losing a month's data.--Gail ShawSQL Server MVP
Thanks for the info Gail. How would I go about doing option 2? |
|
|
carparks
Starting Member
11 Posts |
|
GilaMonster
Master Smack Fu Yak Hacker
4507 Posts |
Posted - 2010-12-21 : 01:53:00
|
quote: Originally posted by carparksIn looking at the backup history, when the backups failed, one day it backed up with no issue, and then the next night it failed and kept failing. So I'm just assuming that the night before the bad backup, has complete data with no corruptions.
Maybe but not necessarily. Unless you're doing the backups with checksum, corruptions won't necessarily fail a backup. It's perfectly possible for SQL to back the database up successfully even if there's corruption. That's why I always recommend running checkDB before a backup to be sure that what you're backing up is good.The only date you can be sure the DB was good was the last time checkDB ran without error. When was that?How do backups fail for a whole month without someone investigating?--Gail ShawSQL Server MVP |
|
|
GilaMonster
Master Smack Fu Yak Hacker
4507 Posts |
Posted - 2010-12-21 : 01:58:28
|
quote: Originally posted by carparks Thanks for the info Gail. How would I go about doing option 2?
Take the DB into single user mode and runDBCC CheckDB (<database name>, REPAIR_ALLOW_DATA_LOSS)Caveats: It WILL lose data. A fair bit from some of those tablesIt will not take referential integrity into account. You could end up with orphaned rowsIt will not fire triggers or check constraints.Edit: Corrected command--Gail ShawSQL Server MVP |
|
|
carparks
Starting Member
11 Posts |
Posted - 2010-12-21 : 23:45:31
|
When I try to run DBCC CHECKDB (i3_eic) WITH REPAIR_ALLOW_DATA_LOSS, it immediately gives me the error - Msg 195, Level 15, State 4, Line 1'REPAIR_ALLOW_DATA_LOSS' is not a recognized option.Am I missing something? |
|
|
carparks
Starting Member
11 Posts |
Posted - 2010-12-22 : 00:16:58
|
Nevermind, I ran DBCC CHECKDB (i3_eic, REPAIR_ALLOW_DATA_LOSS) and it started going. |
|
|
carparks
Starting Member
11 Posts |
Posted - 2010-12-22 : 06:58:50
|
Here are the results from my checkdb with repair allow data loss. Anything good from this? It says it was able to repair/rebuild some things.DBCC results for 'i3_eic'.Service Broker Msg 9675, State 1: Message Types analyzed: 14.Service Broker Msg 9676, State 1: Service Contracts analyzed: 6.Service Broker Msg 9667, State 1: Services analyzed: 3.Service Broker Msg 9668, State 1: Service Queues analyzed: 3.Service Broker Msg 9669, State 1: Conversation Endpoints analyzed: 0.Service Broker Msg 9674, State 1: Conversation Groups analyzed: 0.Service Broker Msg 9670, State 1: Remote Service Bindings analyzed: 0.Msg 8966, Level 16, State 2, Line 1Unable to read and latch page (1:5354592) with latch type SH. 23(Data error (cyclic redundancy check).) failed. Msg 8966, Level 16, State 2, Line 1Unable to read and latch page (1:5366519) with latch type SH. 23(Data error (cyclic redundancy check).) failed. Msg 8966, Level 16, State 2, Line 1Unable to read and latch page (1:5489079) with latch type SH. 23(Data error (cyclic redundancy check).) failed. Msg 8966, Level 16, State 2, Line 1Unable to read and latch page (1:5610478) with latch type SH. 23(Data error (cyclic redundancy check).) failed. Msg 8966, Level 16, State 2, Line 1Unable to read and latch page (1:5610486) with latch type SH. 23(Data error (cyclic redundancy check).) failed. Msg 8966, Level 16, State 2, Line 1Unable to read and latch page (1:5611752) with latch type SH. 23(Data error (cyclic redundancy check).) failed. Msg 8966, Level 16, State 2, Line 1Unable to read and latch page (1:5616599) with latch type SH. 23(Data error (cyclic redundancy check).) failed. Msg 8966, Level 16, State 2, Line 1Unable to read and latch page (1:5623037) with latch type SH. 23(Data error (cyclic redundancy check).) failed. Msg 8966, Level 16, State 2, Line 1Unable to read and latch page (1:5623045) with latch type SH. 23(Data error (cyclic redundancy check).) failed. CHECKDB found 0 allocation errors and 9 consistency errors not associated with any single object.DBCC results for 'sys.sysrowsetcolumns'.There are 2539 rows in 23 pages for object "sys.sysrowsetcolumns".DBCC results for 'sys.sysrowsets'.There are 354 rows in 3 pages for object "sys.sysrowsets".DBCC results for 'sysallocunits'.There are 370 rows in 7 pages for object "sysallocunits".DBCC results for 'sys.sysfiles1'.There are 2 rows in 1 pages for object "sys.sysfiles1".DBCC results for 'sys.syshobtcolumns'.There are 2539 rows in 25 pages for object "sys.syshobtcolumns".DBCC results for 'sys.syshobts'.There are 354 rows in 3 pages for object "sys.syshobts".DBCC results for 'sys.sysftinds'.There are 0 rows in 0 pages for object "sys.sysftinds".DBCC results for 'sys.sysserefs'.There are 370 rows in 3 pages for object "sys.sysserefs".DBCC results for 'sys.sysowners'.There are 23 rows in 1 pages for object "sys.sysowners".DBCC results for 'sys.sysprivs'.There are 179 rows in 1 pages for object "sys.sysprivs".DBCC results for 'sys.sysschobjs'.There are 1227 rows in 28 pages for object "sys.sysschobjs".DBCC results for 'sys.syscolpars'.There are 7024 rows in 223 pages for object "sys.syscolpars".DBCC results for 'sys.sysnsobjs'.There are 1 rows in 1 pages for object "sys.sysnsobjs".DBCC results for 'sys.syscerts'.There are 0 rows in 0 pages for object "sys.syscerts".DBCC results for 'sys.sysxprops'.There are 9 rows in 1 pages for object "sys.sysxprops".DBCC results for 'sys.sysscalartypes'.There are 27 rows in 1 pages for object "sys.sysscalartypes".DBCC results for 'sys.systypedsubobjs'.There are 0 rows in 0 pages for object "sys.systypedsubobjs".DBCC results for 'sys.sysidxstats'.There are 759 rows in 12 pages for object "sys.sysidxstats".DBCC results for 'sys.sysiscols'.There are 1290 rows in 7 pages for object "sys.sysiscols".DBCC results for 'sys.sysbinobjs'.There are 23 rows in 1 pages for object "sys.sysbinobjs".DBCC results for 'sys.sysobjvalues'.There are 1590 rows in 619 pages for object "sys.sysobjvalues".DBCC results for 'sys.sysclsobjs'.There are 16 rows in 1 pages for object "sys.sysclsobjs".DBCC results for 'sys.sysrowsetrefs'.There are 0 rows in 0 pages for object "sys.sysrowsetrefs".DBCC results for 'sys.sysremsvcbinds'.There are 0 rows in 0 pages for object "sys.sysremsvcbinds".DBCC results for 'sys.sysxmitqueue'.There are 0 rows in 0 pages for object "sys.sysxmitqueue".DBCC results for 'sys.sysrts'.There are 1 rows in 1 pages for object "sys.sysrts".DBCC results for 'sys.sysconvgroup'.There are 0 rows in 0 pages for object "sys.sysconvgroup".DBCC results for 'sys.sysdesend'.There are 0 rows in 0 pages for object "sys.sysdesend".DBCC results for 'sys.sysdercv'.There are 0 rows in 0 pages for object "sys.sysdercv".DBCC results for 'sys.syssingleobjrefs'.There are 451 rows in 4 pages for object "sys.syssingleobjrefs".DBCC results for 'sys.sysmultiobjrefs'.There are 6510 rows in 75 pages for object "sys.sysmultiobjrefs".DBCC results for 'sys.sysdbfiles'.There are 2 rows in 1 pages for object "sys.sysdbfiles".DBCC results for 'sys.sysguidrefs'.There are 0 rows in 0 pages for object "sys.sysguidrefs".DBCC results for 'sys.sysqnames'.There are 91 rows in 1 pages for object "sys.sysqnames".DBCC results for 'sys.sysxmlcomponent'.There are 93 rows in 1 pages for object "sys.sysxmlcomponent".DBCC results for 'sys.sysxmlfacet'.There are 97 rows in 1 pages for object "sys.sysxmlfacet".DBCC results for 'sys.sysxmlplacement'.There are 17 rows in 1 pages for object "sys.sysxmlplacement".DBCC results for 'sys.sysobjkeycrypts'.There are 0 rows in 0 pages for object "sys.sysobjkeycrypts".DBCC results for 'sys.sysasymkeys'.There are 0 rows in 0 pages for object "sys.sysasymkeys".DBCC results for 'sys.syssqlguides'.There are 0 rows in 0 pages for object "sys.syssqlguides".DBCC results for 'sys.sysbinsubobjs'.There are 0 rows in 0 pages for object "sys.sysbinsubobjs".DBCC results for 'IndivType'.There are 8 rows in 1 pages for object "IndivType".DBCC results for 'InteractionAttribute'.There are 0 rows in 0 pages for object "InteractionAttribute".DBCC results for 'IAChangeLog'.There are 9134 rows in 127 pages for object "IAChangeLog".DBCC results for 'IntxAnnotation'.There are 30 rows in 3 pages for object "IntxAnnotation".DBCC results for 'IWrkgrpQueueStats'.There are 1265893 rows in 66056 pages for object "IWrkgrpQueueStats".DBCC results for 'IVRInterval'.There are 171902 rows in 2351 pages for object "IVRInterval".DBCC results for 'IntxSegment'.Repair: The Clustered index successfully rebuilt for the object "dbo.IntxSegment" in database "i3_eic".Repair: The page (1:5354592) has been deallocated from object ID 114099447, index ID 1, partition ID 288952598069248, alloc unit ID 288952598069248 (type In-row data).Repair: The page (1:5366519) has been deallocated from object ID 114099447, index ID 1, partition ID 288952598069248, alloc unit ID 288952598069248 (type In-row data).Repair: The Nonclustered index successfully rebuilt for the object "dbo.IntxSegment, PK_IntxSegment" in database "i3_eic".Repair: The Nonclustered index successfully rebuilt for the object "dbo.IntxSegment, IX_IntxSegment_AssnWrkGrp" in database "i3_eic".Repair: The Nonclustered index successfully rebuilt for the object "dbo.IntxSegment, IX_IntxSegment_AppIncID" in database "i3_eic".Msg 8945, Level 16, State 1, Line 1Table error: Object ID 114099447, index ID 1 will be rebuilt. The error has been repaired.Msg 8978, Level 16, State 1, Line 1Table error: Object ID 114099447, index ID 1, partition ID 288952598069248, alloc unit ID 288952598069248 (type In-row data). Page (1:5354174) is missing a reference from previous page (1:5354592). Possible chain linkage problem. The error has been repaired.Msg 2533, Level 16, State 1, Line 1Table error: page (1:5354592) allocated to object ID 114099447, index ID 1, partition ID 288952598069248, alloc unit ID 288952598069248 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header. The error has been repaired.Msg 8976, Level 16, State 1, Line 1Table error: Object ID 114099447, index ID 1, partition ID 288952598069248, alloc unit ID 288952598069248 (type In-row data). Page (1:5354592) was not seen in the scan although its parent (1:5355234) and previous (1:5354173) refer to it. Check any previous errors. The error has been repaired.Msg 2533, Level 16, State 1, Line 1Table error: page (1:5366519) allocated to object ID 114099447, index ID 1, partition ID 288952598069248, alloc unit ID 288952598069248 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header. The error has been repaired.Msg 8976, Level 16, State 1, Line 1Table error: Object ID 114099447, index ID 1, partition ID 288952598069248, alloc unit ID 288952598069248 (type In-row data). Page (1:5366519) was not seen in the scan although its parent (1:5367641) and previous (1:5366545) refer to it. Check any previous errors. The error has been repaired.Msg 8978, Level 16, State 1, Line 1Table error: Object ID 114099447, index ID 1, partition ID 288952598069248, alloc unit ID 288952598069248 (type In-row data). Page (1:5366547) is missing a reference from previous page (1:5366519). Possible chain linkage problem. The error has been repaired.Msg 8945, Level 16, State 1, Line 1Table error: Object ID 114099447, index ID 2 will be rebuilt. The error has been repaired.Msg 8980, Level 16, State 1, Line 1Table error: Object ID 114099447, index ID 2, partition ID 570427574779904, alloc unit ID 570427574779904 (type In-row data). Index node page (0:0), slot 0 refers to child page (1:526566) and previous child (0:0), but they were not encountered. The error has been repaired.Msg 8945, Level 16, State 1, Line 1Table error: Object ID 114099447, index ID 3 will be rebuilt. The error has been repaired.Msg 8980, Level 16, State 1, Line 1Table error: Object ID 114099447, index ID 3, partition ID 851902551490560, alloc unit ID 851902551490560 (type In-row data). Index node page (0:0), slot 0 refers to child page (1:526576) and previous child (0:0), but they were not encountered. The error has been repaired.Msg 8945, Level 16, State 1, Line 1Table error: Object ID 114099447, index ID 4 will be rebuilt. The error has been repaired.There are 5559345 rows in 1062337 pages for object "IntxSegment".CHECKDB found 0 allocation errors and 8 consistency errors in table 'IntxSegment' (object ID 114099447).CHECKDB fixed 0 allocation errors and 8 consistency errors in table 'IntxSegment' (object ID 114099447).DBCC results for 'IVRHistory'.There are 4434894 rows in 45845 pages for object "IVRHistory".DBCC results for 'IntxType'.There are 7 rows in 1 pages for object "IntxType".DBCC results for 'IStatsGroup'.There are 391936 rows in 16885 pages for object "IStatsGroup".DBCC results for 'Intx_Participant'.There are 11117959 rows in 416998 pages for object "Intx_Participant".DBCC results for 'IWrapUpStats'.There are 1769553 rows in 20049 pages for object "IWrapUpStats".DBCC results for 'LocAddress'.There are 0 rows in 0 pages for object "LocAddress".DBCC results for 'IAgentQueueStats'.Repair: The Clustered index successfully rebuilt for the object "dbo.IAgentQueueStats" in database "i3_eic".Repair: The page (1:5623037) has been deallocated from object ID 245575913, index ID 1, partition ID 297569039745024, alloc unit ID 297569039745024 (type In-row data).Repair: The Nonclustered index successfully rebuilt for the object "dbo.IAgentQueueStats, PKQueueName" in database "i3_eic".Repair: The page (1:5623045) has been deallocated from object ID 245575913, index ID 2, partition ID 579044016455680, alloc unit ID 579044016455680 (type In-row data).Repair: The Nonclustered index successfully rebuilt for the object "dbo.IAgentQueueStats, IEIntervalStart" in database "i3_eic".Msg 8945, Level 16, State 1, Line 1Table error: Object ID 245575913, index ID 1 will be rebuilt. The error has been repaired.Msg 2533, Level 16, State 1, Line 1Table error: page (1:5623037) allocated to object ID 245575913, index ID 1, partition ID 297569039745024, alloc unit ID 297569039745024 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header. The error has been repaired.Msg 8976, Level 16, State 1, Line 1Table error: Object ID 245575913, index ID 1, partition ID 297569039745024, alloc unit ID 297569039745024 (type In-row data). Page (1:5623037) was not seen in the scan although its parent (1:5623798) and previous (1:5623036) refer to it. Check any previous errors. The error has been repaired.Msg 8978, Level 16, State 1, Line 1Table error: Object ID 245575913, index ID 1, partition ID 297569039745024, alloc unit ID 297569039745024 (type In-row data). Page (1:5623038) is missing a reference from previous page (1:5623037). Possible chain linkage problem. The error has been repaired.Msg 8945, Level 16, State 1, Line 1Table error: Object ID 245575913, index ID 2 will be rebuilt. The error has been repaired.Msg 2533, Level 16, State 1, Line 1Table error: page (1:5623045) allocated to object ID 245575913, index ID 2, partition ID 579044016455680, alloc unit ID 579044016455680 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header. The error has been repaired.Msg 8976, Level 16, State 1, Line 1Table error: Object ID 245575913, index ID 2, partition ID 579044016455680, alloc unit ID 579044016455680 (type In-row data). Page (1:5623045) was not seen in the scan although its parent (1:6562039) and previous (1:5697474) refer to it. Check any previous errors. The error has been repaired.Msg 8978, Level 16, State 1, Line 1Table error: Object ID 245575913, index ID 2, partition ID 579044016455680, alloc unit ID 579044016455680 (type In-row data). Page (1:5662705) is missing a reference from previous page (1:5623045). Possible chain linkage problem. The error has been repaired.Msg 8945, Level 16, State 1, Line 1Table error: Object ID 245575913, index ID 3 will be rebuilt. The error has been repaired.Msg 8980, Level 16, State 1, Line 1Table error: Object ID 245575913, index ID 3, partition ID 860518993166336, alloc unit ID 860518993166336 (type In-row data). Index node page (0:0), slot 0 refers to child page (1:28355) and previous child (0:0), but they were not encountered. The error has been repaired.There are 22587051 rows in 1324917 pages for object "IAgentQueueStats".CHECKDB found 0 allocation errors and 7 consistency errors in table 'IAgentQueueStats' (object ID 245575913).CHECKDB fixed 0 allocation errors and 7 consistency errors in table 'IAgentQueueStats' (object ID 245575913).DBCC results for 'AgentQueueActivationHist'.There are 1880 rows in 36 pages for object "AgentQueueActivationHist".DBCC results for 'Location'.There are 1 rows in 1 pages for object "Location".DBCC results for 'CallDetail'.Repair: The Clustered index successfully rebuilt for the object "dbo.CallDetail" in database "i3_eic".Repair: The page (1:5489079) has been deallocated from object ID 325576198, index ID 1, partition ID 302811938422784, alloc unit ID 302811938422784 (type In-row data).Repair: The page (1:5610478) has been deallocated from object ID 325576198, index ID 1, partition ID 302811938422784, alloc unit ID 302811938422784 (type In-row data).Repair: The Nonclustered index successfully rebuilt for the object "dbo.CallDetail, LocalUserID_IDX" in database "i3_eic".Repair: The Nonclustered index successfully rebuilt for the object "dbo.CallDetail, I3TimeStampGMT_IDX" in database "i3_eic".Msg 8945, Level 16, State 1, Line 1Table error: Object ID 325576198, index ID 1 will be rebuilt. The error has been repaired.Msg 2533, Level 16, State 1, Line 1Table error: page (1:5489079) allocated to object ID 325576198, index ID 1, partition ID 302811938422784, alloc unit ID 302811938422784 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header. The error has been repaired.Msg 8976, Level 16, State 1, Line 1Table error: Object ID 325576198, index ID 1, partition ID 302811938422784, alloc unit ID 302811938422784 (type In-row data). Page (1:5489079) was not seen in the scan although its parent (1:5490327) and previous (1:5489078) refer to it. Check any previous errors. The error has been repaired.Msg 8978, Level 16, State 1, Line 1Table error: Object ID 325576198, index ID 1, partition ID 302811938422784, alloc unit ID 302811938422784 (type In-row data). Page (1:5489152) is missing a reference from previous page (1:5489079). Possible chain linkage problem. The error has been repaired.Msg 8978, Level 16, State 1, Line 1Table error: Object ID 325576198, index ID 1, partition ID 302811938422784, alloc unit ID 302811938422784 (type In-row data). Page (1:5610408) is missing a reference from previous page (1:5610478). Possible chain linkage problem. The error has been repaired.Msg 2533, Level 16, State 1, Line 1Table error: page (1:5610478) allocated to object ID 325576198, index ID 1, partition ID 302811938422784, alloc unit ID 302811938422784 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header. The error has been repaired.Msg 8976, Level 16, State 1, Line 1Table error: Object ID 325576198, index ID 1, partition ID 302811938422784, alloc unit ID 302811938422784 (type In-row data). Page (1:5610478) was not seen in the scan although its parent (1:5611679) and previous (1:5610413) refer to it. Check any previous errors. The error has been repaired.Msg 8945, Level 16, State 1, Line 1Table error: Object ID 325576198, index ID 2 will be rebuilt. The error has been repaired.Msg 8980, Level 16, State 1, Line 1Table error: Object ID 325576198, index ID 2, partition ID 584286915133440, alloc unit ID 584286915133440 (type In-row data). Index node page (0:0), slot 0 refers to child page (1:3482805) and previous child (0:0), but they were not encountered. The error has been repaired.Msg 8945, Level 16, State 1, Line 1Table error: Object ID 325576198, index ID 3 will be rebuilt. The error has been repaired.Msg 8980, Level 16, State 1, Line 1Table error: Object ID 325576198, index ID 3, partition ID 865761891844096, alloc unit ID 865761891844096 (type In-row data). Index node page (0:0), slot 0 refers to child page (1:6439166) and previous child (0:0), but they were not encountered. The error has been repaired.There are 9969346 rows in 949510 pages for object "CallDetail".CHECKDB found 0 allocation errors and 8 consistency errors in table 'CallDetail' (object ID 325576198).CHECKDB fixed 0 allocation errors and 8 consistency errors in table 'CallDetail' (object ID 325576198).DBCC results for 'LocAttribute'.There are 0 rows in 0 pages for object "LocAttribute".DBCC results for 'LocConnection'.There are 0 rows in 0 pages for object "LocConnection".DBCC results for 'LineConfig'.There are 267 rows in 4 pages for object "LineConfig".DBCC results for 'OrphanedRecordings'.There are 0 rows in 0 pages for object "OrphanedRecordings".DBCC results for 'LineGroupConfig'.There are 6 rows in 1 pages for object "LineGroupConfig".DBCC results for 'OrgAddress'.There are 0 rows in 0 pages for object "OrgAddress".DBCC results for 'ArchiveWork'.There are 0 rows in 0 pages for object "ArchiveWork".DBCC results for 'LineGroupLines'.There are 147 rows in 3 pages for object "LineGroupLines".DBCC results for 'ArchiveWorkTmp'.There are 0 rows in 0 pages for object "ArchiveWorkTmp".DBCC results for 'Organization'.There are 93 rows in 2 pages for object "Organization".DBCC results for 'AgentActivityLog'.There are 1466635 rows in 22793 pages for object "AgentActivityLog".DBCC results for 'Archive_Category'.There are 0 rows in 0 pages for object "Archive_Category".DBCC results for 'IO_DayClassification'.There are 10 rows in 1 pages for object "IO_DayClassification".DBCC results for 'AttributeName'.There are 18 rows in 1 pages for object "AttributeName".DBCC results for 'IO_ShiftRotation'.There are 0 rows in 1 pages for object "IO_ShiftRotation".DBCC results for 'ILineGroupStats'.There are 244858 rows in 2240 pages for object "ILineGroupStats".DBCC results for 'IO_ActivityType'.There are 10 rows in 1 pages for object "IO_ActivityType".DBCC results for 'OrgAttribute'.There are 0 rows in 0 pages for object "OrgAttribute".DBCC results for 'AuditOperation'.There are 17 rows in 1 pages for object "AuditOperation".DBCC results for 'IO_RotationShiftDefinition'.There are 0 rows in 1 pages for object "IO_RotationShiftDefinition".DBCC results for 'IO_Status'.There are 24 rows in 1 pages for object "IO_Status".DBCC results for 'OrgConnection'.There are 6 rows in 1 pages for object "OrgConnection".DBCC results for 'ILineStats'.There are 12698139 rows in 103317 pages for object "ILineStats".DBCC results for 'Category'.There are 1740 rows in 31 pages for object "Category".DBCC results for 'IO_SchedulingUnit'.There are 1 rows in 1 pages for object "IO_SchedulingUnit".DBCC results for 'AccountCodeMirror'.There are 0 rows in 0 pages for object "AccountCodeMirror".DBCC results for 'EmailFileAttachment'.There are 0 rows in 0 pages for object "EmailFileAttachment".DBCC results for 'OrgType'.There are 7 rows in 1 pages for object "OrgType".DBCC results for 'ImportRule'.There are 2 rows in 1 pages for object "ImportRule".DBCC results for 'IO_ShiftDefinition'.There are 42 rows in 1 pages for object "IO_ShiftDefinition".DBCC results for 'dtproperties'.There are 0 rows in 0 pages for object "dtproperties".DBCC results for 'Title'.There are 6 rows in 1 pages for object "Title".DBCC results for 'IRAudit'.There are 68910 rows in 1541 pages for object "IRAudit".DBCC results for 'UserObjectSecurity'.There are 8798 rows in 139 pages for object "UserObjectSecurity".DBCC results for 'RelationshipDescription'.There are 0 rows in 0 pages for object "RelationshipDescription".DBCC results for 'IRDataVersion'.There are 0 rows in 0 pages for object "IRDataVersion".DBCC results for 'LastRecording'.There are 0 rows in 0 pages for object "LastRecording".DBCC results for 'IO_Workgroup'.There are 4 rows in 1 pages for object "IO_Workgroup".DBCC results for 'Relationship'.There are 0 rows in 0 pages for object "Relationship".DBCC results for 'Object'.There are 2136 rows in 21 pages for object "Object".DBCC results for 'IO_Agent'.There are 177 rows in 6 pages for object "IO_Agent".DBCC results for 'Participant'.There are 2 rows in 1 pages for object "Participant".DBCC results for 'sys.queue_messages_919010355'.There are 0 rows in 0 pages for object "sys.queue_messages_919010355".DBCC results for 'Query'.There are 18 rows in 5 pages for object "Query".DBCC results for 'sys.queue_messages_951010469'.There are 0 rows in 0 pages for object "sys.queue_messages_951010469".DBCC results for 'sys.queue_messages_983010583'.There are 0 rows in 0 pages for object "sys.queue_messages_983010583".DBCC results for 'Question'.There are 115 rows in 5 pages for object "Question".DBCC results for 'IO_DailyConstraints'.There are 64 rows in 2 pages for object "IO_DailyConstraints".DBCC results for 'QuestionEnum'.There are 224 rows in 2 pages for object "QuestionEnum".DBCC results for 'Questionnaire'.There are 11 rows in 2 pages for object "Questionnaire".DBCC results for 'IO_TimeOffRequest'.There are 1268 rows in 43 pages for object "IO_TimeOffRequest".DBCC results for 'QuestionnaireForm'.There are 2 rows in 1 pages for object "QuestionnaireForm".DBCC results for 'IO_Activity'.Repair: The Clustered index successfully rebuilt for the object "dbo.IO_Activity" in database "i3_eic".Repair: The page (1:5616599) has been deallocated from object ID 1200723330, index ID 1, partition ID 360165580865536, alloc unit ID 360165580865536 (type In-row data).Repair: The Nonclustered index successfully rebuilt for the object "dbo.IO_Activity, IX_Activity_AgentID" in database "i3_eic".Repair: The Nonclustered index successfully rebuilt for the object "dbo.IO_Activity, IX_Activity_DailyConstraintsID" in database "i3_eic".Repair: The Nonclustered index successfully rebuilt for the object "dbo.IO_Activity, IX_Activity_TimeOffRequestID" in database "i3_eic".Msg 8945, Level 16, State 1, Line 1Table error: Object ID 1200723330, index ID 1 will be rebuilt. The error has been repaired.Msg 8978, Level 16, State 1, Line 1Table error: Object ID 1200723330, index ID 1, partition ID 360165580865536, alloc unit ID 360165580865536 (type In-row data). Page (1:4408707) is missing a reference from previous page (1:5616599). Possible chain linkage problem. The error has been repaired.Msg 2533, Level 16, State 1, Line 1Table error: page (1:5616599) allocated to object ID 1200723330, index ID 1, partition ID 360165580865536, alloc unit ID 360165580865536 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header. The error has been repaired.Msg 8976, Level 16, State 1, Line 1Table error: Object ID 1200723330, index ID 1, partition ID 360165580865536, alloc unit ID 360165580865536 (type In-row data). Page (1:5616599) was not seen in the scan although its parent (1:5425146) and previous (1:4149037) refer to it. Check any previous errors. The error has been repaired.Msg 8945, Level 16, State 1, Line 1Table error: Object ID 1200723330, index ID 2 will be rebuilt. The error has been repaired.Msg 8980, Level 16, State 1, Line 1Table error: Object ID 1200723330, index ID 2, partition ID 641640557576192, alloc unit ID 641640557576192 (type In-row data). Index node page (0:0), slot 0 refers to child page (1:4109601) and previous child (0:0), but they were not encountered. The error has been repaired.Msg 8945, Level 16, State 1, Line 1Table error: Object ID 1200723330, index ID 3 will be rebuilt. The error has been repaired.Msg 8945, Level 16, State 1, Line 1Table error: Object ID 1200723330, index ID 4 will be rebuilt. The error has been repaired.There are 207436 rows in 7444 pages for object "IO_Activity".CHECKDB found 0 allocation errors and 4 consistency errors in table 'IO_Activity' (object ID 1200723330).CHECKDB fixed 0 allocation errors and 4 consistency errors in table 'IO_Activity' (object ID 1200723330).DBCC results for 'QuestionnaireGroup'.There are 22 rows in 2 pages for object "QuestionnaireGroup".DBCC results for 'FaxEnvelopeHist'.There are 180286 rows in 7313 pages for object "FaxEnvelopeHist".DBCC results for 'Questionnaire_Answer'.There are 56 rows in 2 pages for object "Questionnaire_Answer".DBCC results for 'IO_NamedSchedule'.There are 91 rows in 3 pages for object "IO_NamedSchedule".DBCC results for 'RankDefn'.There are 3 rows in 2 pages for object "RankDefn".DBCC results for 'IO_Schedule'.There are 33430 rows in 919 pages for object "IO_Schedule".DBCC results for 'RankGroup'.There are 3 rows in 1 pages for object "RankGroup".DBCC results for 'IO_ScheduleInterval'.There are 577467 rows in 13429 pages for object "IO_ScheduleInterval".DBCC results for 'RecIntxParticipant'.There are 9592695 rows in 100647 pages for object "RecIntxParticipant".DBCC results for 'IO_UtilizationSettings'.There are 24 rows in 1 pages for object "IO_UtilizationSettings".DBCC results for 'RecordingArchive'.There are 364 rows in 10 pages for object "RecordingArchive".DBCC results for 'ININ_APP_VERSION'.There are 141 rows in 2 pages for object "ININ_APP_VERSION".DBCC results for 'IO_ServiceLevelSettings'.There are 4 rows in 1 pages for object "IO_ServiceLevelSettings".DBCC results for 'RecordingCall'.There are 4751754 rows in 193895 pages for object "RecordingCall".DBCC results for 'RecordingChat'.There are 26 rows in 1 pages for object "RecordingChat".DBCC results for 'RecordingData'.Repair: The Clustered index successfully rebuilt for the object "dbo.RecordingData" in database "i3_eic".Repair: The page (1:5610486) has been deallocated from object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data).Repair: The Nonclustered index successfully rebuilt for the object "dbo.RecordingData, IX_RecordingData_CatID" in database "i3_eic".Repair: The Nonclustered index successfully rebuilt for the object "dbo.RecordingData, IX_RecordingData_ArcID" in database "i3_eic".Repair: The Nonclustered index successfully rebuilt for the object "dbo.RecordingData, IX_RecData_IPPMRD" in database "i3_eic".Msg 8945, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1 will be rebuilt. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 102442769711104 (type In-row data). Parent node for page (1:159227) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 102442769711104 (type In-row data). Parent node for page (1:164382) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 102442769711104 (type In-row data). Parent node for page (1:456922) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 102442769711104 (type In-row data). Parent node for page (1:728376) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 102442769711104 (type In-row data). Parent node for page (1:742612) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 102442769711104 (type In-row data). Parent node for page (1:828614) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 102442769711104 (type In-row data). Parent node for page (1:883079) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 102442769711104 (type In-row data). Parent node for page (1:1037443) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 102442769711104 (type In-row data). Parent node for page (1:1143495) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 102442769711104 (type In-row data). Parent node for page (1:1146714) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 102442769711104 (type In-row data). Parent node for page (1:1218264) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 102442769711104 (type In-row data). Parent node for page (1:1225055) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 102442769711104 (type In-row data). Parent node for page (1:1258003) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 102442769711104 (type In-row data). Parent node for page (1:1331249) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 102442769711104 (type In-row data). Parent node for page (1:1386269) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 102442769711104 (type In-row data). Parent node for page (1:1419420) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 102442769711104 (type In-row data). Parent node for page (1:1420871) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 102442769711104 (type In-row data). Parent node for page (1:1422086) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 102442769711104 (type In-row data). Parent node for page (1:1423994) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 102442769711104 (type In-row data). Parent node for page (1:1445268) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 102442769711104 (type In-row data). Parent node for page (1:1450199) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 102442769711104 (type In-row data). Parent node for page (1:1495629) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 102442769711104 (type In-row data). Parent node for page (1:1499364) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 102442769711104 (type In-row data). Parent node for page (1:1665710) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 102442769711104 (type In-row data). Parent node for page (1:1706842) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 102442769711104 (type In-row data). Parent node for page (1:1793601) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 102442769711104 (type In-row data). Parent node for page (1:1801551) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 102442769711104 (type In-row data). Parent node for page (1:1806131) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 102442769711104 (type In-row data). Parent node for page (1:1807520) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 102442769711104 (type In-row data). Parent node for page (1:1816278) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 102442769711104 (type In-row data). Parent node for page (1:1822701) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 102442769711104 (type In-row data). Parent node for page (1:1853586) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 102442769711104 (type In-row data). Parent node for page (1:1857019) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 102442769711104 (type In-row data). Parent node for page (1:1863961) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 102442769711104 (type In-row data). Parent node for page (1:1890000) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:165211) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:283620) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:462759) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:1364386) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:1572136) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:1582560) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:1608596) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:1978218) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:1986616) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:2001963) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:2005247) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:2013703) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:2021499) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:2027000) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:2032180) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:2039419) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:2046111) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:2052496) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:2090172) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:2112529) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:2201224) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:2219323) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:2231167) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:2256309) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:2267086) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:2269854) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:2280122) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:2300411) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:2321014) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:2326533) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:2378540) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:2391129) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:2433613) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:2456692) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:2466277) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:2481906) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:2574212) was not encountered. The error has been repaired.Msg 8978, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Page (1:2613748) is missing a reference from previous page (1:5610486). Possible chain linkage problem. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:2675407) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:2700734) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:2857052) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:2909705) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:3094583) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:3115661) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:3125275) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:3143489) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:3180560) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:3184056) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:3231943) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:3250905) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:3281868) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:3342370) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:3360505) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:3423924) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:3424460) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:3455178) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:3501839) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:3518067) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:3526918) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:3664014) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:3675310) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:3713873) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:3752950) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:3759423) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:3773399) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:3812131) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:3857273) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:3900168) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:3903272) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:3917663) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:3939337) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:3968914) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:4033412) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:4042691) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:4097697) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:4140582) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:4217095) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:4281854) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:4290672) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:4294885) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:4326208) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:4347208) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:4382781) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:4440920) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:4475177) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:4511346) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:4617820) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:4624495) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:4812631) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:4829366) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:4903517) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:4925629) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:4930008) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:5101268) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:5101417) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:5230082) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:5238761) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:5265251) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:5305603) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:5363068) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:5427295) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:5461077) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:5482191) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:5495374) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:5514605) was not encountered. The error has been repaired.Msg 2533, Level 16, State 1, Line 1Table error: page (1:5610486) allocated to object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header. The error has been repaired.Msg 8976, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Page (1:5610486) was not seen in the scan although its parent (1:2861743) and previous (1:1808617) refer to it. Check any previous errors. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:5610487) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:5622528) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:5668295) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:5699074) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:5778129) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:5807914) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:5823431) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:5842015) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:5897039) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:5913779) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:5925340) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:6084307) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:6111730) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:6117707) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:6122167) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:6158765) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:6250562) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:6267592) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:6276599) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:6398152) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:6475045) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:6479338) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:6479568) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:6480012) was not encountered. The error has been repaired.Msg 8977, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 1, partition ID 383917746421760, alloc unit ID 383917746421760 (type In-row data). Parent node for page (1:6496407) was not encountered. The error has been repaired.Msg 8945, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 2 will be rebuilt. The error has been repaired.Msg 8945, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 3 will be rebuilt. The error has been repaired.Msg 8945, Level 16, State 1, Line 1Table error: Object ID 1563152614, index ID 4 will be rebuilt. The error has been repaired.There are 4752583 rows in 312781 pages for object "RecordingData".CHECKDB found 0 allocation errors and 167 consistency errors in table 'RecordingData' (object ID 1563152614).CHECKDB fixed 0 allocation errors and 167 consistency errors in table 'RecordingData' (object ID 1563152614).DBCC results for 'IO_ForecastScheduleEntry'.There are 90 rows in 2 pages for object "IO_ForecastScheduleEntry".DBCC results for 'RecordingEmail'.There are 0 rows in 0 pages for object "RecordingEmail".DBCC results for 'IO_DayClassOverride'.There are 1 rows in 1 pages for object "IO_DayClassOverride".DBCC results for 'RecordingError'.There are 72 rows in 1 pages for object "RecordingError".DBCC results for 'IO_RTAException'.There are 346436 rows in 20952 pages for object "IO_RTAException".DBCC results for 'RecordingFax'.There are 802 rows in 37 pages for object "RecordingFax".DBCC results for 'IO_VolumeForecast'.There are 90 rows in 2 pages for object "IO_VolumeForecast".DBCC results for 'RecordedRule'.Repair: The page (1:5611752) has been deallocated from object ID 1691153070, index ID 0, partition ID 110831407595520, alloc unit ID 110831407595520 (type In-row data).Repair: The Nonclustered index successfully rebuilt for the object "dbo.RecordedRule, IX_RecordedRule_RecID" in database "i3_eic".Repair: The Nonclustered index successfully rebuilt for the object "dbo.RecordedRule, IX_RecordedRule_QnnaireID" in database "i3_eic".Repair: The Nonclustered index successfully rebuilt for the object "dbo.RecordedRule, IX_RecordedRule_IntxID" in database "i3_eic".Repair: The Nonclustered index successfully rebuilt for the object "dbo.RecordedRule, IX_RecordedRule_IntxPartID" in database "i3_eic".Msg 2533, Level 16, State 1, Line 1Table error: page (1:5611752) allocated to object ID 1691153070, index ID 0, partition ID 110831407595520, alloc unit ID 110831407595520 (type In-row data) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header. The error has been repaired.Msg 8945, Level 16, State 1, Line 1Table error: Object ID 1691153070, index ID 2 will be rebuilt. The error has been repaired.Msg 8980, Level 16, State 1, Line 1Table error: Object ID 1691153070, index ID 2, partition ID 673781361016832, alloc unit ID 673781361016832 (type In-row data). Index node page (0:0), slot 0 refers to child page (1:4769260) and previous child (0:0), but they were not encountered. The error has been repaired.Msg 8945, Level 16, State 1, Line 1Table error: Object ID 1691153070, index ID 3 will be rebuilt. The error has been repaired.Msg 8945, Level 16, State 1, Line 1Table error: Object ID 1691153070, index ID 4 will be rebuilt. The error has been repaired.Msg 8945, Level 16, State 1, Line 1Table error: Object ID 1691153070, index ID 5 will be rebuilt. The error has been repaired.There are 6630819 rows in 86132 pages for object "RecordedRule".CHECKDB found 0 allocation errors and 2 consistency errors in table 'RecordedRule' (object ID 1691153070).CHECKDB fixed 0 allocation errors and 2 consistency errors in table 'RecordedRule' (object ID 1691153070).DBCC results for 'RecordingWork'.There are 0 rows in 0 pages for object "RecordingWork".DBCC results for 'IO_DaySelection'.There are 2500 rows in 52 pages for object "IO_DaySelection".DBCC results for 'RecordingUserPref'.There are 0 rows in 0 pages for object "RecordingUserPref".DBCC results for 'IO_VolumeForecastStats'.There are 181800 rows in 5560 pages for object "IO_VolumeForecastStats".DBCC results for 'Recording_Attribute'.There are 17 rows in 4 pages for object "Recording_Attribute".DBCC results for 'ScreenRecordingData'.There are 0 rows in 0 pages for object "ScreenRecordingData".DBCC results for 'IO_HeadcountForecast'.There are 91 rows in 2 pages for object "IO_HeadcountForecast".DBCC results for 'ScreenRecParticipant'.There are 0 rows in 0 pages for object "ScreenRecParticipant".DBCC results for 'IO_HeadcountForecastStats'.There are 140959 rows in 6837 pages for object "IO_HeadcountForecastStats".DBCC results for 'AddrType'.There are 4 rows in 1 pages for object "AddrType".DBCC results for 'sysdiagrams'.There are 0 rows in 0 pages for object "sysdiagrams".DBCC results for 'ScreenRecParticipantHold'.There are 0 rows in 0 pages for object "ScreenRecParticipantHold".DBCC results for 'AttributeType'.There are 2 rows in 1 pages for object "AttributeType".DBCC results for 'TemplateParam'.There are 68 rows in 5 pages for object "TemplateParam".DBCC results for 'ConnectionType'.There are 7 rows in 1 pages for object "ConnectionType".DBCC results for 'ConnSubType'.There are 6 rows in 1 pages for object "ConnSubType".DBCC results for 'IndivAddress'.There are 0 rows in 0 pages for object "IndivAddress".DBCC results for 'UserQueryTemplateInfo'.There are 1 rows in 1 pages for object "UserQueryTemplateInfo".DBCC results for 'Contacts'.There are 373 rows in 15 pages for object "Contacts".DBCC results for 'IRChangeVersion'.There are 1622 rows in 32 pages for object "IRChangeVersion".DBCC results for 'IndivAttribute'.There are 8306 rows in 178 pages for object "IndivAttribute".DBCC results for 'SpeedDialList'.There are 21 rows in 1 pages for object "SpeedDialList".DBCC results for 'RecordingWorkControl'.There are 0 rows in 0 pages for object "RecordingWorkControl".DBCC results for 'IndivConnection'.There are 52534 rows in 905 pages for object "IndivConnection".DBCC results for 'SpeedDial'.There are 76 rows in 3 pages for object "SpeedDial".DBCC results for 'UnprocRecordingData'.There are 3250313 rows in 235792 pages for object "UnprocRecordingData".DBCC results for 'Individual'.There are 34417 rows in 1494 pages for object "Individual".DBCC results for 'UserWorkgroups'.There are 782 rows in 7 pages for object "UserWorkgroups".DBCC results for 'ICDirChangeLog'.There are 1909096 rows in 39933 pages for object "ICDirChangeLog".CHECKDB found 0 allocation errors and 205 consistency errors in database 'i3_eic'.CHECKDB fixed 0 allocation errors and 196 consistency errors in database 'i3_eic'. is the minimum repair level for the errors found by DBCC CHECKDB (i3_eic, repair_allow_data_loss).DBCC execution completed. If DBCC printed error messages, contact your system administrator. |
|
|
GilaMonster
Master Smack Fu Yak Hacker
4507 Posts |
Posted - 2010-12-22 : 09:38:28
|
Run this, post the results.DBCC CHECKDB (<Database Name>) WITH NO_INFOMSGS, ALL_ERRORMSGS --Gail ShawSQL Server MVP |
|
|
carparks
Starting Member
11 Posts |
Posted - 2010-12-22 : 09:49:25
|
I'm trying a backup on that database right now, so as soon as it's done I will run that. I did do a DBCC CHECKDB after running the repair_allow_data_loss and it came back with no errors. I still don't know if that's good or bad, but I will run what you suggested and post it as soon as my backup job completes...or fails. Thanks. |
|
|
carparks
Starting Member
11 Posts |
Posted - 2010-12-22 : 11:50:04
|
I ran this: DBCC CHECKDB (i3_eic) WITH NO_INFOMSGS, ALL_ERRORMSGSAnd got this: Command(s) completed successfully.The backups are failing with this:Failed:(-1073548784) Executing the query "BACKUP DATABASE [i3_eic] TO DISK = N'S:\\Program Files\\Microsoft SQL Server\\MSSQL.1\\MSSQL\\Backup\\i3_eic\\i3_eic_backup_201012220646.bak' WITH NOFORMAT, NOINIT, NAME = N'i3_eic_backup_20101222064639', SKIP, REWIND, NOUNLOAD, STATS = 10" failed with the following error: "A nonrecoverable I/O error occurred on file "S:\\Program Files\\Microsoft SQL Server\\MSSQL.1\\MSSQL\\Data\\i3_eic.mdf:" 23(Data error (cyclic redundancy check).).BACKUP DATABASE is terminating abnormally.10 percent processed.20 percent processed.30 percent processed.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly. |
|
|
Swaynebell
Starting Member
8 Posts |
Posted - 2010-12-22 : 12:29:03
|
Curious.The 9 CRC (cyclic redundancy check) errors that were at the top of your original output appeared as failing again in the output you posted from the repair. When you ran CHECK DB again though it didn't show them, but your backup is failing and reporting CRC errors.As you can see, you're in Gail's extremely capable hands, so I'm confident she will straighten this out in short order. |
|
|
GilaMonster
Master Smack Fu Yak Hacker
4507 Posts |
Posted - 2010-12-22 : 14:32:14
|
That does not look good. Are you seeing any hardware errors? (check windows event log, RAID/SAN logs, etc)--Gail ShawSQL Server MVP |
|
|
carparks
Starting Member
11 Posts |
Posted - 2010-12-22 : 15:37:17
|
quote: Originally posted by GilaMonster That does not look good. Are you seeing any hardware errors? (check windows event log, RAID/SAN logs, etc)--Gail ShawSQL Server MVP
Yep.Event ID: 24606: "Logical drive 1 configured on array controller P400i [Embedded] returned a fatal error during a read/write request from/to the volume. Logical block address 439666272, block count 16 and command 32 were taken from the failed logical I/O request. Array controller P400i [Embedded] is also reporting that the last physical drive to report a fatal error condition (associated with this logical request), is located on bus 0 and ID 2." I just replaced a hard drive that was on bus 0 ID 3, and now I am seeing this for ID 2. I guess I'll try and replace this disk. I have upgraded to the latest firmware on the Array controller previously. |
|
|
GilaMonster
Master Smack Fu Yak Hacker
4507 Posts |
Posted - 2010-12-22 : 17:06:36
|
Fix the hardware errors first, otherwise the DB is just going to keep on corrupting.--Gail ShawSQL Server MVP |
|
|
Next Page
|
|
|
|
|