Re: Clean checkdb & checkcatalog - why is "Attempt to repair any minor problems" kicking in ?

From: Paul S Randal [MS] (prandal_at_online.microsoft.com)
Date: 06/18/04 

Date: Thu, 17 Jun 2004 20:51:16 -0700

Tibor, you mean REPAIR_FAST.

The command has to run in single_user mode and the maintenance job is
failing because of that. You shouldn't use that option and I've ensured its
been removed in SQL Server 2005.

Thanks 

-- 
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Tibor Karaszi" <tibor_please.no.email_karaszi@hotmail.nomail.com> wrote in
message news:OBWpvLDVEHA.2544@TK2MSFTNGP10.phx.gbl...
> Seems like you assume that maint wiz first run DBCC CHECKDB without the
repair option and if it find
> a problem, it run again, using FAST_REPAIR. It doesn't. It just runs the
command once, using the
> FAST_REPAIR option. IMO, exposing this option in a wizard-like tool is bad
design...
>
> -- 
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
>
> "zoranlee" <zoranlee@hotmail.com> wrote in message
> news:3842add9.0406161549.585ece6e@posting.google.com...
> > A client was complaining that their DB Maint. plans ( on a server set
> > up by them )started failing.
> >
> > Checked it out and once I turned the "Attempt to repair any minor
> > problems" off it was OK. I understand this is a known problem.
> >
> > I never turn this option on myself so I am not familiar with it.
> > Integrity check should be running an DBCC CHECKDB, right?
> > So this option would probably be the equivalent of the REPAIR_FAST
> > option.
> >
> > I did a dbcc checkdb and checkcatalog manually and both were clean.
> >
> > Why is "auto repair" kicking in if everything is OK?
> > or
> > If there is a problem to fix why is it not showing up in DBCC?
> >
> > Any suggestions?
> >
> > Thanks
> >
> > Z
>
>

Relevant Pages
Loading