Backup corrupted after de-fragmentation

Hi
We have a database of about 40GB and a full backup of that database. The
backup resides on "E" drive and recently we de-fragmented that drive. After
de-fragmentation we restored the database and we ran dbcc checkdb command
and it shows some errors. Before de-fragmentation we restored this backup
several times and we didn't encountered any problems. Does de-fragmentation
creates any problem? What is the best way to de-fragment a drive which
contains database backup?
Thanks
Ram
What errors does checkdb return?
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Ram" <Ramakrishna.pothuganti@.vizual.co.in> wrote in message
news:ugLPBhSUFHA.2172@.tk2msftngp13.phx.gbl...
> Hi
> We have a database of about 40GB and a full backup of that database. The
> backup resides on "E" drive and recently we de-fragmented that drive.
After
> de-fragmentation we restored the database and we ran dbcc checkdb command
> and it shows some errors. Before de-fragmentation we restored this backup
> several times and we didn't encountered any problems. Does
de-fragmentation
> creates any problem? What is the best way to de-fragment a drive which
> contains database backup?
> Thanks
> Ram
>
|||Here are the error messages genereated by dbcc checkdb command
DBCC results for 'GRIEVANCEFOLLOWUP'.
Server: Msg 8944, Level 16, State 17, Line 1
Table error: Object ID 629577281, index ID 0, page (1:3716011), row 0. Test
(columnOffsets->offTbl [varColumnNumber] <= (nextRec - pRec)) failed. Values
are 160 and 130.
Server: Msg 8944, Level 16, State 1, Line 1
Table error: Object ID 629577281, index ID 0, page (1:3727315), row 0. Test
(columnOffsets->offTbl [varColumnNumber] <= (nextRec - pRec)) failed. Values
are 160 and 130.
Server: Msg 8944, Level 16, State 1, Line 1
Table error: Object ID 629577281, index ID 0, page (1:3729592), row 0. Test
(columnOffsets->offTbl [varColumnNumber] <= (nextRec - pRec)) failed. Values
are 160 and 130.
There are 399834 rows in 19992 pages for object 'GRIEVANCEFOLLOWUP'.
CHECKDB found 0 allocation errors and 3 consistency errors in table
'GRIEVANCEFOLLOWUP' (object ID 629577281).
There are 122 rows in 2 pages for object 'OC_GRIDCOLUMNS'.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1634104862, index ID 0: Page (1:3716003) could not be processed.
See other errors for details.
Server: Msg 8944, Level 16, State 1, Line 1
Table error: Object ID 1634104862, index ID 0, page (1:3716003), row 47.
Test (ColumnOffsets <= (nextRec - pRec)) failed. Values are 28416 and 145.
Server: Msg 2533, Level 16, State 1, Line 1
Table error: Page (1:3716004) allocated to object ID 1634104862, index ID 0
was not seen. Page may be invalid or have incorrect object ID information
in its header.
Server: Msg 2533, Level 16, State 1, Line 1
Table error: Page (1:3716005) allocated to object ID 1634104862, index ID 0
was not seen. Page may be invalid or have incorrect object ID information
in its header.
Server: Msg 2533, Level 16, State 1, Line 1
Table error: Page (1:3716006) allocated to object ID 1634104862, index ID 0
was not seen. Page may be invalid or have incorrect object ID information
in its header.
Server: Msg 2533, Level 16, State 1, Line 1
Table error: Page (1:3716007) allocated to object ID 1634104862, index ID 0
was not seen. Page may be invalid or have incorrect object ID information
in its header.
Server: Msg 2533, Level 16, State 1, Line 1
Table error: Page (1:3716008) allocated to object ID 1634104862, index ID 0
was not seen. Page may be invalid or have incorrect object ID information
in its header.
Server: Msg 2533, Level 16, State 1, Line 1
Table error: Page (1:3716009) allocated to object ID 1634104862, index ID 0
was not seen. Page may be invalid or have incorrect object ID information
in its header.
Server: Msg 2533, Level 16, State 1, Line 1
Table error: Page (1:3716010) allocated to object ID 1634104862, index ID 0
was not seen. Page may be invalid or have incorrect object ID information
in its header.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1634104862, index ID 0: Page (1:3716011) could not be processed.
See other errors for details.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1634104862, index ID 0: Page (1:3727307) could not be processed.
See other errors for details.
DBCC results for 'TIMESHEETS'.
Server: Msg 8944, Level 16, State 2, Line 1
Table error: Object ID 1634104862, index ID 0, page (1:3727307), row 1. Test
(!(hdr->r_tagA & (VERSION_MASK | RECTAG_RESV_A | RECTAG_RESV_B))) failed.
Values are 45 and 193.
Server: Msg 8944, Level 16, State 1, Line 1
Table error: Object ID 1634104862, index ID 0, page (1:3727307), row 1. Test
(ColumnOffsets <= (nextRec - pRec)) failed. Values are 23319 and 394.
Server: Msg 2533, Level 16, State 1, Line 1
Table error: Page (1:3727308) allocated to object ID 1634104862, index ID 0
was not seen. Page may be invalid or have incorrect object ID information
in its header.
Server: Msg 2533, Level 16, State 1, Line 1
Table error: Page (1:3727309) allocated to object ID 1634104862, index ID 0
was not seen. Page may be invalid or have incorrect object ID information
in its header.
Server: Msg 2533, Level 16, State 1, Line 1
Table error: Page (1:3727310) allocated to object ID 1634104862, index ID 0
was not seen. Page may be invalid or have incorrect object ID information
in its header.
Server: Msg 2533, Level 16, State 1, Line 1
Table error: Page (1:3727311) allocated to object ID 1634104862, index ID 0
was not seen. Page may be invalid or have incorrect object ID information
in its header.
Server: Msg 2533, Level 16, State 1, Line 1
Table error: Page (1:3727312) allocated to object ID 1634104862, index ID 0
was not seen. Page may be invalid or have incorrect object ID information
in its header.
Server: Msg 2533, Level 16, State 1, Line 1
Table error: Page (1:3727313) allocated to object ID 1634104862, index ID 0
was not seen. Page may be invalid or have incorrect object ID information
in its header.
Server: Msg 2533, Level 16, State 1, Line 1
Table error: Page (1:3727314) allocated to object ID 1634104862, index ID 0
was not seen. Page may be invalid or have incorrect object ID information
in its header.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1634104862, index ID 0: Page (1:3727315) could not be processed.
See other errors for details.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1634104862, index ID 0: Page (1:3729587) could not be processed.
See other errors for details.
Server: Msg 8941, Level 16, State 1, Line 1
Table error: Object ID 1634104862, index ID 0, page (1:3729587). Test
(sorted [i].offset >= PAGEHEADSIZE) failed. Slot 57, offset 0x2e is invalid.
Server: Msg 8942, Level 16, State 101, Line 1
Table error: Object ID 1634104862, index ID 0, page (1:3729587). Test
(sorted[i].offset >= max) failed. Slot 0, offset 0x39 overlaps with the
prior row.
Server: Msg 2533, Level 16, State 1, Line 1
Table error: Page (1:3729588) allocated to object ID 1634104862, index ID 0
was not seen. Page may be invalid or have incorrect object ID information
in its header.
Server: Msg 2533, Level 16, State 1, Line 1
Table error: Page (1:3729589) allocated to object ID 1634104862, index ID 0
was not seen. Page may be invalid or have incorrect object ID information
in its header.
Server: Msg 2533, Level 16, State 1, Line 1
Table error: Page (1:3729590) allocated to object ID 1634104862, index ID 0
was not seen. Page may be invalid or have incorrect object ID information
in its header.
Server: Msg 2533, Level 16, State 1, Line 1
Table error: Page (1:3729591) allocated to object ID 1634104862, index ID 0
was not seen. Page may be invalid or have incorrect object ID information
in its header.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1634104862, index ID 0: Page (1:3729592) could not be processed.
See other errors for details.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 1634104862, index ID 1. Page (1:3716003) was not seen
in the scan although its parent (1:3715435) and previous (1:3716002) refer
to it. Check any previous errors.
Server: Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 1634104862, index ID 1. Index node page (1:3715435),
slot 154 refers to child page (1:3716004) and previous child (1:3716003),
but they were not encountered.
Server: Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 1634104862, index ID 1. Index node page (1:3715435),
slot 155 refers to child page (1:3716005) and previous child (1:3716004),
but they were not encountered.
Server: Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 1634104862, index ID 1. Index node page (1:3715435),
slot 156 refers to child page (1:3716006) and previous child (1:3716005),
but they were not encountered.
Server: Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 1634104862, index ID 1. Index node page (1:3715435),
slot 157 refers to child page (1:3716007) and previous child (1:3716006),
but they were not encountered.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 1634104862, index ID 1. Page (1:3716008) was not seen
in the scan although its parent (1:3714274) and previous (1:3715943) refer
to it. Check any previous errors.
Server: Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 1634104862, index ID 1. Index node page (1:3714274),
slot 167 refers to child page (1:3716009) and previous child (1:3716008),
but they were not encountered.
Server: Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 1634104862, index ID 1. Index node page (1:3714274),
slot 168 refers to child page (1:3716010) and previous child (1:3716009),
but they were not encountered.
Server: Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 1634104862, index ID 1. Index node page (1:3714274),
slot 169 refers to child page (1:3716011) and previous child (1:3716010),
but they were not encountered.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1634104862, index ID 1. Page (1:3716012) is missing a
reference from previous page (1:3716011). Possible chain linkage problem.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1634104862, index ID 1. Page (1:3716104) is missing a
reference from previous page (1:3716007). Possible chain linkage problem.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 1634104862, index ID 1. Page (1:3727307) was not seen
in the scan although its parent (1:3726987) and previous (1:3727306) refer
to it. Check any previous errors.
Server: Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 1634104862, index ID 1. Index node page (1:3726987),
slot 131 refers to child page (1:3727308) and previous child (1:3727307),
but they were not encountered.
Server: Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 1634104862, index ID 1. Index node page (1:3726987),
slot 132 refers to child page (1:3727309) and previous child (1:3727308),
but they were not encountered.
Server: Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 1634104862, index ID 1. Index node page (1:3726987),
slot 133 refers to child page (1:3727310) and previous child (1:3727309),
but they were not encountered.
Server: Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 1634104862, index ID 1. Index node page (1:3726987),
slot 134 refers to child page (1:3727311) and previous child (1:3727310),
but they were not encountered.
Server: Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 1634104862, index ID 1. Index node page (1:3726987),
slot 135 refers to child page (1:3727312) and previous child (1:3727311),
but they were not encountered.
Server: Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 1634104862, index ID 1. Index node page (1:3726987),
slot 136 refers to child page (1:3727313) and previous child (1:3727312),
but they were not encountered.
Server: Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 1634104862, index ID 1. Index node page (1:3726987),
slot 137 refers to child page (1:3727314) and previous child (1:3727313),
but they were not encountered.
Server: Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 1634104862, index ID 1. Index node page (1:3726987),
slot 138 refers to child page (1:3727315) and previous child (1:3727314),
but they were not encountered.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1634104862, index ID 1. Page (1:3727316) is missing a
reference from previous page (1:3727315). Possible chain linkage problem.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 1634104862, index ID 1. Page (1:3729587) was not seen
in the scan although its parent (1:3729110) and previous (1:3729586) refer
to it. Check any previous errors.
Server: Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 1634104862, index ID 1. Index node page (1:3729110),
slot 126 refers to child page (1:3729588) and previous child (1:3729587),
but they were not encountered.
Server: Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 1634104862, index ID 1. Index node page (1:3729110),
slot 127 refers to child page (1:3729589) and previous child (1:3729588),
but they were not encountered.
Server: Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 1634104862, index ID 1. Index node page (1:3729110),
slot 128 refers to child page (1:3729590) and previous child (1:3729589),
but they were not encountered.
Server: Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 1634104862, index ID 1. Index node page (1:3729110),
slot 129 refers to child page (1:3729591) and previous child (1:3729590),
but they were not encountered.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 1634104862, index ID 1. Page (1:3729592) was not seen
in the scan although its parent (1:564380) and previous (1:3729431) refer to
it. Check any previous errors.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1634104862, index ID 1. Page (1:3729593) is missing a
reference from previous page (1:3729592). Possible chain linkage problem.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1634104862, index ID 1. Page (1:3729688) is missing a
reference from previous page (1:3729591). Possible chain linkage problem.
There are 2078683 rows in 34246 pages for object 'TIMESHEETS'.
CHECKDB found 0 allocation errors and 58 consistency errors in table
'TIMESHEETS' (object ID 1634104862).
"Paul S Randal [MS]" <prandal@.online.microsoft.com> wrote in message
news:%23MmIm4TUFHA.1148@.tk2msftngp13.phx.gbl...
> What errors does checkdb return?
> --
> Paul Randal
> Dev Lead, Microsoft SQL Server Storage Engine
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> "Ram" <Ramakrishna.pothuganti@.vizual.co.in> wrote in message
> news:ugLPBhSUFHA.2172@.tk2msftngp13.phx.gbl...
> After
> de-fragmentation
>
|||Well it certainly looks like the backup contains a corrupt database but if
something went badly wrong during a disk defrag I'd expect to see more
obvious errors (e.g. the restore fails, recovery fails, or large chunks of
pages missing) rather than specific things like the 8944s in
GRIEVANCEFOLLOWUP.
Did the restore itself give any errors, during recovery maybe? Given that
there are several whole extents missing, it looks like an optimized index
build was partially rolled back or forward by recovery.
I think your best bet is going to be contacting PSS rather than trying to do
this over a newsgroup.
Regards.
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Ram" <Ramakrishna.pothuganti@.vizual.co.in> wrote in message
news:e26lVIVUFHA.1384@.TK2MSFTNGP09.phx.gbl...
> Here are the error messages genereated by dbcc checkdb command
> DBCC results for 'GRIEVANCEFOLLOWUP'.
> Server: Msg 8944, Level 16, State 17, Line 1
> Table error: Object ID 629577281, index ID 0, page (1:3716011), row 0.
Test
> (columnOffsets->offTbl [varColumnNumber] <= (nextRec - pRec)) failed.
Values
> are 160 and 130.
> Server: Msg 8944, Level 16, State 1, Line 1
> Table error: Object ID 629577281, index ID 0, page (1:3727315), row 0.
Test
> (columnOffsets->offTbl [varColumnNumber] <= (nextRec - pRec)) failed.
Values
> are 160 and 130.
> Server: Msg 8944, Level 16, State 1, Line 1
> Table error: Object ID 629577281, index ID 0, page (1:3729592), row 0.
Test
> (columnOffsets->offTbl [varColumnNumber] <= (nextRec - pRec)) failed.
Values
> are 160 and 130.
> There are 399834 rows in 19992 pages for object 'GRIEVANCEFOLLOWUP'.
> CHECKDB found 0 allocation errors and 3 consistency errors in table
> 'GRIEVANCEFOLLOWUP' (object ID 629577281).
>
> There are 122 rows in 2 pages for object 'OC_GRIDCOLUMNS'.
> Server: Msg 8928, Level 16, State 1, Line 1
> Object ID 1634104862, index ID 0: Page (1:3716003) could not be processed.
> See other errors for details.
> Server: Msg 8944, Level 16, State 1, Line 1
> Table error: Object ID 1634104862, index ID 0, page (1:3716003), row 47.
> Test (ColumnOffsets <= (nextRec - pRec)) failed. Values are 28416 and 145.
> Server: Msg 2533, Level 16, State 1, Line 1
> Table error: Page (1:3716004) allocated to object ID 1634104862, index ID
0
> was not seen. Page may be invalid or have incorrect object ID information
> in its header.
> Server: Msg 2533, Level 16, State 1, Line 1
> Table error: Page (1:3716005) allocated to object ID 1634104862, index ID
0
> was not seen. Page may be invalid or have incorrect object ID information
> in its header.
> Server: Msg 2533, Level 16, State 1, Line 1
> Table error: Page (1:3716006) allocated to object ID 1634104862, index ID
0
> was not seen. Page may be invalid or have incorrect object ID information
> in its header.
> Server: Msg 2533, Level 16, State 1, Line 1
> Table error: Page (1:3716007) allocated to object ID 1634104862, index ID
0
> was not seen. Page may be invalid or have incorrect object ID information
> in its header.
> Server: Msg 2533, Level 16, State 1, Line 1
> Table error: Page (1:3716008) allocated to object ID 1634104862, index ID
0
> was not seen. Page may be invalid or have incorrect object ID information
> in its header.
> Server: Msg 2533, Level 16, State 1, Line 1
> Table error: Page (1:3716009) allocated to object ID 1634104862, index ID
0
> was not seen. Page may be invalid or have incorrect object ID information
> in its header.
> Server: Msg 2533, Level 16, State 1, Line 1
> Table error: Page (1:3716010) allocated to object ID 1634104862, index ID
0
> was not seen. Page may be invalid or have incorrect object ID information
> in its header.
> Server: Msg 8928, Level 16, State 1, Line 1
> Object ID 1634104862, index ID 0: Page (1:3716011) could not be processed.
> See other errors for details.
> Server: Msg 8928, Level 16, State 1, Line 1
> Object ID 1634104862, index ID 0: Page (1:3727307) could not be processed.
> See other errors for details.
>
>
> DBCC results for 'TIMESHEETS'.
> Server: Msg 8944, Level 16, State 2, Line 1
> Table error: Object ID 1634104862, index ID 0, page (1:3727307), row 1.
Test
> (!(hdr->r_tagA & (VERSION_MASK | RECTAG_RESV_A | RECTAG_RESV_B))) failed.
> Values are 45 and 193.
> Server: Msg 8944, Level 16, State 1, Line 1
> Table error: Object ID 1634104862, index ID 0, page (1:3727307), row 1.
Test
> (ColumnOffsets <= (nextRec - pRec)) failed. Values are 23319 and 394.
> Server: Msg 2533, Level 16, State 1, Line 1
> Table error: Page (1:3727308) allocated to object ID 1634104862, index ID
0
> was not seen. Page may be invalid or have incorrect object ID information
> in its header.
> Server: Msg 2533, Level 16, State 1, Line 1
> Table error: Page (1:3727309) allocated to object ID 1634104862, index ID
0
> was not seen. Page may be invalid or have incorrect object ID information
> in its header.
> Server: Msg 2533, Level 16, State 1, Line 1
> Table error: Page (1:3727310) allocated to object ID 1634104862, index ID
0
> was not seen. Page may be invalid or have incorrect object ID information
> in its header.
> Server: Msg 2533, Level 16, State 1, Line 1
> Table error: Page (1:3727311) allocated to object ID 1634104862, index ID
0
> was not seen. Page may be invalid or have incorrect object ID information
> in its header.
> Server: Msg 2533, Level 16, State 1, Line 1
> Table error: Page (1:3727312) allocated to object ID 1634104862, index ID
0
> was not seen. Page may be invalid or have incorrect object ID information
> in its header.
> Server: Msg 2533, Level 16, State 1, Line 1
> Table error: Page (1:3727313) allocated to object ID 1634104862, index ID
0
> was not seen. Page may be invalid or have incorrect object ID information
> in its header.
> Server: Msg 2533, Level 16, State 1, Line 1
> Table error: Page (1:3727314) allocated to object ID 1634104862, index ID
0
> was not seen. Page may be invalid or have incorrect object ID information
> in its header.
> Server: Msg 8928, Level 16, State 1, Line 1
> Object ID 1634104862, index ID 0: Page (1:3727315) could not be processed.
> See other errors for details.
> Server: Msg 8928, Level 16, State 1, Line 1
> Object ID 1634104862, index ID 0: Page (1:3729587) could not be processed.
> See other errors for details.
> Server: Msg 8941, Level 16, State 1, Line 1
> Table error: Object ID 1634104862, index ID 0, page (1:3729587). Test
> (sorted [i].offset >= PAGEHEADSIZE) failed. Slot 57, offset 0x2e is
invalid.
> Server: Msg 8942, Level 16, State 101, Line 1
> Table error: Object ID 1634104862, index ID 0, page (1:3729587). Test
> (sorted[i].offset >= max) failed. Slot 0, offset 0x39 overlaps with the
> prior row.
> Server: Msg 2533, Level 16, State 1, Line 1
> Table error: Page (1:3729588) allocated to object ID 1634104862, index ID
0
> was not seen. Page may be invalid or have incorrect object ID information
> in its header.
> Server: Msg 2533, Level 16, State 1, Line 1
> Table error: Page (1:3729589) allocated to object ID 1634104862, index ID
0
> was not seen. Page may be invalid or have incorrect object ID information
> in its header.
> Server: Msg 2533, Level 16, State 1, Line 1
> Table error: Page (1:3729590) allocated to object ID 1634104862, index ID
0
> was not seen. Page may be invalid or have incorrect object ID information
> in its header.
> Server: Msg 2533, Level 16, State 1, Line 1
> Table error: Page (1:3729591) allocated to object ID 1634104862, index ID
0
> was not seen. Page may be invalid or have incorrect object ID information
> in its header.
> Server: Msg 8928, Level 16, State 1, Line 1
> Object ID 1634104862, index ID 0: Page (1:3729592) could not be processed.
> See other errors for details.
> Server: Msg 8976, Level 16, State 1, Line 1
> Table error: Object ID 1634104862, index ID 1. Page (1:3716003) was not
seen
> in the scan although its parent (1:3715435) and previous (1:3716002) refer
> to it. Check any previous errors.
> Server: Msg 8980, Level 16, State 1, Line 1
> Table error: Object ID 1634104862, index ID 1. Index node page
(1:3715435),
> slot 154 refers to child page (1:3716004) and previous child (1:3716003),
> but they were not encountered.
> Server: Msg 8980, Level 16, State 1, Line 1
> Table error: Object ID 1634104862, index ID 1. Index node page
(1:3715435),
> slot 155 refers to child page (1:3716005) and previous child (1:3716004),
> but they were not encountered.
> Server: Msg 8980, Level 16, State 1, Line 1
> Table error: Object ID 1634104862, index ID 1. Index node page
(1:3715435),
> slot 156 refers to child page (1:3716006) and previous child (1:3716005),
> but they were not encountered.
> Server: Msg 8980, Level 16, State 1, Line 1
> Table error: Object ID 1634104862, index ID 1. Index node page
(1:3715435),
> slot 157 refers to child page (1:3716007) and previous child (1:3716006),
> but they were not encountered.
> Server: Msg 8976, Level 16, State 1, Line 1
> Table error: Object ID 1634104862, index ID 1. Page (1:3716008) was not
seen
> in the scan although its parent (1:3714274) and previous (1:3715943) refer
> to it. Check any previous errors.
> Server: Msg 8980, Level 16, State 1, Line 1
> Table error: Object ID 1634104862, index ID 1. Index node page
(1:3714274),
> slot 167 refers to child page (1:3716009) and previous child (1:3716008),
> but they were not encountered.
> Server: Msg 8980, Level 16, State 1, Line 1
> Table error: Object ID 1634104862, index ID 1. Index node page
(1:3714274),
> slot 168 refers to child page (1:3716010) and previous child (1:3716009),
> but they were not encountered.
> Server: Msg 8980, Level 16, State 1, Line 1
> Table error: Object ID 1634104862, index ID 1. Index node page
(1:3714274),
> slot 169 refers to child page (1:3716011) and previous child (1:3716010),
> but they were not encountered.
> Server: Msg 8978, Level 16, State 1, Line 1
> Table error: Object ID 1634104862, index ID 1. Page (1:3716012) is missing
a
> reference from previous page (1:3716011). Possible chain linkage problem.
> Server: Msg 8978, Level 16, State 1, Line 1
> Table error: Object ID 1634104862, index ID 1. Page (1:3716104) is missing
a
> reference from previous page (1:3716007). Possible chain linkage problem.
> Server: Msg 8976, Level 16, State 1, Line 1
> Table error: Object ID 1634104862, index ID 1. Page (1:3727307) was not
seen
> in the scan although its parent (1:3726987) and previous (1:3727306) refer
> to it. Check any previous errors.
> Server: Msg 8980, Level 16, State 1, Line 1
> Table error: Object ID 1634104862, index ID 1. Index node page
(1:3726987),
> slot 131 refers to child page (1:3727308) and previous child (1:3727307),
> but they were not encountered.
> Server: Msg 8980, Level 16, State 1, Line 1
> Table error: Object ID 1634104862, index ID 1. Index node page
(1:3726987),
> slot 132 refers to child page (1:3727309) and previous child (1:3727308),
> but they were not encountered.
> Server: Msg 8980, Level 16, State 1, Line 1
> Table error: Object ID 1634104862, index ID 1. Index node page
(1:3726987),
> slot 133 refers to child page (1:3727310) and previous child (1:3727309),
> but they were not encountered.
> Server: Msg 8980, Level 16, State 1, Line 1
> Table error: Object ID 1634104862, index ID 1. Index node page
(1:3726987),
> slot 134 refers to child page (1:3727311) and previous child (1:3727310),
> but they were not encountered.
> Server: Msg 8980, Level 16, State 1, Line 1
> Table error: Object ID 1634104862, index ID 1. Index node page
(1:3726987),
> slot 135 refers to child page (1:3727312) and previous child (1:3727311),
> but they were not encountered.
> Server: Msg 8980, Level 16, State 1, Line 1
> Table error: Object ID 1634104862, index ID 1. Index node page
(1:3726987),
> slot 136 refers to child page (1:3727313) and previous child (1:3727312),
> but they were not encountered.
> Server: Msg 8980, Level 16, State 1, Line 1
> Table error: Object ID 1634104862, index ID 1. Index node page
(1:3726987),
> slot 137 refers to child page (1:3727314) and previous child (1:3727313),
> but they were not encountered.
> Server: Msg 8980, Level 16, State 1, Line 1
> Table error: Object ID 1634104862, index ID 1. Index node page
(1:3726987),
> slot 138 refers to child page (1:3727315) and previous child (1:3727314),
> but they were not encountered.
> Server: Msg 8978, Level 16, State 1, Line 1
> Table error: Object ID 1634104862, index ID 1. Page (1:3727316) is missing
a
> reference from previous page (1:3727315). Possible chain linkage problem.
> Server: Msg 8976, Level 16, State 1, Line 1
> Table error: Object ID 1634104862, index ID 1. Page (1:3729587) was not
seen
> in the scan although its parent (1:3729110) and previous (1:3729586) refer
> to it. Check any previous errors.
> Server: Msg 8980, Level 16, State 1, Line 1
> Table error: Object ID 1634104862, index ID 1. Index node page
(1:3729110),
> slot 126 refers to child page (1:3729588) and previous child (1:3729587),
> but they were not encountered.
> Server: Msg 8980, Level 16, State 1, Line 1
> Table error: Object ID 1634104862, index ID 1. Index node page
(1:3729110),
> slot 127 refers to child page (1:3729589) and previous child (1:3729588),
> but they were not encountered.
> Server: Msg 8980, Level 16, State 1, Line 1
> Table error: Object ID 1634104862, index ID 1. Index node page
(1:3729110),
> slot 128 refers to child page (1:3729590) and previous child (1:3729589),
> but they were not encountered.
> Server: Msg 8980, Level 16, State 1, Line 1
> Table error: Object ID 1634104862, index ID 1. Index node page
(1:3729110),
> slot 129 refers to child page (1:3729591) and previous child (1:3729590),
> but they were not encountered.
> Server: Msg 8976, Level 16, State 1, Line 1
> Table error: Object ID 1634104862, index ID 1. Page (1:3729592) was not
seen
> in the scan although its parent (1:564380) and previous (1:3729431) refer
to
> it. Check any previous errors.
> Server: Msg 8978, Level 16, State 1, Line 1
> Table error: Object ID 1634104862, index ID 1. Page (1:3729593) is missing
a
> reference from previous page (1:3729592). Possible chain linkage problem.
> Server: Msg 8978, Level 16, State 1, Line 1
> Table error: Object ID 1634104862, index ID 1. Page (1:3729688) is missing
a[vbcol=seagreen]
> reference from previous page (1:3729591). Possible chain linkage problem.
> There are 2078683 rows in 34246 pages for object 'TIMESHEETS'.
> CHECKDB found 0 allocation errors and 58 consistency errors in table
> 'TIMESHEETS' (object ID 1634104862).
> "Paul S Randal [MS]" <prandal@.online.microsoft.com> wrote in message
> news:%23MmIm4TUFHA.1148@.tk2msftngp13.phx.gbl...
The[vbcol=seagreen]
command
>
|||Hi Paul
This is a test database. For doing load test we pumped lot of data into
this database and after pumping the data we rebuild the indexes in this
database. After the error we created a new database and loaded 40 GB data
and now everything works perfect. We found the bottleneck is harddisk. At
present database resides on a RAID 5 array. (Both mdf and ldf files are in
same array). We are planning to keep LDF file on separate RAID 1 array to
increase the performance.
What is your opinion on this setup?
Thanks
Ram
"Paul S Randal [MS]" <prandal@.online.microsoft.com> wrote in message
news:e$$NWPbUFHA.1152@.tk2msftngp13.phx.gbl...
> Well it certainly looks like the backup contains a corrupt database but if
> something went badly wrong during a disk defrag I'd expect to see more
> obvious errors (e.g. the restore fails, recovery fails, or large chunks of
> pages missing) rather than specific things like the 8944s in
> GRIEVANCEFOLLOWUP.
> Did the restore itself give any errors, during recovery maybe? Given that
> there are several whole extents missing, it looks like an optimized index
> build was partially rolled back or forward by recovery.
> I think your best bet is going to be contacting PSS rather than trying to
> do
> this over a newsgroup.
> Regards.
> --
> Paul Randal
> Dev Lead, Microsoft SQL Server Storage Engine
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> "Ram" <Ramakrishna.pothuganti@.vizual.co.in> wrote in message
> news:e26lVIVUFHA.1384@.TK2MSFTNGP09.phx.gbl...
> Test
> Values
> Test
> Values
> Test
> Values
> 0
> 0
> 0
> 0
> 0
> 0
> 0
> Test
> Test
> 0
> 0
> 0
> 0
> 0
> 0
> 0
> invalid.
> 0
> 0
> 0
> 0
> seen
> (1:3715435),
> (1:3715435),
> (1:3715435),
> (1:3715435),
> seen
> (1:3714274),
> (1:3714274),
> (1:3714274),
> a
> a
> seen
> (1:3726987),
> (1:3726987),
> (1:3726987),
> (1:3726987),
> (1:3726987),
> (1:3726987),
> (1:3726987),
> (1:3726987),
> a
> seen
> (1:3729110),
> (1:3729110),
> (1:3729110),
> (1:3729110),
> seen
> to
> a
> a
> The
> command
>
|||You should definitely separate the log and data files if possible and not
using some 'intelligent' controller.
Have a read of the whitepaper below on the IO system we have.
http://www.microsoft.com/technet/pro...lIObasics.mspx
Regards.
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Ram" <Ramakrishna.pothuganti@.vizual.co.in> wrote in message
news:OTzTkViUFHA.900@.TK2MSFTNGP10.phx.gbl...
> Hi Paul
> This is a test database. For doing load test we pumped lot of data into
> this database and after pumping the data we rebuild the indexes in this
> database. After the error we created a new database and loaded 40 GB data
> and now everything works perfect. We found the bottleneck is harddisk.
At
> present database resides on a RAID 5 array. (Both mdf and ldf files are in
> same array). We are planning to keep LDF file on separate RAID 1 array
to[vbcol=seagreen]
> increase the performance.
> What is your opinion on this setup?
> Thanks
> Ram
> "Paul S Randal [MS]" <prandal@.online.microsoft.com> wrote in message
> news:e$$NWPbUFHA.1152@.tk2msftngp13.phx.gbl...
if[vbcol=seagreen]
of[vbcol=seagreen]
that[vbcol=seagreen]
index[vbcol=seagreen]
to[vbcol=seagreen]
47.[vbcol=seagreen]
ID[vbcol=seagreen]
ID[vbcol=seagreen]
ID[vbcol=seagreen]
ID[vbcol=seagreen]
ID[vbcol=seagreen]
ID[vbcol=seagreen]
ID[vbcol=seagreen]
failed.[vbcol=seagreen]
ID[vbcol=seagreen]
ID[vbcol=seagreen]
ID[vbcol=seagreen]
ID[vbcol=seagreen]
ID[vbcol=seagreen]
ID[vbcol=seagreen]
ID[vbcol=seagreen]
ID[vbcol=seagreen]
ID[vbcol=seagreen]
ID[vbcol=seagreen]
ID[vbcol=seagreen]
(1:3716003),[vbcol=seagreen]
(1:3716004),[vbcol=seagreen]
(1:3716005),[vbcol=seagreen]
(1:3716006),[vbcol=seagreen]
(1:3716008),[vbcol=seagreen]
(1:3716009),[vbcol=seagreen]
(1:3716010),[vbcol=seagreen]
problem.[vbcol=seagreen]
problem.[vbcol=seagreen]
(1:3727307),[vbcol=seagreen]
(1:3727308),[vbcol=seagreen]
(1:3727309),[vbcol=seagreen]
(1:3727310),[vbcol=seagreen]
(1:3727311),[vbcol=seagreen]
(1:3727312),[vbcol=seagreen]
(1:3727313),[vbcol=seagreen]
(1:3727314),[vbcol=seagreen]
problem.[vbcol=seagreen]
(1:3729587),[vbcol=seagreen]
(1:3729588),[vbcol=seagreen]
(1:3729589),[vbcol=seagreen]
(1:3729590),[vbcol=seagreen]
refer[vbcol=seagreen]
problem.[vbcol=seagreen]
problem.[vbcol=seagreen]
drive.
>