January 27, 2009 at 7:52 pm
Hi,
I have a question.
How to execute DBCC CheckDb command to remove the consistency errors found in msdb database.
Do we suppose to get the database in single user mode?
Pls reply with the steps......
January 27, 2009 at 9:20 pm
Hi,
Using arguments like (REPAIR_ALLOW_DATA_LOSS | REPAIR_FAST| REPAIR_REBUILD), the CHECKDB errors can be repaired. (Check BOL for more info. as these options need to be used catiously. There may be loss of data with certain arguments)
[font="Verdana"]Renuka__[/font]
January 27, 2009 at 11:33 pm
shivayogigouda.patil (1/27/2009)
How to execute DBCC CheckDb command to remove the consistency errors found in msdb database.Do we suppose to get the database in single user mode?
The preferred way to fix most corruption problems is to restore a clean backup, not run the repair commands. Do you have a clean backup?
Can you post the full output of the following command please.
DBCC CHECKDB (< Database Name > ) WITH NO_INFOMSGS, ALL_ERRORMSGS
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
January 29, 2009 at 7:36 am
Renuka (1/27/2009)
Hi,Using arguments like (REPAIR_ALLOW_DATA_LOSS | REPAIR_FAST| REPAIR_REBUILD), the CHECKDB errors can be repaired. (Check BOL for more info. as these options need to be used catiously. There may be loss of data with certain arguments)
Auuuggghhhh! To expand on Gail's post, never, EVER are these the first course(s) of action. If a clean backup is not availabe (if not, why not?), you can try and get as much of the data as possible by exporting the data before attempting to repair with data loss. You never know what data you will lose which potentially can lead to bigger issues.
-- You can't be late until you show up.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply