DBCC Checkdb consistency Error on Production Database

Question

Post reply

DBCC Checkdb consistency Error on Production Database

rollercoaster43

Ten Centuries

Points: 1306
More actions
January 14, 2014 at 12:05 am

#287216

Hi All,
My production server details are :
Microsoft SQL Server 2005 - 9.00.5000.00 (X64)
Copyright (c) 1988-2005 Microsoft Corporation Enterprise Edition (64-bit)
on Windows NT 5.2 (Build 3790: Service Pack 2)
I have had a consistency error on one of my databases last week in a non clustered index on a table and I had dropped and recreated the non-clustered index to get rid of it.
Following the incident, I came across another cnsitency check error on the same table and I have attached a complete dump of the error.
Is repair_allow_data_loss the only option here? Do I have to take a downtime for this activity since this is a critical production database?
Thanks in advance..

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply

Gail Shaw SSC Guru Points: 1004504 More actions · Answer 1

Please run the following and post the full and complete, unedited output

DBCC CheckDB (<database name>) WITH NO_INFOMSGS, ALL_ERRORMSGS

Do you have a clean backup and an unbroken log chain from that clean backup?

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Perry Whittle SSC Guru Points: 234013 More actions · Answer 2

Doesnt look good for that table, as Gail said do you have a clean backup and unbroken log chain. If not, why not 😉

-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs" 😉

enriquemallon Ten Centuries Points: 1239 More actions · Answer 3

You can eradicate SQL database consistency error go to replication folder of the object explorer and right click on it then select Launch Replication monitor. Then Launch Repl Monitor->My Publisher->NCFM and make a right click on it the n again select agent profile.When the Agent Profiles window is displayed, make sure the "Distribution Agents" page is selected. Then in the Agent profiles section, click and select the "Default for New" checkbox for "Continue on data consistency errors". You can click on the ellipsis button next to this profile, to view its parameters. The properties dialog box will open, and if you scroll down a bit, you will see the -SkipErrors Parameter, as highlighted below:Finally, click , and then to set the new default profile for the Distribution Agent.:-)

MalD Old Hand Points: 366 More actions · Answer 4

enriquemallon (7/31/2014)
You can eradicate SQL database consistency error go to replication folder of the object explorer and right click on it then select Launch Replication monitor. Then Launch Repl Monitor->My Publisher->NCFM and make a right click on it the n again select agent profile.When the Agent Profiles window is displayed, make sure the "Distribution Agents" page is selected. Then in the Agent profiles section, click and select the "Default for New" checkbox for "Continue on data consistency errors". You can click on the ellipsis button next to this profile, to view its parameters. The properties dialog box will open, and if you scroll down a bit, you will see the -SkipErrors Parameter, as highlighted below:Finally, click , and then to set the new default profile for the Distribution Agent.:-)

Scary :ermm: ! It doesn't even make sense.