dbcc output capture

Hi
Is there a way to capture the dbcc output into a t-sql variable or in
table.
Thanks
MangeshMangesh Deshpande wrote:
> Hi
> Is there a way to capture the dbcc output into a t-sql variable
> or in table.
>
> Thanks
> Mangesh
Many DBCC statements in SQL 2000 offer a WITH TABLERESULTS option that
return the information as a result set. You can insert into a temp table
using:
create table #dbcc_test (tran_item nvarchar(128), tran_val
nvarchar(128))
insert into #dbcc_test
Exec ('dbcc opentran (''pubs'') with tableresults')
Select * from #dbcc_test
Drop table #dbcc_test
David Gugick
Imceda Software
www.imceda.com|||I'm not sure which command you're trying to capture results for, but please
note that the TABLERESULTS option is not supported for use with DBCC
commands unless Books Online specifically indicates its use in the syntax
diagram.
Thanks,
--
Ryan Stonecipher
Microsoft SQL Server Storage Engine, DBCC
This posting is provided "AS IS" with no warranties, and confers no rights.
"David Gugick" <davidg-nospam@.imceda.com> wrote in message
news:%23sso5TsIFHA.1860@.TK2MSFTNGP15.phx.gbl...
> Mangesh Deshpande wrote:
> Many DBCC statements in SQL 2000 offer a WITH TABLERESULTS option that
> return the information as a result set. You can insert into a temp table
> using:
> create table #dbcc_test (tran_item nvarchar(128), tran_val nvarchar(128))
> insert into #dbcc_test
> Exec ('dbcc opentran (''pubs'') with tableresults')
> Select * from #dbcc_test
> Drop table #dbcc_test
>
> --
> David Gugick
> Imceda Software
> www.imceda.com|||Thanks. The real coincedence. I wanted to write the script to use
dbcc indexdefrag using dbcc showcontig utility by capturing the output and
selectively running for some tables where scan density is low. But I found
the exact same script in MS SQL 2000 doc. Thanks again.
"Ryan Stonecipher [MSFT]" wrote:

> I'm not sure which command you're trying to capture results for, but pleas
e
> note that the TABLERESULTS option is not supported for use with DBCC
> commands unless Books Online specifically indicates its use in the syntax
> diagram.
> Thanks,
> --
> Ryan Stonecipher
> Microsoft SQL Server Storage Engine, DBCC
> This posting is provided "AS IS" with no warranties, and confers no rights
.
> "David Gugick" <davidg-nospam@.imceda.com> wrote in message
> news:%23sso5TsIFHA.1860@.TK2MSFTNGP15.phx.gbl...
>
>

dbcc output capture

Hi
Is there a way to capture the dbcc output into a t-sql variable or in
table.
Thanks
Mangesh
Mangesh Deshpande wrote:
> Hi
> Is there a way to capture the dbcc output into a t-sql variable
> or in table.
>
> Thanks
> Mangesh
Many DBCC statements in SQL 2000 offer a WITH TABLERESULTS option that
return the information as a result set. You can insert into a temp table
using:
create table #dbcc_test (tran_item nvarchar(128), tran_val
nvarchar(128))
insert into #dbcc_test
Exec ('dbcc opentran (''pubs'') with tableresults')
Select * from #dbcc_test
Drop table #dbcc_test
David Gugick
Imceda Software
www.imceda.com
|||I'm not sure which command you're trying to capture results for, but please
note that the TABLERESULTS option is not supported for use with DBCC
commands unless Books Online specifically indicates its use in the syntax
diagram.
Thanks,
Ryan Stonecipher
Microsoft SQL Server Storage Engine, DBCC
This posting is provided "AS IS" with no warranties, and confers no rights.
"David Gugick" <davidg-nospam@.imceda.com> wrote in message
news:%23sso5TsIFHA.1860@.TK2MSFTNGP15.phx.gbl...
> Mangesh Deshpande wrote:
> Many DBCC statements in SQL 2000 offer a WITH TABLERESULTS option that
> return the information as a result set. You can insert into a temp table
> using:
> create table #dbcc_test (tran_item nvarchar(128), tran_val nvarchar(128))
> insert into #dbcc_test
> Exec ('dbcc opentran (''pubs'') with tableresults')
> Select * from #dbcc_test
> Drop table #dbcc_test
>
> --
> David Gugick
> Imceda Software
> www.imceda.com
|||Thanks. The real coincedence. I wanted to write the script to use
dbcc indexdefrag using dbcc showcontig utility by capturing the output and
selectively running for some tables where scan density is low. But I found
the exact same script in MS SQL 2000 doc. Thanks again.
"Ryan Stonecipher [MSFT]" wrote:

> I'm not sure which command you're trying to capture results for, but please
> note that the TABLERESULTS option is not supported for use with DBCC
> commands unless Books Online specifically indicates its use in the syntax
> diagram.
> Thanks,
> --
> Ryan Stonecipher
> Microsoft SQL Server Storage Engine, DBCC
> This posting is provided "AS IS" with no warranties, and confers no rights.
> "David Gugick" <davidg-nospam@.imceda.com> wrote in message
> news:%23sso5TsIFHA.1860@.TK2MSFTNGP15.phx.gbl...
>
>

dbcc output capture

Hi
Is there a way to capture the dbcc output into a t-sql variable or in
table.
Thanks
MangeshMangesh Deshpande wrote:
> Hi
> Is there a way to capture the dbcc output into a t-sql variable
> or in table.
>
> Thanks
> Mangesh
Many DBCC statements in SQL 2000 offer a WITH TABLERESULTS option that
return the information as a result set. You can insert into a temp table
using:
create table #dbcc_test (tran_item nvarchar(128), tran_val
nvarchar(128))
insert into #dbcc_test
Exec ('dbcc opentran (''pubs'') with tableresults')
Select * from #dbcc_test
Drop table #dbcc_test
David Gugick
Imceda Software
www.imceda.com|||I'm not sure which command you're trying to capture results for, but please
note that the TABLERESULTS option is not supported for use with DBCC
commands unless Books Online specifically indicates its use in the syntax
diagram.
Thanks,
--
Ryan Stonecipher
Microsoft SQL Server Storage Engine, DBCC
This posting is provided "AS IS" with no warranties, and confers no rights.
"David Gugick" <davidg-nospam@.imceda.com> wrote in message
news:%23sso5TsIFHA.1860@.TK2MSFTNGP15.phx.gbl...
> Mangesh Deshpande wrote:
>> Hi
>> Is there a way to capture the dbcc output into a t-sql variable
>> or in table.
>>
>> Thanks
>> Mangesh
> Many DBCC statements in SQL 2000 offer a WITH TABLERESULTS option that
> return the information as a result set. You can insert into a temp table
> using:
> create table #dbcc_test (tran_item nvarchar(128), tran_val nvarchar(128))
> insert into #dbcc_test
> Exec ('dbcc opentran (''pubs'') with tableresults')
> Select * from #dbcc_test
> Drop table #dbcc_test
>
> --
> David Gugick
> Imceda Software
> www.imceda.com|||Thanks. The real coincedence. I wanted to write the script to use
dbcc indexdefrag using dbcc showcontig utility by capturing the output and
selectively running for some tables where scan density is low. But I found
the exact same script in MS SQL 2000 doc. Thanks again.
"Ryan Stonecipher [MSFT]" wrote:
> I'm not sure which command you're trying to capture results for, but please
> note that the TABLERESULTS option is not supported for use with DBCC
> commands unless Books Online specifically indicates its use in the syntax
> diagram.
> Thanks,
> --
> Ryan Stonecipher
> Microsoft SQL Server Storage Engine, DBCC
> This posting is provided "AS IS" with no warranties, and confers no rights.
> "David Gugick" <davidg-nospam@.imceda.com> wrote in message
> news:%23sso5TsIFHA.1860@.TK2MSFTNGP15.phx.gbl...
> > Mangesh Deshpande wrote:
> >> Hi
> >>
> >> Is there a way to capture the dbcc output into a t-sql variable
> >> or in table.
> >>
> >>
> >> Thanks
> >> Mangesh
> >
> > Many DBCC statements in SQL 2000 offer a WITH TABLERESULTS option that
> > return the information as a result set. You can insert into a temp table
> > using:
> >
> > create table #dbcc_test (tran_item nvarchar(128), tran_val nvarchar(128))
> >
> > insert into #dbcc_test
> > Exec ('dbcc opentran (''pubs'') with tableresults')
> >
> > Select * from #dbcc_test
> >
> > Drop table #dbcc_test
> >
> >
> > --
> > David Gugick
> > Imceda Software
> > www.imceda.com
>
>sql

DBCC CheckDB Repair_Rebuild caused data loss.

Hi,
I tried Repair_Rebuild option in 7.0 . I was thinking that the following DBC
C command would not cause any data loss, which also noted in T-SQL Reference
s:
DBCC CHECKDB (dadabase name, REPAIR_FAST)
I lost 285 rows in a table that has total 103 thousand rows. (Thanks to back
ups, I was able to get those rows back.) Is data loss possible while using R
epair_rebuild option?
I got following messages:
...
Server: Msg 8993, Level 16, State 1, Line 0
Object ID 1656497080, forwarding row page (1:27122), slot 9 points to page (
1:242059), slot 14. Did not encounter forwarded row. Possible allocation err
or.
(I believe 285 times.)
...
The error has been repaired.
(I believe 285 times.)
...
Repair: Deleted record for object ID 1656497080, index ID 0, on page (1:2712
2), slot 9. Indexes will be rebuilt.
(I believe 285 times.)
...
CHECKDB fixed 0 allocation errors and 285 consistency errors in table 'table
name'. (object ID 1656497080).
...
CHECKDB fixed 0 allocation errors and 285 consistency errors in database 'da
tabasename'.
...
Thanks,
Akin HocaI tried following DBCC command: DBCC CHECKDB (dadabase name, Repair_Rebuild)
not DBCC CHECKDB (dadabase name, REPAIR_FAST)
Thanks,
Akin
-- Akin wrote: --
Hi,
I tried Repair_Rebuild option in 7.0 . I was thinking that the following DBC
C command would not cause any data loss, which also noted in T-SQL Reference
s:
DBCC CHECKDB (dadabase name, REPAIR_FAST)
I lost 285 rows in a table that has total 103 thousand rows. (Thanks to back
ups, I was able to get those rows back.) Is data loss possible while using R
epair_rebuild option?
I got following messages:
..
Server: Msg 8993, Level 16, State 1, Line 0
Object ID 1656497080, forwarding row page (1:27122), slot 9 points to page (
1:242059), slot 14. Did not encounter forwarded row. Possible allocation err
or.
(I believe 285 times.)
..
The error has been repaired.
(I believe 285 times.)
..
Repair: Deleted record for object ID 1656497080, index ID 0, on page (1:2712
2), slot 9. Indexes will be rebuilt.
(I believe 285 times.)
..
CHECKDB fixed 0 allocation errors and 285 consistency errors in table 'table
name'. (object ID 1656497080).
..
CHECKDB fixed 0 allocation errors and 285 consistency errors in database 'da
tabasename'.
..
Thanks,
Akin Hoca|||You didn't lose any data as part of the repair. What happened was that you
had 285 forwarding records point to non-existent records.
When a heap record is updated such that it grows and there is no space for
the record to expand, it is moved to a new location in the heap. This new
location is called a forwarded record. The old location then contains a
pointer to the new location. The pointer in the old location is called a
forwarding record. Non-clustered indexes on heaps refer back to the heap
records using a physical record identifier (i.e. the file/page/slot of the
record). Using the forwarded row mechanism means that updates to heap
records do not cause updates to non-clustered indexes on the heap. It's an
optimization mechanism.
So, your heap had 285 of the pointer records in that did not point to
updated copies of the original record. These were deleted by repair and this
is allowed under repair_rebuild, because no data is being lost. The
non-clustered indexes were rebuilt because they would have referenced the
285 pointer records, and so must be rebuilt to remove those references.
Please let me know if that did not make sense.
Now, the more interesting question is how did this situation arise in the
first place? That I do not know and you may want to call PSS for assistance.
Regards.
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Akin" <anonymous@.discussions.microsoft.com> wrote in message
news:7E85386A-0102-4B30-8BF1-BB123342C065@.microsoft.com...
> I tried following DBCC command: DBCC CHECKDB (dadabase name,
Repair_Rebuild)
> not DBCC CHECKDB (dadabase name, REPAIR_FAST)
> Thanks,
> Akin
>
> -- Akin wrote: --
> Hi,
> I tried Repair_Rebuild option in 7.0 . I was thinking that the
following DBCC command would not cause any data loss, which also noted in
T-SQL References:
> DBCC CHECKDB (dadabase name, REPAIR_FAST)
> I lost 285 rows in a table that has total 103 thousand rows. (Thanks
to backups, I was able to get those rows back.) Is data loss possible while
using Repair_rebuild option?
> I got following messages:
> ...
> Server: Msg 8993, Level 16, State 1, Line 0
> Object ID 1656497080, forwarding row page (1:27122), slot 9 points to
page (1:242059), slot 14. Did not encounter forwarded row. Possible
allocation error.
> (I believe 285 times.)
> ...
> The error has been repaired.
> (I believe 285 times.)
> ...
> Repair: Deleted record for object ID 1656497080, index ID 0, on page
(1:27122), slot 9. Indexes will be rebuilt.
> (I believe 285 times.)
> ...
> CHECKDB fixed 0 allocation errors and 285 consistency errors in table
'tablename'. (object ID 1656497080).
> ...
> CHECKDB fixed 0 allocation errors and 285 consistency errors in
database 'databasename'.
> ...
> Thanks,
> Akin Hoca

DBCC CheckDB Repair_Rebuild caused data loss.

Hi,
I tried Repair_Rebuild option in 7.0 . I was thinking that the following DBCC command would not cause any data loss, which also noted in T-SQL References:
DBCC CHECKDB (dadabase name, REPAIR_FAST)
I lost 285 rows in a table that has total 103 thousand rows. (Thanks to backups, I was able to get those rows back.) Is data loss possible while using Repair_rebuild option?
I got following messages:
...
Server: Msg 8993, Level 16, State 1, Line 0
Object ID 1656497080, forwarding row page (1:27122), slot 9 points to page (1:242059), slot 14. Did not encounter forwarded row. Possible allocation error.
(I believe 285 times.)
...
The error has been repaired.
(I believe 285 times.)
...
Repair: Deleted record for object ID 1656497080, index ID 0, on page (1:27122), slot 9. Indexes will be rebuilt.
(I believe 285 times.)
...
CHECKDB fixed 0 allocation errors and 285 consistency errors in table 'tablename'. (object ID 1656497080).
...
CHECKDB fixed 0 allocation errors and 285 consistency errors in database 'databasename'.
...
Thanks,
Akin Hoca
I tried following DBCC command: DBCC CHECKDB (dadabase name, Repair_Rebuild)
not DBCC CHECKDB (dadabase name, REPAIR_FAST)
Thanks,
Akin
-- Akin wrote: --
Hi,
I tried Repair_Rebuild option in 7.0 . I was thinking that the following DBCC command would not cause any data loss, which also noted in T-SQL References:
DBCC CHECKDB (dadabase name, REPAIR_FAST)
I lost 285 rows in a table that has total 103 thousand rows. (Thanks to backups, I was able to get those rows back.) Is data loss possible while using Repair_rebuild option?
I got following messages:
...
Server: Msg 8993, Level 16, State 1, Line 0
Object ID 1656497080, forwarding row page (1:27122), slot 9 points to page (1:242059), slot 14. Did not encounter forwarded row. Possible allocation error.
(I believe 285 times.)
...
The error has been repaired.
(I believe 285 times.)
...
Repair: Deleted record for object ID 1656497080, index ID 0, on page (1:27122), slot 9. Indexes will be rebuilt.
(I believe 285 times.)
...
CHECKDB fixed 0 allocation errors and 285 consistency errors in table 'tablename'. (object ID 1656497080).
...
CHECKDB fixed 0 allocation errors and 285 consistency errors in database 'databasename'.
...
Thanks,
Akin Hoca
|||You didn't lose any data as part of the repair. What happened was that you
had 285 forwarding records point to non-existent records.
When a heap record is updated such that it grows and there is no space for
the record to expand, it is moved to a new location in the heap. This new
location is called a forwarded record. The old location then contains a
pointer to the new location. The pointer in the old location is called a
forwarding record. Non-clustered indexes on heaps refer back to the heap
records using a physical record identifier (i.e. the file/page/slot of the
record). Using the forwarded row mechanism means that updates to heap
records do not cause updates to non-clustered indexes on the heap. It's an
optimization mechanism.
So, your heap had 285 of the pointer records in that did not point to
updated copies of the original record. These were deleted by repair and this
is allowed under repair_rebuild, because no data is being lost. The
non-clustered indexes were rebuilt because they would have referenced the
285 pointer records, and so must be rebuilt to remove those references.
Please let me know if that did not make sense.
Now, the more interesting question is how did this situation arise in the
first place? That I do not know and you may want to call PSS for assistance.
Regards.
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Akin" <anonymous@.discussions.microsoft.com> wrote in message
news:7E85386A-0102-4B30-8BF1-BB123342C065@.microsoft.com...
> I tried following DBCC command: DBCC CHECKDB (dadabase name,
Repair_Rebuild)
> not DBCC CHECKDB (dadabase name, REPAIR_FAST)
> Thanks,
> Akin
>
> -- Akin wrote: --
> Hi,
> I tried Repair_Rebuild option in 7.0 . I was thinking that the
following DBCC command would not cause any data loss, which also noted in
T-SQL References:
> DBCC CHECKDB (dadabase name, REPAIR_FAST)
> I lost 285 rows in a table that has total 103 thousand rows. (Thanks
to backups, I was able to get those rows back.) Is data loss possible while
using Repair_rebuild option?
> I got following messages:
> ...
> Server: Msg 8993, Level 16, State 1, Line 0
> Object ID 1656497080, forwarding row page (1:27122), slot 9 points to
page (1:242059), slot 14. Did not encounter forwarded row. Possible
allocation error.
> (I believe 285 times.)
> ...
> The error has been repaired.
> (I believe 285 times.)
> ...
> Repair: Deleted record for object ID 1656497080, index ID 0, on page
(1:27122), slot 9. Indexes will be rebuilt.
> (I believe 285 times.)
> ...
> CHECKDB fixed 0 allocation errors and 285 consistency errors in table
'tablename'. (object ID 1656497080).
> ...
> CHECKDB fixed 0 allocation errors and 285 consistency errors in
database 'databasename'.
> ...
> Thanks,
> Akin Hoca

DBCC CHECKDB (database) WITH ALL_ERRORMSGS

Yesterday, I received approximately 200 error messages from the T-SQL DBCC
CHECKDB(database) WITH ALL_ERRORMSGS command.
Listed below are some of the output errors that I received.
Please let me know the best way to resolve these errors.
Thank You,
DBCC results for 'ACC_CNTRL_LOG'.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 797961919, index ID 0: Page (1:80654) could not be processed. See
other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 797961919, index ID 0, page (1:80654). Test
(m_freeCnt == freeCnt) failed. Values are 213 and 245.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 797961919, index ID 0: Page (1:81930) could not be processed. See
other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 797961919, index ID 0, page (1:81930). Test
(m_freeCnt == freeCnt) failed. Values are 207 and 239.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 826486023, index ID 0: Page (1:75016) could not be processed. See
other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 826486023, index ID 0, page (1:75016). Test
(m_freeCnt == freeCnt) failed. Values are 221 and 253.
There are 3549 rows in 58 pages for object 'ACC_CNTRL_LOG'.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 826486023, index ID 0: Page (1:81936) could not be processed. See
other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 826486023, index ID 0, page (1:81936). Test
(m_freeCnt == freeCnt) failed. Values are 221 and 253.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 826486023, index ID 0: Page (1:81938) could not be processed. See
other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 826486023, index ID 0, page (1:81938). Test
(m_freeCnt == freeCnt) failed. Values are 213 and 245.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 826486023, index ID 0: Page (1:83168) could not be processed. See
other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 826486023, index ID 0, page (1:83168). Test
(m_freeCnt == freeCnt) failed. Values are 219 and 251.
There are 254060 rows in 6235 pages for object 'USER_ATTR'.
CHECKDB found 0 allocation errors and 8 consistency errors in table
'USER_ATTR' (object ID 826486023).
DBCC results for 'ATTRIBUTE_SUMMARY'.
Server: Msg 8939, Level 16, State 106, Line 1
Table error: Object ID 1975730141, index ID 3, page (1:80730). Test
(m_freeCnt == freeCnt) failed. Values are 24 and 56.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 1975730141, index ID 3. Page (1:80730) was not seen
in the scan although its parent (1:15408) and previous (1:76422) refer to it.
Check any previous errors.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1975730141, index ID 3. Page (1:84752) is missing a
reference from previous page (1:80730). Possible chain linkage problem.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1975730141, index ID 4: Page (1:79858) could not be processed. See
other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 1975730141, index ID 4, page (1:79858). Test
(m_freeCnt == freeCnt) failed. Values are 24 and 56.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 1975730141, index ID 4. Page (1:79858) was not seen
in the scan although its parent (1:81368) and previous (1:74375) refer to it.
Check any previous errors.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1975730141, index ID 4. Page (1:84893) is missing a
reference from previous page (1:79858). Possible chain linkage problem.
There are 153206 rows in 3650 pages for object 'ATTRIBUTE_SUMMARY'.
CHECKDB found 0 allocation errors and 12 consistency errors in table
'ATTRIBUTE_SUMMARY' (You might want to review this
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=738137&SiteID=1
--
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Joe K." <Joe K.@.discussions.microsoft.com> wrote in message
news:57321F20-58C5-4BA8-9EA4-2222531294F9@.microsoft.com...
> Yesterday, I received approximately 200 error messages from the T-SQL DBCC
> CHECKDB(database) WITH ALL_ERRORMSGS command.
> Listed below are some of the output errors that I received.
> Please let me know the best way to resolve these errors.
> Thank You,
>
> DBCC results for 'ACC_CNTRL_LOG'.
> Server: Msg 8928, Level 16, State 1, Line 1
> Object ID 797961919, index ID 0: Page (1:80654) could not be processed.
> See
> other errors for details.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 797961919, index ID 0, page (1:80654). Test
> (m_freeCnt == freeCnt) failed. Values are 213 and 245.
> Server: Msg 8928, Level 16, State 1, Line 1
> Object ID 797961919, index ID 0: Page (1:81930) could not be processed.
> See
> other errors for details.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 797961919, index ID 0, page (1:81930). Test
> (m_freeCnt == freeCnt) failed. Values are 207 and 239.
> Server: Msg 8928, Level 16, State 1, Line 1
> Object ID 826486023, index ID 0: Page (1:75016) could not be processed.
> See
> other errors for details.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 826486023, index ID 0, page (1:75016). Test
> (m_freeCnt == freeCnt) failed. Values are 221 and 253.
> There are 3549 rows in 58 pages for object 'ACC_CNTRL_LOG'.
> Server: Msg 8928, Level 16, State 1, Line 1
> Object ID 826486023, index ID 0: Page (1:81936) could not be processed.
> See
> other errors for details.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 826486023, index ID 0, page (1:81936). Test
> (m_freeCnt == freeCnt) failed. Values are 221 and 253.
> Server: Msg 8928, Level 16, State 1, Line 1
> Object ID 826486023, index ID 0: Page (1:81938) could not be processed.
> See
> other errors for details.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 826486023, index ID 0, page (1:81938). Test
> (m_freeCnt == freeCnt) failed. Values are 213 and 245.
> Server: Msg 8928, Level 16, State 1, Line 1
> Object ID 826486023, index ID 0: Page (1:83168) could not be processed.
> See
> other errors for details.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 826486023, index ID 0, page (1:83168). Test
> (m_freeCnt == freeCnt) failed. Values are 219 and 251.
> There are 254060 rows in 6235 pages for object 'USER_ATTR'.
> CHECKDB found 0 allocation errors and 8 consistency errors in table
> 'USER_ATTR' (object ID 826486023).
>
> DBCC results for 'ATTRIBUTE_SUMMARY'.
> Server: Msg 8939, Level 16, State 106, Line 1
> Table error: Object ID 1975730141, index ID 3, page (1:80730). Test
> (m_freeCnt == freeCnt) failed. Values are 24 and 56.
> Server: Msg 8976, Level 16, State 1, Line 1
> Table error: Object ID 1975730141, index ID 3. Page (1:80730) was not seen
> in the scan although its parent (1:15408) and previous (1:76422) refer to
> it.
> Check any previous errors.
> Server: Msg 8978, Level 16, State 1, Line 1
> Table error: Object ID 1975730141, index ID 3. Page (1:84752) is missing a
> reference from previous page (1:80730). Possible chain linkage problem.
> Server: Msg 8928, Level 16, State 1, Line 1
> Object ID 1975730141, index ID 4: Page (1:79858) could not be processed.
> See
> other errors for details.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 1975730141, index ID 4, page (1:79858). Test
> (m_freeCnt == freeCnt) failed. Values are 24 and 56.
> Server: Msg 8976, Level 16, State 1, Line 1
> Table error: Object ID 1975730141, index ID 4. Page (1:79858) was not seen
> in the scan although its parent (1:81368) and previous (1:74375) refer to
> it.
> Check any previous errors.
> Server: Msg 8978, Level 16, State 1, Line 1
> Table error: Object ID 1975730141, index ID 4. Page (1:84893) is missing a
> reference from previous page (1:79858). Possible chain linkage problem.
> There are 153206 rows in 3650 pages for object 'ATTRIBUTE_SUMMARY'.
> CHECKDB found 0 allocation errors and 12 consistency errors in table
> 'ATTRIBUTE_SUMMARY' (

DBCC CHECKDB (database) WITH ALL_ERRORMSGS

Yesterday, I received approximately 200 error messages from the T-SQL DBCC
CHECKDB(database) WITH ALL_ERRORMSGS command.
Listed below are some of the output errors that I received.
Please let me know the best way to resolve these errors.
Thank You,
DBCC results for 'ACC_CNTRL_LOG'.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 797961919, index ID 0: Page (1:80654) could not be processed. See
other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 797961919, index ID 0, page (1:80654). Test
(m_freeCnt == freeCnt) failed. Values are 213 and 245.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 797961919, index ID 0: Page (1:81930) could not be processed. See
other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 797961919, index ID 0, page (1:81930). Test
(m_freeCnt == freeCnt) failed. Values are 207 and 239.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 826486023, index ID 0: Page (1:75016) could not be processed. See
other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 826486023, index ID 0, page (1:75016). Test
(m_freeCnt == freeCnt) failed. Values are 221 and 253.
There are 3549 rows in 58 pages for object 'ACC_CNTRL_LOG'.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 826486023, index ID 0: Page (1:81936) could not be processed. See
other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 826486023, index ID 0, page (1:81936). Test
(m_freeCnt == freeCnt) failed. Values are 221 and 253.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 826486023, index ID 0: Page (1:81938) could not be processed. See
other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 826486023, index ID 0, page (1:81938). Test
(m_freeCnt == freeCnt) failed. Values are 213 and 245.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 826486023, index ID 0: Page (1:83168) could not be processed. See
other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 826486023, index ID 0, page (1:83168). Test
(m_freeCnt == freeCnt) failed. Values are 219 and 251.
There are 254060 rows in 6235 pages for object 'USER_ATTR'.
CHECKDB found 0 allocation errors and 8 consistency errors in table
'USER_ATTR' (object ID 826486023).
DBCC results for 'ATTRIBUTE_SUMMARY'.
Server: Msg 8939, Level 16, State 106, Line 1
Table error: Object ID 1975730141, index ID 3, page (1:80730). Test
(m_freeCnt == freeCnt) failed. Values are 24 and 56.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 1975730141, index ID 3. Page (1:80730) was not seen
in the scan although its parent (1:15408) and previous (1:76422) refer to it
.
Check any previous errors.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1975730141, index ID 3. Page (1:84752) is missing a
reference from previous page (1:80730). Possible chain linkage problem.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1975730141, index ID 4: Page (1:79858) could not be processed. See
other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 1975730141, index ID 4, page (1:79858). Test
(m_freeCnt == freeCnt) failed. Values are 24 and 56.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 1975730141, index ID 4. Page (1:79858) was not seen
in the scan although its parent (1:81368) and previous (1:74375) refer to it
.
Check any previous errors.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1975730141, index ID 4. Page (1:84893) is missing a
reference from previous page (1:79858). Possible chain linkage problem.
There are 153206 rows in 3650 pages for object 'ATTRIBUTE_SUMMARY'.
CHECKDB found 0 allocation errors and 12 consistency errors in table
'ATTRIBUTE_SUMMARY' (You might want to review this
http://forums.microsoft.com/MSDN/Sh...738137&SiteID=1
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Joe K." <Joe K.@.discussions.microsoft.com> wrote in message
news:57321F20-58C5-4BA8-9EA4-2222531294F9@.microsoft.com...
> Yesterday, I received approximately 200 error messages from the T-SQL DBCC
> CHECKDB(database) WITH ALL_ERRORMSGS command.
> Listed below are some of the output errors that I received.
> Please let me know the best way to resolve these errors.
> Thank You,
>
> DBCC results for 'ACC_CNTRL_LOG'.
> Server: Msg 8928, Level 16, State 1, Line 1
> Object ID 797961919, index ID 0: Page (1:80654) could not be processed.
> See
> other errors for details.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 797961919, index ID 0, page (1:80654). Test
> (m_freeCnt == freeCnt) failed. Values are 213 and 245.
> Server: Msg 8928, Level 16, State 1, Line 1
> Object ID 797961919, index ID 0: Page (1:81930) could not be processed.
> See
> other errors for details.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 797961919, index ID 0, page (1:81930). Test
> (m_freeCnt == freeCnt) failed. Values are 207 and 239.
> Server: Msg 8928, Level 16, State 1, Line 1
> Object ID 826486023, index ID 0: Page (1:75016) could not be processed.
> See
> other errors for details.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 826486023, index ID 0, page (1:75016). Test
> (m_freeCnt == freeCnt) failed. Values are 221 and 253.
> There are 3549 rows in 58 pages for object 'ACC_CNTRL_LOG'.
> Server: Msg 8928, Level 16, State 1, Line 1
> Object ID 826486023, index ID 0: Page (1:81936) could not be processed.
> See
> other errors for details.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 826486023, index ID 0, page (1:81936). Test
> (m_freeCnt == freeCnt) failed. Values are 221 and 253.
> Server: Msg 8928, Level 16, State 1, Line 1
> Object ID 826486023, index ID 0: Page (1:81938) could not be processed.
> See
> other errors for details.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 826486023, index ID 0, page (1:81938). Test
> (m_freeCnt == freeCnt) failed. Values are 213 and 245.
> Server: Msg 8928, Level 16, State 1, Line 1
> Object ID 826486023, index ID 0: Page (1:83168) could not be processed.
> See
> other errors for details.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 826486023, index ID 0, page (1:83168). Test
> (m_freeCnt == freeCnt) failed. Values are 219 and 251.
> There are 254060 rows in 6235 pages for object 'USER_ATTR'.
> CHECKDB found 0 allocation errors and 8 consistency errors in table
> 'USER_ATTR' (object ID 826486023).
>
> DBCC results for 'ATTRIBUTE_SUMMARY'.
> Server: Msg 8939, Level 16, State 106, Line 1
> Table error: Object ID 1975730141, index ID 3, page (1:80730). Test
> (m_freeCnt == freeCnt) failed. Values are 24 and 56.
> Server: Msg 8976, Level 16, State 1, Line 1
> Table error: Object ID 1975730141, index ID 3. Page (1:80730) was not seen
> in the scan although its parent (1:15408) and previous (1:76422) refer to
> it.
> Check any previous errors.
> Server: Msg 8978, Level 16, State 1, Line 1
> Table error: Object ID 1975730141, index ID 3. Page (1:84752) is missing a
> reference from previous page (1:80730). Possible chain linkage problem.
> Server: Msg 8928, Level 16, State 1, Line 1
> Object ID 1975730141, index ID 4: Page (1:79858) could not be processed.
> See
> other errors for details.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 1975730141, index ID 4, page (1:79858). Test
> (m_freeCnt == freeCnt) failed. Values are 24 and 56.
> Server: Msg 8976, Level 16, State 1, Line 1
> Table error: Object ID 1975730141, index ID 4. Page (1:79858) was not seen
> in the scan although its parent (1:81368) and previous (1:74375) refer to
> it.
> Check any previous errors.
> Server: Msg 8978, Level 16, State 1, Line 1
> Table error: Object ID 1975730141, index ID 4. Page (1:84893) is missing a
> reference from previous page (1:79858). Possible chain linkage problem.
> There are 153206 rows in 3650 pages for object 'ATTRIBUTE_SUMMARY'.
> CHECKDB found 0 allocation errors and 12 consistency errors in table
> 'ATTRIBUTE_SUMMARY' (

DBCC CHECKDB (database) WITH ALL_ERRORMSGS

Yesterday, I received approximately 200 error messages from the T-SQL DBCC
CHECKDB(database) WITH ALL_ERRORMSGS command.
Listed below are some of the output errors that I received.
Please let me know the best way to resolve these errors.
Thank You,
DBCC results for 'ACC_CNTRL_LOG'.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 797961919, index ID 0: Page (1:80654) could not be processed. See
other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 797961919, index ID 0, page (1:80654). Test
(m_freeCnt == freeCnt) failed. Values are 213 and 245.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 797961919, index ID 0: Page (1:81930) could not be processed. See
other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 797961919, index ID 0, page (1:81930). Test
(m_freeCnt == freeCnt) failed. Values are 207 and 239.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 826486023, index ID 0: Page (1:75016) could not be processed. See
other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 826486023, index ID 0, page (1:75016). Test
(m_freeCnt == freeCnt) failed. Values are 221 and 253.
There are 3549 rows in 58 pages for object 'ACC_CNTRL_LOG'.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 826486023, index ID 0: Page (1:81936) could not be processed. See
other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 826486023, index ID 0, page (1:81936). Test
(m_freeCnt == freeCnt) failed. Values are 221 and 253.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 826486023, index ID 0: Page (1:81938) could not be processed. See
other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 826486023, index ID 0, page (1:81938). Test
(m_freeCnt == freeCnt) failed. Values are 213 and 245.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 826486023, index ID 0: Page (1:83168) could not be processed. See
other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 826486023, index ID 0, page (1:83168). Test
(m_freeCnt == freeCnt) failed. Values are 219 and 251.
There are 254060 rows in 6235 pages for object 'USER_ATTR'.
CHECKDB found 0 allocation errors and 8 consistency errors in table
'USER_ATTR' (object ID 826486023).
DBCC results for 'ATTRIBUTE_SUMMARY'.
Server: Msg 8939, Level 16, State 106, Line 1
Table error: Object ID 1975730141, index ID 3, page (1:80730). Test
(m_freeCnt == freeCnt) failed. Values are 24 and 56.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 1975730141, index ID 3. Page (1:80730) was not seen
in the scan although its parent (1:15408) and previous (1:76422) refer to it.
Check any previous errors.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1975730141, index ID 3. Page (1:84752) is missing a
reference from previous page (1:80730). Possible chain linkage problem.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1975730141, index ID 4: Page (1:79858) could not be processed. See
other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 1975730141, index ID 4, page (1:79858). Test
(m_freeCnt == freeCnt) failed. Values are 24 and 56.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 1975730141, index ID 4. Page (1:79858) was not seen
in the scan although its parent (1:81368) and previous (1:74375) refer to it.
Check any previous errors.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1975730141, index ID 4. Page (1:84893) is missing a
reference from previous page (1:79858). Possible chain linkage problem.
There are 153206 rows in 3650 pages for object 'ATTRIBUTE_SUMMARY'.
CHECKDB found 0 allocation errors and 12 consistency errors in table
'ATTRIBUTE_SUMMARY' (
You might want to review this
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=738137&SiteID=1
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Joe K." <Joe K.@.discussions.microsoft.com> wrote in message
news:57321F20-58C5-4BA8-9EA4-2222531294F9@.microsoft.com...
> Yesterday, I received approximately 200 error messages from the T-SQL DBCC
> CHECKDB(database) WITH ALL_ERRORMSGS command.
> Listed below are some of the output errors that I received.
> Please let me know the best way to resolve these errors.
> Thank You,
>
> DBCC results for 'ACC_CNTRL_LOG'.
> Server: Msg 8928, Level 16, State 1, Line 1
> Object ID 797961919, index ID 0: Page (1:80654) could not be processed.
> See
> other errors for details.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 797961919, index ID 0, page (1:80654). Test
> (m_freeCnt == freeCnt) failed. Values are 213 and 245.
> Server: Msg 8928, Level 16, State 1, Line 1
> Object ID 797961919, index ID 0: Page (1:81930) could not be processed.
> See
> other errors for details.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 797961919, index ID 0, page (1:81930). Test
> (m_freeCnt == freeCnt) failed. Values are 207 and 239.
> Server: Msg 8928, Level 16, State 1, Line 1
> Object ID 826486023, index ID 0: Page (1:75016) could not be processed.
> See
> other errors for details.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 826486023, index ID 0, page (1:75016). Test
> (m_freeCnt == freeCnt) failed. Values are 221 and 253.
> There are 3549 rows in 58 pages for object 'ACC_CNTRL_LOG'.
> Server: Msg 8928, Level 16, State 1, Line 1
> Object ID 826486023, index ID 0: Page (1:81936) could not be processed.
> See
> other errors for details.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 826486023, index ID 0, page (1:81936). Test
> (m_freeCnt == freeCnt) failed. Values are 221 and 253.
> Server: Msg 8928, Level 16, State 1, Line 1
> Object ID 826486023, index ID 0: Page (1:81938) could not be processed.
> See
> other errors for details.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 826486023, index ID 0, page (1:81938). Test
> (m_freeCnt == freeCnt) failed. Values are 213 and 245.
> Server: Msg 8928, Level 16, State 1, Line 1
> Object ID 826486023, index ID 0: Page (1:83168) could not be processed.
> See
> other errors for details.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 826486023, index ID 0, page (1:83168). Test
> (m_freeCnt == freeCnt) failed. Values are 219 and 251.
> There are 254060 rows in 6235 pages for object 'USER_ATTR'.
> CHECKDB found 0 allocation errors and 8 consistency errors in table
> 'USER_ATTR' (object ID 826486023).
>
> DBCC results for 'ATTRIBUTE_SUMMARY'.
> Server: Msg 8939, Level 16, State 106, Line 1
> Table error: Object ID 1975730141, index ID 3, page (1:80730). Test
> (m_freeCnt == freeCnt) failed. Values are 24 and 56.
> Server: Msg 8976, Level 16, State 1, Line 1
> Table error: Object ID 1975730141, index ID 3. Page (1:80730) was not seen
> in the scan although its parent (1:15408) and previous (1:76422) refer to
> it.
> Check any previous errors.
> Server: Msg 8978, Level 16, State 1, Line 1
> Table error: Object ID 1975730141, index ID 3. Page (1:84752) is missing a
> reference from previous page (1:80730). Possible chain linkage problem.
> Server: Msg 8928, Level 16, State 1, Line 1
> Object ID 1975730141, index ID 4: Page (1:79858) could not be processed.
> See
> other errors for details.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 1975730141, index ID 4, page (1:79858). Test
> (m_freeCnt == freeCnt) failed. Values are 24 and 56.
> Server: Msg 8976, Level 16, State 1, Line 1
> Table error: Object ID 1975730141, index ID 4. Page (1:79858) was not seen
> in the scan although its parent (1:81368) and previous (1:74375) refer to
> it.
> Check any previous errors.
> Server: Msg 8978, Level 16, State 1, Line 1
> Table error: Object ID 1975730141, index ID 4. Page (1:84893) is missing a
> reference from previous page (1:79858). Possible chain linkage problem.
> There are 153206 rows in 3650 pages for object 'ATTRIBUTE_SUMMARY'.
> CHECKDB found 0 allocation errors and 12 consistency errors in table
> 'ATTRIBUTE_SUMMARY' (