dbcc checkdb

I found the error 2508 after I ran dbcc checkdb on one of my tables. It
says it found a consistency error. What should I do? Can I run the
dbcc checkdb <dbname>,repair_rebuild.
Please advice.
Regards
JaideepYou have some serious data corruption problems.
Issue a DBCC CHECKDB('DatabaseName',repair_allow_data
_loss)
If this does not fix the problem or cause important data to be lost you will
have to restore the latest backup.
Hopefully you will have a recent backup available you can restore from.
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
"jai" <dbasybase@.gmail.com> wrote in message
news:1157504133.116486.17050@.d34g2000cwd.googlegroups.com...
>I found the error 2508 after I ran dbcc checkdb on one of my tables. It
> says it found a consistency error. What should I do? Can I run the
> dbcc checkdb <dbname>,repair_rebuild.
> Please advice.
> Regards
> Jaideep
>|||Hi,
Please do not execute CHECKDB with option repair_allow_data_loss directly.
1. Do a Full database backup
2. Then execute dbcc checkdb <dbname>,repair_rebuild.
3. See if the error is fixed. If the error is not fixed then go with
repair_allow_data_loss
Thanks
Hari
SQL Server MVP
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:%23e0A$GV0GHA.4808@.TK2MSFTNGP04.phx.gbl...
> You have some serious data corruption problems.
> Issue a DBCC CHECKDB('DatabaseName',repair_allow_data
_loss)
> If this does not fix the problem or cause important data to be lost you
> will have to restore the latest backup.
> Hopefully you will have a recent backup available you can restore from.
> --
> 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
>
> "jai" <dbasybase@.gmail.com> wrote in message
> news:1157504133.116486.17050@.d34g2000cwd.googlegroups.com...
>|||Hello,
Thanks Hari for your help. Actually, I was able to fix the problem
using DBCC UPDATEUSAGE. I don't know if dbcc checkdb would have solved
the row count error in the system views.
Regards
Jaideep
Hari Prasad wrote:[vbcol=seagreen]
> Hi,
> Please do not execute CHECKDB with option repair_allow_data_loss directly.
> 1. Do a Full database backup
> 2. Then execute dbcc checkdb <dbname>,repair_rebuild.
> 3. See if the error is fixed. If the error is not fixed then go with
> repair_allow_data_loss
> Thanks
> Hari
> SQL Server MVP
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:%23e0A$GV0GHA.4808@.TK2MSFTNGP04.phx.gbl...|||Hi,
Thanks for getting back with the update. Actually DBCC CHECKDB will report
the rewcount errors and need to use DBCC UPDATEUSAGE
to fix it. You did the right action.
Thanks
Hari
SQL Server MVP
"jai" <dbasybase@.gmail.com> wrote in message
news:1157639412.832187.165890@.d34g2000cwd.googlegroups.com...
> Hello,
> Thanks Hari for your help. Actually, I was able to fix the problem
> using DBCC UPDATEUSAGE. I don't know if dbcc checkdb would have solved
> the row count error in the system views.
> Regards
> Jaideep
> Hari Prasad wrote:
>