dbcc shrinkfile & recovery mode

Occasionally, we have gotten messages that the logfile is too big on one
of our servers. At that point, we will run a backup of the database and
then dbcc shrinkfile on it.
From what I've read, I thought that some of the properties we have set
would make it unnecessary to have to do that. On the Options tab on the
database properties, we have the Recovery model set to Simple, and have
the following settings checked: Auto Update Statistics, Auto Shrink,
and Auto Create Statistics.
Is there another setting I'm missing? Or, should I just set up a job to
back up the database and run the dbcc shrinkfile on it at set intervals?
BC
AutoShrink is taking your log file down to a very minimal size when it runs,
and then your Autogrow has to kick in when the db has a lot of
activity...if it is very busy, it could grow quite large. I've never seen
a SQL Server message "too big"...what are you really getting, and what is
the size at that point.?
In theory, if you set the db to Simple and DBCC Shrinkfile it down to a size
that is big enough to handle your busiest time frames you should be good
from there.
Kevin Hill
President
3NF Consulting
www.3nf-inc.com/NewsGroups.htm
www.DallasDBAs.com/forum - new DB forum for Dallas/Ft. Worth area DBAs.
www.experts-exchange.com - experts compete for points to answer your
questions
"Blasting Cap" <goober@.christian.net> wrote in message
news:%23xn12hncFHA.1384@.TK2MSFTNGP09.phx.gbl...
> Occasionally, we have gotten messages that the logfile is too big on one
> of our servers. At that point, we will run a backup of the database and
> then dbcc shrinkfile on it.
> From what I've read, I thought that some of the properties we have set
> would make it unnecessary to have to do that. On the Options tab on the
> database properties, we have the Recovery model set to Simple, and have
> the following settings checked: Auto Update Statistics, Auto Shrink, and
> Auto Create Statistics.
> Is there another setting I'm missing? Or, should I just set up a job to
> back up the database and run the dbcc shrinkfile on it at set intervals?
> BC

dbcc shrinkfile & recovery mode

Occasionally, we have gotten messages that the logfile is too big on one
of our servers. At that point, we will run a backup of the database and
then dbcc shrinkfile on it.
From what I've read, I thought that some of the properties we have set
would make it unnecessary to have to do that. On the Options tab on the
database properties, we have the Recovery model set to Simple, and have
the following settings checked: Auto Update Statistics, Auto Shrink,
and Auto Create Statistics.
Is there another setting I'm missing? Or, should I just set up a job to
back up the database and run the dbcc shrinkfile on it at set intervals?
BCAutoShrink is taking your log file down to a very minimal size when it runs,
and then your Autogrow has to kick in when the db has a lot of
activity...if it is very busy, it could grow quite large. I've never seen
a SQL Server message "too big"...what are you really getting, and what is
the size at that point.?
In theory, if you set the db to Simple and DBCC Shrinkfile it down to a size
that is big enough to handle your busiest time frames you should be good
from there.
Kevin Hill
President
3NF Consulting
www.3nf-inc.com/NewsGroups.htm
www.DallasDBAs.com/forum - new DB forum for Dallas/Ft. Worth area DBAs.
www.experts-exchange.com - experts compete for points to answer your
questions
"Blasting Cap" <goober@.christian.net> wrote in message
news:%23xn12hncFHA.1384@.TK2MSFTNGP09.phx.gbl...
> Occasionally, we have gotten messages that the logfile is too big on one
> of our servers. At that point, we will run a backup of the database and
> then dbcc shrinkfile on it.
> From what I've read, I thought that some of the properties we have set
> would make it unnecessary to have to do that. On the Options tab on the
> database properties, we have the Recovery model set to Simple, and have
> the following settings checked: Auto Update Statistics, Auto Shrink, and
> Auto Create Statistics.
> Is there another setting I'm missing? Or, should I just set up a job to
> back up the database and run the dbcc shrinkfile on it at set intervals?
> BC

dbcc shrinkfile & recovery mode

Occasionally, we have gotten messages that the logfile is too big on one
of our servers. At that point, we will run a backup of the database and
then dbcc shrinkfile on it.
From what I've read, I thought that some of the properties we have set
would make it unnecessary to have to do that. On the Options tab on the
database properties, we have the Recovery model set to Simple, and have
the following settings checked: Auto Update Statistics, Auto Shrink,
and Auto Create Statistics.
Is there another setting I'm missing? Or, should I just set up a job to
back up the database and run the dbcc shrinkfile on it at set intervals?
BCAutoShrink is taking your log file down to a very minimal size when it runs,
and then your Autogrow has to kick in when the db has a lot of
activity...if it is very busy, it could grow quite large. I've never seen
a SQL Server message "too big"...what are you really getting, and what is
the size at that point.?
In theory, if you set the db to Simple and DBCC Shrinkfile it down to a size
that is big enough to handle your busiest time frames you should be good
from there.
--
Kevin Hill
President
3NF Consulting
www.3nf-inc.com/NewsGroups.htm
www.DallasDBAs.com/forum - new DB forum for Dallas/Ft. Worth area DBAs.
www.experts-exchange.com - experts compete for points to answer your
questions
"Blasting Cap" <goober@.christian.net> wrote in message
news:%23xn12hncFHA.1384@.TK2MSFTNGP09.phx.gbl...
> Occasionally, we have gotten messages that the logfile is too big on one
> of our servers. At that point, we will run a backup of the database and
> then dbcc shrinkfile on it.
> From what I've read, I thought that some of the properties we have set
> would make it unnecessary to have to do that. On the Options tab on the
> database properties, we have the Recovery model set to Simple, and have
> the following settings checked: Auto Update Statistics, Auto Shrink, and
> Auto Create Statistics.
> Is there another setting I'm missing? Or, should I just set up a job to
> back up the database and run the dbcc shrinkfile on it at set intervals?
> BC

DBCC Showcontig

Does anyone know why i get this answer:
DBCC execution completed. If DBCC printed error messages,
contact your system administrator. when i do a dbcc
showcontig ofa table? BUt another table gives me results..
Any explanation?
ThanxsPerhaps that table doesn't have any indexes? Use sp_helpindex to check which indexes each table has.
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"smiley" <anonymous@.discussions.microsoft.com> wrote in message
news:059601c3adcc$d57d2cf0$a401280a@.phx.gbl...
> Does anyone know why i get this answer:
> DBCC execution completed. If DBCC printed error messages,
> contact your system administrator. when i do a dbcc
> showcontig ofa table? BUt another table gives me results..
> Any explanation?
> Thanxssql

dbcc completed messages

How do you avoid them (from Qa and/or a VB program)?
Thanks in advance!
KOni.
Generally you can specify with no_infomsgs to avoid the "DBCC execution
completed. If DBCC printed error messages, contact your system
administrator." message e.g.
dbcc memorystatus with no_infomsgs
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Koni Kogan" <kkogan@.haiint.com> wrote in message
news:%23fJ2rQnVFHA.3636@.TK2MSFTNGP14.phx.gbl...
> How do you avoid them (from Qa and/or a VB program)?
> Thanks in advance!
> KOni.

dbcc completed messages

How do you avoid them (from Qa and/or a VB program)?
Thanks in advance!
KOni.Generally you can specify with no_infomsgs to avoid the "DBCC execution
completed. If DBCC printed error messages, contact your system
administrator." message e.g.
dbcc memorystatus with no_infomsgs
--
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Koni Kogan" <kkogan@.haiint.com> wrote in message
news:%23fJ2rQnVFHA.3636@.TK2MSFTNGP14.phx.gbl...
> How do you avoid them (from Qa and/or a VB program)?
> Thanks in advance!
> KOni.

dbcc completed messages

How do you avoid them (from Qa and/or a VB program)?
Thanks in advance!
KOni.Generally you can specify with no_infomsgs to avoid the "DBCC execution
completed. If DBCC printed error messages, contact your system
administrator." message e.g.
dbcc memorystatus with no_infomsgs
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Koni Kogan" <kkogan@.haiint.com> wrote in message
news:%23fJ2rQnVFHA.3636@.TK2MSFTNGP14.phx.gbl...
> How do you avoid them (from Qa and/or a VB program)?
> Thanks in advance!
> KOni.

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' (