check sql licence: checkdb

Showing posts with label checkdb. Show all posts

Sunday, March 25, 2012

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

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
ZSeems 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|||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
>|||> Tibor, you mean REPAIR_FAST.
Indeed. Thanks for catching that.
> and I've ensured its
> been removed in SQL Server 2005.
I'm happy to hear that! :-)
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Paul S Randal [MS]" <prandal@.online.microsoft.com> wrote in message
news:%233rYvdOVEHA.3420@.TK2MSFTNGP12.phx.gbl...
> 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
> >
> >
>

Tuesday, February 14, 2012

Checkdb vs Integrity with indexes

Is there a difference running checkdb -DBCC checkdb ('database') and running
the Integrity with Indexes option of a maintenance plan? The checkdb output
shows detail while the integrity output shows almost no detail.
Thanks
RonWhat about if you manually run DBCC CHECKDB ('database') WITH NO_INFOMSGS?
Do the outputs match then?
--
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Ron" <Ron@.discussions.microsoft.com> wrote in message
news:9E360D8A-D225-45C8-A5F7-D8671E46F417@.microsoft.com...
> Is there a difference running checkdb -DBCC checkdb ('database') and
running
> the Integrity with Indexes option of a maintenance plan? The checkdb
output
> shows detail while the integrity output shows almost no detail.
> Thanks
> Ron|||No different results.
Because the Integrity with Indexes via the maintenance plan produces
different output than a DBCC checkdb database, I wanted to know if both are
doing the same thing.
I'm thinking of replacing the integrity with a DBCC checkdb, but would like
to know what's the difference between the two besides the output.
"Paul S Randal [MS]" wrote:
> What about if you manually run DBCC CHECKDB ('database') WITH NO_INFOMSGS?
> Do the outputs match then?
> --
> Paul Randal
> Dev Lead, Microsoft SQL Server Storage Engine
> This posting is provided "AS IS" with no warranties, and confers no rights.
> "Ron" <Ron@.discussions.microsoft.com> wrote in message
> news:9E360D8A-D225-45C8-A5F7-D8671E46F417@.microsoft.com...
> > Is there a difference running checkdb -DBCC checkdb ('database') and
> running
> > the Integrity with Indexes option of a maintenance plan? The checkdb
> output
> > shows detail while the integrity output shows almost no detail.
> >
> > Thanks
> >
> > Ron
>
>|||Can you post the output? As far as I'm aware, the integrity check runs DBCC
CHECKDB.
--
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Ron" <Ron@.discussions.microsoft.com> wrote in message
news:03075079-DA30-47EE-9550-E792A8E4EB1D@.microsoft.com...
> No different results.
> Because the Integrity with Indexes via the maintenance plan produces
> different output than a DBCC checkdb database, I wanted to know if both
are
> doing the same thing.
> I'm thinking of replacing the integrity with a DBCC checkdb, but would
like
> to know what's the difference between the two besides the output.
> "Paul S Randal [MS]" wrote:
> > What about if you manually run DBCC CHECKDB ('database') WITH
NO_INFOMSGS?
> > Do the outputs match then?
> >
> > --
> > Paul Randal
> > Dev Lead, Microsoft SQL Server Storage Engine
> >
> > This posting is provided "AS IS" with no warranties, and confers no
rights.
> >
> > "Ron" <Ron@.discussions.microsoft.com> wrote in message
> > news:9E360D8A-D225-45C8-A5F7-D8671E46F417@.microsoft.com...
> > > Is there a difference running checkdb -DBCC checkdb ('database') and
> > running
> > > the Integrity with Indexes option of a maintenance plan? The checkdb
> > output
> > > shows detail while the integrity output shows almost no detail.
> > >
> > > Thanks
> > >
> > > Ron
> >
> >
> >|||Here the Integrity output:
1] Database ABCD: Check Data and Index Linkage...
(null)
(null)
** Execution Time: 0 hrs, 0 mins, 1 secs **
Here's the DBCC checkdb output :
Job 'DBCC checkdb' : Step 1, 'CheckDB Cinfo' : Began Executing 2005-02-13
04:00:00
DBCC results for 'Cinfo'. [SQLSTATE 01000]
DBCC results for 'sysobjects'. [SQLSTATE 01000]
There are 71 rows in 1 pages for object 'sysobjects'. [SQLSTATE 01000]
DBCC results for 'sysindexes'. [SQLSTATE 01000]
There are 125 rows in 5 pages for object 'sysindexes'. [SQLSTATE 01000]
DBCC results for 'syscolumns'. [SQLSTATE 01000]
There are 514 rows in 9 pages for object 'syscolumns'. [SQLSTATE 01000]
DBCC results for 'systypes'. [SQLSTATE 01000]
There are 26 rows in 1 pages for object 'systypes'. [SQLSTATE 01000]
DBCC results for 'syscomments'. [SQLSTATE 01000]
There are 113 rows in 10 pages for object 'syscomments'. [SQLSTATE 01000]
DBCC results for 'sysfiles1'. [SQLSTATE 01000]
There are 2 rows in 1 pages for object 'sysfiles1'. [SQLSTATE 01000]
DBCC results for 'syspermissions'. [SQLSTATE 01000]
There are 37 rows in 1 pages for object 'syspermissions'. [SQLSTATE 01000]
DBCC results for 'sysusers'. [SQLSTATE 01000]
There are 17 rows in 1 pages for object 'sysusers'. [SQLSTATE 01000]
DBCC results for 'sysproperties'. [SQLSTATE 01000]
There are 0 rows in 0 pages for object 'sysproperties'. [SQLSTATE 01000]
DBCC results for 'sysdepends'. [SQLSTATE 01000]
There are 422 rows in 2 pages for object 'sysdepends'. [SQLSTATE 01000]
DBCC results for 'sysreferences'. [SQLSTATE 01000]
There are 0 rows in 1 pages for object 'sysreferences'. [SQLSTATE 01000]
DBCC results for 'sysfulltextcatalogs'. [SQLSTATE 01000]
There are 0 rows in 1 pages for object 'sysfulltextcatalogs'. [SQLSTATE 01000]
DBCC results for 'sysfulltextnotify'. [SQLSTATE 01000]
There are 0 rows in 0 pages for object 'sysfulltextnotify'. [SQLSTATE 01000]
DBCC results for 'sysfilegroups'. [SQLSTATE 01000]
There are 1 rows in 1 pages for object 'sysfilegroups'. [SQLSTATE 01000]
DBCC results for 'cinfo.CI_APS'. [SQLSTATE 01000]
There are 1 rows in 1 pages for object 'cinfo.CI_APS'. [SQLSTATE 01000]
DBCC results for 'cinfo.CI_AUDITTRACE'. [SQLSTATE 01000]
There are 0 rows in 1 pages for object 'cinfo.CI_AUDITTRACE'. [SQLSTATE 01000]
DBCC results for 'cinfo.CI_CLSMACHINES'. [SQLSTATE 01000]
There are 2 rows in 1 pages for object 'cinfo.CI_CLSMACHINES'. [SQLSTATE
01000]
DBCC results for 'cinfo.CI_EVENTS'. [SQLSTATE 01000]
There are 2 rows in 1 pages for object 'cinfo.CI_EVENTS'. [SQLSTATE 01000]
DBCC results for 'cinfo.CI_GOVINFO'. [SQLSTATE 01000]
There are 0 rows in 1 pages for object 'cinfo.CI_GOVINFO'. [SQLSTATE 01000]
DBCC results for 'cinfo.CI_GRPINFO'. [SQLSTATE 01000]
There are 7 rows in 2 pages for object 'cinfo.CI_GRPINFO'. [SQLSTATE 01000]
DBCC results for 'cinfo.CI_GRPUSERS'. [SQLSTATE 01000]
There are 106 rows in 2 pages for object 'cinfo.CI_GRPUSERS'. [SQLSTATE 01000]
DBCC results for 'cinfo.CI_HISTORY'. [SQLSTATE 01000]
There are 0 rows in 1 pages for object 'cinfo.CI_HISTORY'. [SQLSTATE 01000]
DBCC results for 'cinfo.CI_INFOOBJECTS'. [SQLSTATE 01000]
There are 589 rows in 22 pages for object 'cinfo.CI_INFOOBJECTS'. [SQLSTATE
01000]
DBCC results for 'cinfo.CI_ISPLUGINS'. [SQLSTATE 01000]
There are 0 rows in 1 pages for object 'cinfo.CI_ISPLUGINS'. [SQLSTATE 01000]
DBCC results for 'cinfo.CI_MACHAVAIL'. [SQLSTATE 01000]
There are 0 rows in 1 pages for object 'cinfo.CI_MACHAVAIL'. [SQLSTATE 01000]
DBCC results for 'cinfo.CI_MACHINECLASS'. [SQLSTATE 01000]
There are 0 rows in 1 pages for object 'cinfo.CI_MACHINECLASS'. [SQLSTATE
01000]
DBCC results for 'cinfo.CI_MACHINEGROUP'. [SQLSTATE 01000]
There are 2 rows in 1 pages for object 'cinfo.CI_MACHINEGROUP'. [SQLSTATE
01000]
DBCC results for 'cinfo.CI_MACHINV'. [SQLSTATE 01000]
There are 2 rows in 1 pages for object 'cinfo.CI_MACHINV'. [SQLSTATE 01000]
DBCC results for 'cinfo.CI_NEXTID'. [SQLSTATE 01000]
There are 1 rows in 1 pages for object 'cinfo.CI_NEXTID'. [SQLSTATE 01000]
DBCC results for 'cinfo.CI_RESTRICTIONS'. [SQLSTATE 01000]
There are 0 rows in 1 pages for object 'cinfo.CI_RESTRICTIONS'. [SQLSTATE
01000]
DBCC results for 'cinfo.CI_RIGHTROLES'. [SQLSTATE 01000]
There are 145 rows in 1 pages for object 'cinfo.CI_RIGHTROLES'. [SQLSTATE
01000]
DBCC results for 'cinfo.CI_RUNTIMEIMAGE'. [SQLSTATE 01000]
There are 2080 rows in 101 pages for object 'cinfo.CI_RUNTIMEIMAGE'.
[SQLSTATE 01000]
DBCC results for 'cinfo.CI_SCHEDULES'. [SQLSTATE 01000]
There are 0 rows in 1 pages for object 'cinfo.CI_SCHEDULES'. [SQLSTATE 01000]
DBCC results for 'cinfo.CI_SECRIGHTS'. [SQLSTATE 01000]
There are 1397 rows in 12 pages for object 'cinfo.CI_SECRIGHTS'. [SQLSTATE
01000]
DBCC results for 'cinfo.CI_SPECIALDATES'. [SQLSTATE 01000]
There are 0 rows in 1 pages for object 'cinfo.CI_SPECIALDATES'. [SQLSTATE
01000]
DBCC results for 'cinfo.CI_SPECIALDAYS'. [SQLSTATE 01000]
There are 0 rows in 1 pages for object 'cinfo.CI_SPECIALDAYS'. [SQLSTATE
01000]
DBCC results for 'cinfo.CI_TEMPLATEDATES'. [SQLSTATE 01000]
There are 458 rows in 4 pages for object 'cinfo.CI_TEMPLATEDATES'. [SQLSTATE
01000]
DBCC results for 'cinfo.CI_TEMPLATEDAYS'. [SQLSTATE 01000]
There are 143 rows in 1 pages for object 'cinfo.CI_TEMPLATEDAYS'. [SQLSTATE
01000]
DBCC results for 'cinfo.CI_TEMPLATES'. [SQLSTATE 01000]
There are 9 rows in 1 pages for object 'cinfo.CI_TEMPLATES'. [SQLSTATE 01000]
DBCC results for 'cinfo.CI_TIMEINFO'. [SQLSTATE 01000]
There are 0 rows in 1 pages for object 'cinfo.CI_TIMEINFO'. [SQLSTATE 01000]
DBCC results for 'cinfo.CI_USERS'. [SQLSTATE 01000]
There are 51 rows in 5 pages for object 'cinfo.CI_USERS'. [SQLSTATE 01000]
DBCC results for 'cinfo.CI_CHANNEL_INFO'. [SQLSTATE 01000]
There are 0 rows in 1 pages for object 'cinfo.CI_CHANNEL_INFO'. [SQLSTATE
01000]
DBCC results for 'cinfo.CI_ARCHIVEDOBJECTS'. [SQLSTATE 01000]
There are 0 rows in 1 pages for object 'cinfo.CI_ARCHIVEDOBJECTS'. [SQLSTATE
01000]
DBCC results for 'dtproperties'. [SQLSTATE 01000]
There are 0 rows in 1 pages for object 'dtproperties'. [SQLSTATE 01000]
CHECKDB found 0 allocation errors and 0 consistency errors in database
'cinfo'. [SQLSTATE 01000]
DBCC execution completed. If DBCC printed error messages, contact your
system administrator. [SQLSTATE 01000]
"Paul S Randal [MS]" wrote:
> Can you post the output? As far as I'm aware, the integrity check runs DBCC
> CHECKDB.
> --
> Paul Randal
> Dev Lead, Microsoft SQL Server Storage Engine
> This posting is provided "AS IS" with no warranties, and confers no rights.
> "Ron" <Ron@.discussions.microsoft.com> wrote in message
> news:03075079-DA30-47EE-9550-E792A8E4EB1D@.microsoft.com...
> > No different results.
> >
> > Because the Integrity with Indexes via the maintenance plan produces
> > different output than a DBCC checkdb database, I wanted to know if both
> are
> > doing the same thing.
> >
> > I'm thinking of replacing the integrity with a DBCC checkdb, but would
> like
> > to know what's the difference between the two besides the output.
> >
> > "Paul S Randal [MS]" wrote:
> >
> > > What about if you manually run DBCC CHECKDB ('database') WITH
> NO_INFOMSGS?
> > > Do the outputs match then?
> > >
> > > --
> > > Paul Randal
> > > Dev Lead, Microsoft SQL Server Storage Engine
> > >
> > > This posting is provided "AS IS" with no warranties, and confers no
> rights.
> > >
> > > "Ron" <Ron@.discussions.microsoft.com> wrote in message
> > > news:9E360D8A-D225-45C8-A5F7-D8671E46F417@.microsoft.com...
> > > > Is there a difference running checkdb -DBCC checkdb ('database') and
> > > running
> > > > the Integrity with Indexes option of a maintenance plan? The checkdb
> > > output
> > > > shows detail while the integrity output shows almost no detail.
> > > >
> > > > Thanks
> > > >
> > > > Ron
> > >
> > >
> > >
>
>|||Seems like maint wiz doesn't add WITH NO_INFOMSGS to the DBCC commend...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"Ron" <Ron@.discussions.microsoft.com> wrote in message
news:57E3528C-7953-47CE-BB5B-19C35199C094@.microsoft.com...
> Here the Integrity output:
> 1] Database ABCD: Check Data and Index Linkage...
>
> (null)
> (null)
> ** Execution Time: 0 hrs, 0 mins, 1 secs **
> Here's the DBCC checkdb output :
> Job 'DBCC checkdb' : Step 1, 'CheckDB Cinfo' : Began Executing 2005-02-13
> 04:00:00
> DBCC results for 'Cinfo'. [SQLSTATE 01000]
> DBCC results for 'sysobjects'. [SQLSTATE 01000]
> There are 71 rows in 1 pages for object 'sysobjects'. [SQLSTATE 01000]
> DBCC results for 'sysindexes'. [SQLSTATE 01000]
> There are 125 rows in 5 pages for object 'sysindexes'. [SQLSTATE 01000]
> DBCC results for 'syscolumns'. [SQLSTATE 01000]
> There are 514 rows in 9 pages for object 'syscolumns'. [SQLSTATE 01000]
> DBCC results for 'systypes'. [SQLSTATE 01000]
> There are 26 rows in 1 pages for object 'systypes'. [SQLSTATE 01000]
> DBCC results for 'syscomments'. [SQLSTATE 01000]
> There are 113 rows in 10 pages for object 'syscomments'. [SQLSTATE 01000]
> DBCC results for 'sysfiles1'. [SQLSTATE 01000]
> There are 2 rows in 1 pages for object 'sysfiles1'. [SQLSTATE 01000]
> DBCC results for 'syspermissions'. [SQLSTATE 01000]
> There are 37 rows in 1 pages for object 'syspermissions'. [SQLSTATE 01000]
> DBCC results for 'sysusers'. [SQLSTATE 01000]
> There are 17 rows in 1 pages for object 'sysusers'. [SQLSTATE 01000]
> DBCC results for 'sysproperties'. [SQLSTATE 01000]
> There are 0 rows in 0 pages for object 'sysproperties'. [SQLSTATE 01000]
> DBCC results for 'sysdepends'. [SQLSTATE 01000]
> There are 422 rows in 2 pages for object 'sysdepends'. [SQLSTATE 01000]
> DBCC results for 'sysreferences'. [SQLSTATE 01000]
> There are 0 rows in 1 pages for object 'sysreferences'. [SQLSTATE 01000]
> DBCC results for 'sysfulltextcatalogs'. [SQLSTATE 01000]
> There are 0 rows in 1 pages for object 'sysfulltextcatalogs'. [SQLSTATE 01000]
> DBCC results for 'sysfulltextnotify'. [SQLSTATE 01000]
> There are 0 rows in 0 pages for object 'sysfulltextnotify'. [SQLSTATE 01000]
> DBCC results for 'sysfilegroups'. [SQLSTATE 01000]
> There are 1 rows in 1 pages for object 'sysfilegroups'. [SQLSTATE 01000]
> DBCC results for 'cinfo.CI_APS'. [SQLSTATE 01000]
> There are 1 rows in 1 pages for object 'cinfo.CI_APS'. [SQLSTATE 01000]
> DBCC results for 'cinfo.CI_AUDITTRACE'. [SQLSTATE 01000]
> There are 0 rows in 1 pages for object 'cinfo.CI_AUDITTRACE'. [SQLSTATE 01000]
> DBCC results for 'cinfo.CI_CLSMACHINES'. [SQLSTATE 01000]
> There are 2 rows in 1 pages for object 'cinfo.CI_CLSMACHINES'. [SQLSTATE
> 01000]
> DBCC results for 'cinfo.CI_EVENTS'. [SQLSTATE 01000]
> There are 2 rows in 1 pages for object 'cinfo.CI_EVENTS'. [SQLSTATE 01000]
> DBCC results for 'cinfo.CI_GOVINFO'. [SQLSTATE 01000]
> There are 0 rows in 1 pages for object 'cinfo.CI_GOVINFO'. [SQLSTATE 01000]
> DBCC results for 'cinfo.CI_GRPINFO'. [SQLSTATE 01000]
> There are 7 rows in 2 pages for object 'cinfo.CI_GRPINFO'. [SQLSTATE 01000]
> DBCC results for 'cinfo.CI_GRPUSERS'. [SQLSTATE 01000]
> There are 106 rows in 2 pages for object 'cinfo.CI_GRPUSERS'. [SQLSTATE 01000]
> DBCC results for 'cinfo.CI_HISTORY'. [SQLSTATE 01000]
> There are 0 rows in 1 pages for object 'cinfo.CI_HISTORY'. [SQLSTATE 01000]
> DBCC results for 'cinfo.CI_INFOOBJECTS'. [SQLSTATE 01000]
> There are 589 rows in 22 pages for object 'cinfo.CI_INFOOBJECTS'. [SQLSTATE
> 01000]
> DBCC results for 'cinfo.CI_ISPLUGINS'. [SQLSTATE 01000]
> There are 0 rows in 1 pages for object 'cinfo.CI_ISPLUGINS'. [SQLSTATE 01000]
> DBCC results for 'cinfo.CI_MACHAVAIL'. [SQLSTATE 01000]
> There are 0 rows in 1 pages for object 'cinfo.CI_MACHAVAIL'. [SQLSTATE 01000]
> DBCC results for 'cinfo.CI_MACHINECLASS'. [SQLSTATE 01000]
> There are 0 rows in 1 pages for object 'cinfo.CI_MACHINECLASS'. [SQLSTATE
> 01000]
> DBCC results for 'cinfo.CI_MACHINEGROUP'. [SQLSTATE 01000]
> There are 2 rows in 1 pages for object 'cinfo.CI_MACHINEGROUP'. [SQLSTATE
> 01000]
> DBCC results for 'cinfo.CI_MACHINV'. [SQLSTATE 01000]
> There are 2 rows in 1 pages for object 'cinfo.CI_MACHINV'. [SQLSTATE 01000]
> DBCC results for 'cinfo.CI_NEXTID'. [SQLSTATE 01000]
> There are 1 rows in 1 pages for object 'cinfo.CI_NEXTID'. [SQLSTATE 01000]
> DBCC results for 'cinfo.CI_RESTRICTIONS'. [SQLSTATE 01000]
> There are 0 rows in 1 pages for object 'cinfo.CI_RESTRICTIONS'. [SQLSTATE
> 01000]
> DBCC results for 'cinfo.CI_RIGHTROLES'. [SQLSTATE 01000]
> There are 145 rows in 1 pages for object 'cinfo.CI_RIGHTROLES'. [SQLSTATE
> 01000]
> DBCC results for 'cinfo.CI_RUNTIMEIMAGE'. [SQLSTATE 01000]
> There are 2080 rows in 101 pages for object 'cinfo.CI_RUNTIMEIMAGE'.
> [SQLSTATE 01000]
> DBCC results for 'cinfo.CI_SCHEDULES'. [SQLSTATE 01000]
> There are 0 rows in 1 pages for object 'cinfo.CI_SCHEDULES'. [SQLSTATE 01000]
> DBCC results for 'cinfo.CI_SECRIGHTS'. [SQLSTATE 01000]
> There are 1397 rows in 12 pages for object 'cinfo.CI_SECRIGHTS'. [SQLSTATE
> 01000]
> DBCC results for 'cinfo.CI_SPECIALDATES'. [SQLSTATE 01000]
> There are 0 rows in 1 pages for object 'cinfo.CI_SPECIALDATES'. [SQLSTATE
> 01000]
> DBCC results for 'cinfo.CI_SPECIALDAYS'. [SQLSTATE 01000]
> There are 0 rows in 1 pages for object 'cinfo.CI_SPECIALDAYS'. [SQLSTATE
> 01000]
> DBCC results for 'cinfo.CI_TEMPLATEDATES'. [SQLSTATE 01000]
> There are 458 rows in 4 pages for object 'cinfo.CI_TEMPLATEDATES'. [SQLSTATE
> 01000]
> DBCC results for 'cinfo.CI_TEMPLATEDAYS'. [SQLSTATE 01000]
> There are 143 rows in 1 pages for object 'cinfo.CI_TEMPLATEDAYS'. [SQLSTATE
> 01000]
> DBCC results for 'cinfo.CI_TEMPLATES'. [SQLSTATE 01000]
> There are 9 rows in 1 pages for object 'cinfo.CI_TEMPLATES'. [SQLSTATE 01000]
> DBCC results for 'cinfo.CI_TIMEINFO'. [SQLSTATE 01000]
> There are 0 rows in 1 pages for object 'cinfo.CI_TIMEINFO'. [SQLSTATE 01000]
> DBCC results for 'cinfo.CI_USERS'. [SQLSTATE 01000]
> There are 51 rows in 5 pages for object 'cinfo.CI_USERS'. [SQLSTATE 01000]
> DBCC results for 'cinfo.CI_CHANNEL_INFO'. [SQLSTATE 01000]
> There are 0 rows in 1 pages for object 'cinfo.CI_CHANNEL_INFO'. [SQLSTATE
> 01000]
> DBCC results for 'cinfo.CI_ARCHIVEDOBJECTS'. [SQLSTATE 01000]
> There are 0 rows in 1 pages for object 'cinfo.CI_ARCHIVEDOBJECTS'. [SQLSTATE
> 01000]
> DBCC results for 'dtproperties'. [SQLSTATE 01000]
> There are 0 rows in 1 pages for object 'dtproperties'. [SQLSTATE 01000]
> CHECKDB found 0 allocation errors and 0 consistency errors in database
> 'cinfo'. [SQLSTATE 01000]
> DBCC execution completed. If DBCC printed error messages, contact your
> system administrator. [SQLSTATE 01000]
>
> "Paul S Randal [MS]" wrote:
>> Can you post the output? As far as I'm aware, the integrity check runs DBCC
>> CHECKDB.
>> --
>> Paul Randal
>> Dev Lead, Microsoft SQL Server Storage Engine
>> This posting is provided "AS IS" with no warranties, and confers no rights.
>> "Ron" <Ron@.discussions.microsoft.com> wrote in message
>> news:03075079-DA30-47EE-9550-E792A8E4EB1D@.microsoft.com...
>> > No different results.
>> >
>> > Because the Integrity with Indexes via the maintenance plan produces
>> > different output than a DBCC checkdb database, I wanted to know if both
>> are
>> > doing the same thing.
>> >
>> > I'm thinking of replacing the integrity with a DBCC checkdb, but would
>> like
>> > to know what's the difference between the two besides the output.
>> >
>> > "Paul S Randal [MS]" wrote:
>> >
>> > > What about if you manually run DBCC CHECKDB ('database') WITH
>> NO_INFOMSGS?
>> > > Do the outputs match then?
>> > >
>> > > --
>> > > Paul Randal
>> > > Dev Lead, Microsoft SQL Server Storage Engine
>> > >
>> > > This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>> > >
>> > > "Ron" <Ron@.discussions.microsoft.com> wrote in message
>> > > news:9E360D8A-D225-45C8-A5F7-D8671E46F417@.microsoft.com...
>> > > > Is there a difference running checkdb -DBCC checkdb ('database') and
>> > > running
>> > > > the Integrity with Indexes option of a maintenance plan? The checkdb
>> > > output
>> > > > shows detail while the integrity output shows almost no detail.
>> > > >
>> > > > Thanks
>> > > >
>> > > > Ron
>> > >
>> > >
>> > >
>>|||I'm not sure I follow. When dbcc checkdb runs with NO_INFOMSGS it doesn't
look like the Integrity output.
I guess my question is simply "Does the Integrity (with indexes) job from
the maintenance plan do exactly what DBCC checkdb does?"
"Tibor Karaszi" wrote:
> Seems like maint wiz doesn't add WITH NO_INFOMSGS to the DBCC commend...
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> http://www.sqlug.se/
>
> "Ron" <Ron@.discussions.microsoft.com> wrote in message
> news:57E3528C-7953-47CE-BB5B-19C35199C094@.microsoft.com...
> > Here the Integrity output:
> > 1] Database ABCD: Check Data and Index Linkage...
> >
> >
> >
> > (null)
> > (null)
> > ** Execution Time: 0 hrs, 0 mins, 1 secs **
> >
> > Here's the DBCC checkdb output :
> > Job 'DBCC checkdb' : Step 1, 'CheckDB Cinfo' : Began Executing 2005-02-13
> > 04:00:00
> >
> > DBCC results for 'Cinfo'. [SQLSTATE 01000]
> > DBCC results for 'sysobjects'. [SQLSTATE 01000]
> > There are 71 rows in 1 pages for object 'sysobjects'. [SQLSTATE 01000]
> > DBCC results for 'sysindexes'. [SQLSTATE 01000]
> > There are 125 rows in 5 pages for object 'sysindexes'. [SQLSTATE 01000]
> > DBCC results for 'syscolumns'. [SQLSTATE 01000]
> > There are 514 rows in 9 pages for object 'syscolumns'. [SQLSTATE 01000]
> > DBCC results for 'systypes'. [SQLSTATE 01000]
> > There are 26 rows in 1 pages for object 'systypes'. [SQLSTATE 01000]
> > DBCC results for 'syscomments'. [SQLSTATE 01000]
> > There are 113 rows in 10 pages for object 'syscomments'. [SQLSTATE 01000]
> > DBCC results for 'sysfiles1'. [SQLSTATE 01000]
> > There are 2 rows in 1 pages for object 'sysfiles1'. [SQLSTATE 01000]
> > DBCC results for 'syspermissions'. [SQLSTATE 01000]
> > There are 37 rows in 1 pages for object 'syspermissions'. [SQLSTATE 01000]
> > DBCC results for 'sysusers'. [SQLSTATE 01000]
> > There are 17 rows in 1 pages for object 'sysusers'. [SQLSTATE 01000]
> > DBCC results for 'sysproperties'. [SQLSTATE 01000]
> > There are 0 rows in 0 pages for object 'sysproperties'. [SQLSTATE 01000]
> > DBCC results for 'sysdepends'. [SQLSTATE 01000]
> > There are 422 rows in 2 pages for object 'sysdepends'. [SQLSTATE 01000]
> > DBCC results for 'sysreferences'. [SQLSTATE 01000]
> > There are 0 rows in 1 pages for object 'sysreferences'. [SQLSTATE 01000]
> > DBCC results for 'sysfulltextcatalogs'. [SQLSTATE 01000]
> > There are 0 rows in 1 pages for object 'sysfulltextcatalogs'. [SQLSTATE 01000]
> > DBCC results for 'sysfulltextnotify'. [SQLSTATE 01000]
> > There are 0 rows in 0 pages for object 'sysfulltextnotify'. [SQLSTATE 01000]
> > DBCC results for 'sysfilegroups'. [SQLSTATE 01000]
> > There are 1 rows in 1 pages for object 'sysfilegroups'. [SQLSTATE 01000]
> > DBCC results for 'cinfo.CI_APS'. [SQLSTATE 01000]
> > There are 1 rows in 1 pages for object 'cinfo.CI_APS'. [SQLSTATE 01000]
> > DBCC results for 'cinfo.CI_AUDITTRACE'. [SQLSTATE 01000]
> > There are 0 rows in 1 pages for object 'cinfo.CI_AUDITTRACE'. [SQLSTATE 01000]
> > DBCC results for 'cinfo.CI_CLSMACHINES'. [SQLSTATE 01000]
> > There are 2 rows in 1 pages for object 'cinfo.CI_CLSMACHINES'. [SQLSTATE
> > 01000]
> > DBCC results for 'cinfo.CI_EVENTS'. [SQLSTATE 01000]
> > There are 2 rows in 1 pages for object 'cinfo.CI_EVENTS'. [SQLSTATE 01000]
> > DBCC results for 'cinfo.CI_GOVINFO'. [SQLSTATE 01000]
> > There are 0 rows in 1 pages for object 'cinfo.CI_GOVINFO'. [SQLSTATE 01000]
> > DBCC results for 'cinfo.CI_GRPINFO'. [SQLSTATE 01000]
> > There are 7 rows in 2 pages for object 'cinfo.CI_GRPINFO'. [SQLSTATE 01000]
> > DBCC results for 'cinfo.CI_GRPUSERS'. [SQLSTATE 01000]
> > There are 106 rows in 2 pages for object 'cinfo.CI_GRPUSERS'. [SQLSTATE 01000]
> > DBCC results for 'cinfo.CI_HISTORY'. [SQLSTATE 01000]
> > There are 0 rows in 1 pages for object 'cinfo.CI_HISTORY'. [SQLSTATE 01000]
> > DBCC results for 'cinfo.CI_INFOOBJECTS'. [SQLSTATE 01000]
> > There are 589 rows in 22 pages for object 'cinfo.CI_INFOOBJECTS'. [SQLSTATE
> > 01000]
> > DBCC results for 'cinfo.CI_ISPLUGINS'. [SQLSTATE 01000]
> > There are 0 rows in 1 pages for object 'cinfo.CI_ISPLUGINS'. [SQLSTATE 01000]
> > DBCC results for 'cinfo.CI_MACHAVAIL'. [SQLSTATE 01000]
> > There are 0 rows in 1 pages for object 'cinfo.CI_MACHAVAIL'. [SQLSTATE 01000]
> > DBCC results for 'cinfo.CI_MACHINECLASS'. [SQLSTATE 01000]
> > There are 0 rows in 1 pages for object 'cinfo.CI_MACHINECLASS'. [SQLSTATE
> > 01000]
> > DBCC results for 'cinfo.CI_MACHINEGROUP'. [SQLSTATE 01000]
> > There are 2 rows in 1 pages for object 'cinfo.CI_MACHINEGROUP'. [SQLSTATE
> > 01000]
> > DBCC results for 'cinfo.CI_MACHINV'. [SQLSTATE 01000]
> > There are 2 rows in 1 pages for object 'cinfo.CI_MACHINV'. [SQLSTATE 01000]
> > DBCC results for 'cinfo.CI_NEXTID'. [SQLSTATE 01000]
> > There are 1 rows in 1 pages for object 'cinfo.CI_NEXTID'. [SQLSTATE 01000]
> > DBCC results for 'cinfo.CI_RESTRICTIONS'. [SQLSTATE 01000]
> > There are 0 rows in 1 pages for object 'cinfo.CI_RESTRICTIONS'. [SQLSTATE
> > 01000]
> > DBCC results for 'cinfo.CI_RIGHTROLES'. [SQLSTATE 01000]
> > There are 145 rows in 1 pages for object 'cinfo.CI_RIGHTROLES'. [SQLSTATE
> > 01000]
> > DBCC results for 'cinfo.CI_RUNTIMEIMAGE'. [SQLSTATE 01000]
> > There are 2080 rows in 101 pages for object 'cinfo.CI_RUNTIMEIMAGE'.
> > [SQLSTATE 01000]
> > DBCC results for 'cinfo.CI_SCHEDULES'. [SQLSTATE 01000]
> > There are 0 rows in 1 pages for object 'cinfo.CI_SCHEDULES'. [SQLSTATE 01000]
> > DBCC results for 'cinfo.CI_SECRIGHTS'. [SQLSTATE 01000]
> > There are 1397 rows in 12 pages for object 'cinfo.CI_SECRIGHTS'. [SQLSTATE
> > 01000]
> > DBCC results for 'cinfo.CI_SPECIALDATES'. [SQLSTATE 01000]
> > There are 0 rows in 1 pages for object 'cinfo.CI_SPECIALDATES'. [SQLSTATE
> > 01000]
> > DBCC results for 'cinfo.CI_SPECIALDAYS'. [SQLSTATE 01000]
> > There are 0 rows in 1 pages for object 'cinfo.CI_SPECIALDAYS'. [SQLSTATE
> > 01000]
> > DBCC results for 'cinfo.CI_TEMPLATEDATES'. [SQLSTATE 01000]
> > There are 458 rows in 4 pages for object 'cinfo.CI_TEMPLATEDATES'. [SQLSTATE
> > 01000]
> > DBCC results for 'cinfo.CI_TEMPLATEDAYS'. [SQLSTATE 01000]
> > There are 143 rows in 1 pages for object 'cinfo.CI_TEMPLATEDAYS'. [SQLSTATE
> > 01000]
> > DBCC results for 'cinfo.CI_TEMPLATES'. [SQLSTATE 01000]
> > There are 9 rows in 1 pages for object 'cinfo.CI_TEMPLATES'. [SQLSTATE 01000]
> > DBCC results for 'cinfo.CI_TIMEINFO'. [SQLSTATE 01000]
> > There are 0 rows in 1 pages for object 'cinfo.CI_TIMEINFO'. [SQLSTATE 01000]
> > DBCC results for 'cinfo.CI_USERS'. [SQLSTATE 01000]
> > There are 51 rows in 5 pages for object 'cinfo.CI_USERS'. [SQLSTATE 01000]
> > DBCC results for 'cinfo.CI_CHANNEL_INFO'. [SQLSTATE 01000]
> > There are 0 rows in 1 pages for object 'cinfo.CI_CHANNEL_INFO'. [SQLSTATE
> > 01000]
> > DBCC results for 'cinfo.CI_ARCHIVEDOBJECTS'. [SQLSTATE 01000]
> > There are 0 rows in 1 pages for object 'cinfo.CI_ARCHIVEDOBJECTS'. [SQLSTATE
> > 01000]
> > DBCC results for 'dtproperties'. [SQLSTATE 01000]
> > There are 0 rows in 1 pages for object 'dtproperties'. [SQLSTATE 01000]
> > CHECKDB found 0 allocation errors and 0 consistency errors in database
> > 'cinfo'. [SQLSTATE 01000]
> > DBCC execution completed. If DBCC printed error messages, contact your
> > system administrator. [SQLSTATE 01000]
> >
> >
> > "Paul S Randal [MS]" wrote:
> >
> >> Can you post the output? As far as I'm aware, the integrity check runs DBCC
> >> CHECKDB.
> >>
> >> --
> >> Paul Randal
> >> Dev Lead, Microsoft SQL Server Storage Engine
> >>
> >> This posting is provided "AS IS" with no warranties, and confers no rights.
> >>
> >> "Ron" <Ron@.discussions.microsoft.com> wrote in message
> >> news:03075079-DA30-47EE-9550-E792A8E4EB1D@.microsoft.com...
> >> > No different results.
> >> >
> >> > Because the Integrity with Indexes via the maintenance plan produces
> >> > different output than a DBCC checkdb database, I wanted to know if both
> >> are
> >> > doing the same thing.
> >> >
> >> > I'm thinking of replacing the integrity with a DBCC checkdb, but would
> >> like
> >> > to know what's the difference between the two besides the output.
> >> >
> >> > "Paul S Randal [MS]" wrote:
> >> >
> >> > > What about if you manually run DBCC CHECKDB ('database') WITH
> >> NO_INFOMSGS?
> >> > > Do the outputs match then?
> >> > >
> >> > > --
> >> > > Paul Randal
> >> > > Dev Lead, Microsoft SQL Server Storage Engine
> >> > >
> >> > > This posting is provided "AS IS" with no warranties, and confers no
> >> rights.
> >> > >
> >> > > "Ron" <Ron@.discussions.microsoft.com> wrote in message
> >> > > news:9E360D8A-D225-45C8-A5F7-D8671E46F417@.microsoft.com...
> >> > > > Is there a difference running checkdb -DBCC checkdb ('database') and
> >> > > running
> >> > > > the Integrity with Indexes option of a maintenance plan? The checkdb
> >> > > output
> >> > > > shows detail while the integrity output shows almost no detail.
> >> > > >
> >> > > > Thanks
> >> > > >
> >> > > > Ron
> >> > >
> >> > >
> >> > >
> >>
> >>
> >>
>
>|||> I guess my question is simply "Does the Integrity (with indexes) job from
> the maintenance plan do exactly what DBCC checkdb does?"
All the maintenance wizard does is execute SQL commands. I ran a profiler trace to capture the
command executed by the maintenance wizard:
dbcc checkdb WITH NO_INFOMSGS
If you are curious, you can use profiler while the maint wizard is executing to capture the commands
that it executing against SQL Server.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Ron" <Ron@.discussions.microsoft.com> wrote in message
news:A051C9CE-671A-46FF-BD75-DAE4A408B081@.microsoft.com...
> I'm not sure I follow. When dbcc checkdb runs with NO_INFOMSGS it doesn't
> look like the Integrity output.
> I guess my question is simply "Does the Integrity (with indexes) job from
> the maintenance plan do exactly what DBCC checkdb does?"
> "Tibor Karaszi" wrote:
>> Seems like maint wiz doesn't add WITH NO_INFOMSGS to the DBCC commend...
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>> http://www.sqlug.se/
>>
>> "Ron" <Ron@.discussions.microsoft.com> wrote in message
>> news:57E3528C-7953-47CE-BB5B-19C35199C094@.microsoft.com...
>> > Here the Integrity output:
>> > 1] Database ABCD: Check Data and Index Linkage...
>> >
>> >
>> >
>> > (null)
>> > (null)
>> > ** Execution Time: 0 hrs, 0 mins, 1 secs **
>> >
>> > Here's the DBCC checkdb output :
>> > Job 'DBCC checkdb' : Step 1, 'CheckDB Cinfo' : Began Executing 2005-02-13
>> > 04:00:00
>> >
>> > DBCC results for 'Cinfo'. [SQLSTATE 01000]
>> > DBCC results for 'sysobjects'. [SQLSTATE 01000]
>> > There are 71 rows in 1 pages for object 'sysobjects'. [SQLSTATE 01000]
>> > DBCC results for 'sysindexes'. [SQLSTATE 01000]
>> > There are 125 rows in 5 pages for object 'sysindexes'. [SQLSTATE 01000]
>> > DBCC results for 'syscolumns'. [SQLSTATE 01000]
>> > There are 514 rows in 9 pages for object 'syscolumns'. [SQLSTATE 01000]
>> > DBCC results for 'systypes'. [SQLSTATE 01000]
>> > There are 26 rows in 1 pages for object 'systypes'. [SQLSTATE 01000]
>> > DBCC results for 'syscomments'. [SQLSTATE 01000]
>> > There are 113 rows in 10 pages for object 'syscomments'. [SQLSTATE 01000]
>> > DBCC results for 'sysfiles1'. [SQLSTATE 01000]
>> > There are 2 rows in 1 pages for object 'sysfiles1'. [SQLSTATE 01000]
>> > DBCC results for 'syspermissions'. [SQLSTATE 01000]
>> > There are 37 rows in 1 pages for object 'syspermissions'. [SQLSTATE 01000]
>> > DBCC results for 'sysusers'. [SQLSTATE 01000]
>> > There are 17 rows in 1 pages for object 'sysusers'. [SQLSTATE 01000]
>> > DBCC results for 'sysproperties'. [SQLSTATE 01000]
>> > There are 0 rows in 0 pages for object 'sysproperties'. [SQLSTATE 01000]
>> > DBCC results for 'sysdepends'. [SQLSTATE 01000]
>> > There are 422 rows in 2 pages for object 'sysdepends'. [SQLSTATE 01000]
>> > DBCC results for 'sysreferences'. [SQLSTATE 01000]
>> > There are 0 rows in 1 pages for object 'sysreferences'. [SQLSTATE 01000]
>> > DBCC results for 'sysfulltextcatalogs'. [SQLSTATE 01000]
>> > There are 0 rows in 1 pages for object 'sysfulltextcatalogs'. [SQLSTATE 01000]
>> > DBCC results for 'sysfulltextnotify'. [SQLSTATE 01000]
>> > There are 0 rows in 0 pages for object 'sysfulltextnotify'. [SQLSTATE 01000]
>> > DBCC results for 'sysfilegroups'. [SQLSTATE 01000]
>> > There are 1 rows in 1 pages for object 'sysfilegroups'. [SQLSTATE 01000]
>> > DBCC results for 'cinfo.CI_APS'. [SQLSTATE 01000]
>> > There are 1 rows in 1 pages for object 'cinfo.CI_APS'. [SQLSTATE 01000]
>> > DBCC results for 'cinfo.CI_AUDITTRACE'. [SQLSTATE 01000]
>> > There are 0 rows in 1 pages for object 'cinfo.CI_AUDITTRACE'. [SQLSTATE 01000]
>> > DBCC results for 'cinfo.CI_CLSMACHINES'. [SQLSTATE 01000]
>> > There are 2 rows in 1 pages for object 'cinfo.CI_CLSMACHINES'. [SQLSTATE
>> > 01000]
>> > DBCC results for 'cinfo.CI_EVENTS'. [SQLSTATE 01000]
>> > There are 2 rows in 1 pages for object 'cinfo.CI_EVENTS'. [SQLSTATE 01000]
>> > DBCC results for 'cinfo.CI_GOVINFO'. [SQLSTATE 01000]
>> > There are 0 rows in 1 pages for object 'cinfo.CI_GOVINFO'. [SQLSTATE 01000]
>> > DBCC results for 'cinfo.CI_GRPINFO'. [SQLSTATE 01000]
>> > There are 7 rows in 2 pages for object 'cinfo.CI_GRPINFO'. [SQLSTATE 01000]
>> > DBCC results for 'cinfo.CI_GRPUSERS'. [SQLSTATE 01000]
>> > There are 106 rows in 2 pages for object 'cinfo.CI_GRPUSERS'. [SQLSTATE 01000]
>> > DBCC results for 'cinfo.CI_HISTORY'. [SQLSTATE 01000]
>> > There are 0 rows in 1 pages for object 'cinfo.CI_HISTORY'. [SQLSTATE 01000]
>> > DBCC results for 'cinfo.CI_INFOOBJECTS'. [SQLSTATE 01000]
>> > There are 589 rows in 22 pages for object 'cinfo.CI_INFOOBJECTS'. [SQLSTATE
>> > 01000]
>> > DBCC results for 'cinfo.CI_ISPLUGINS'. [SQLSTATE 01000]
>> > There are 0 rows in 1 pages for object 'cinfo.CI_ISPLUGINS'. [SQLSTATE 01000]
>> > DBCC results for 'cinfo.CI_MACHAVAIL'. [SQLSTATE 01000]
>> > There are 0 rows in 1 pages for object 'cinfo.CI_MACHAVAIL'. [SQLSTATE 01000]
>> > DBCC results for 'cinfo.CI_MACHINECLASS'. [SQLSTATE 01000]
>> > There are 0 rows in 1 pages for object 'cinfo.CI_MACHINECLASS'. [SQLSTATE
>> > 01000]
>> > DBCC results for 'cinfo.CI_MACHINEGROUP'. [SQLSTATE 01000]
>> > There are 2 rows in 1 pages for object 'cinfo.CI_MACHINEGROUP'. [SQLSTATE
>> > 01000]
>> > DBCC results for 'cinfo.CI_MACHINV'. [SQLSTATE 01000]
>> > There are 2 rows in 1 pages for object 'cinfo.CI_MACHINV'. [SQLSTATE 01000]
>> > DBCC results for 'cinfo.CI_NEXTID'. [SQLSTATE 01000]
>> > There are 1 rows in 1 pages for object 'cinfo.CI_NEXTID'. [SQLSTATE 01000]
>> > DBCC results for 'cinfo.CI_RESTRICTIONS'. [SQLSTATE 01000]
>> > There are 0 rows in 1 pages for object 'cinfo.CI_RESTRICTIONS'. [SQLSTATE
>> > 01000]
>> > DBCC results for 'cinfo.CI_RIGHTROLES'. [SQLSTATE 01000]
>> > There are 145 rows in 1 pages for object 'cinfo.CI_RIGHTROLES'. [SQLSTATE
>> > 01000]
>> > DBCC results for 'cinfo.CI_RUNTIMEIMAGE'. [SQLSTATE 01000]
>> > There are 2080 rows in 101 pages for object 'cinfo.CI_RUNTIMEIMAGE'.
>> > [SQLSTATE 01000]
>> > DBCC results for 'cinfo.CI_SCHEDULES'. [SQLSTATE 01000]
>> > There are 0 rows in 1 pages for object 'cinfo.CI_SCHEDULES'. [SQLSTATE 01000]
>> > DBCC results for 'cinfo.CI_SECRIGHTS'. [SQLSTATE 01000]
>> > There are 1397 rows in 12 pages for object 'cinfo.CI_SECRIGHTS'. [SQLSTATE
>> > 01000]
>> > DBCC results for 'cinfo.CI_SPECIALDATES'. [SQLSTATE 01000]
>> > There are 0 rows in 1 pages for object 'cinfo.CI_SPECIALDATES'. [SQLSTATE
>> > 01000]
>> > DBCC results for 'cinfo.CI_SPECIALDAYS'. [SQLSTATE 01000]
>> > There are 0 rows in 1 pages for object 'cinfo.CI_SPECIALDAYS'. [SQLSTATE
>> > 01000]
>> > DBCC results for 'cinfo.CI_TEMPLATEDATES'. [SQLSTATE 01000]
>> > There are 458 rows in 4 pages for object 'cinfo.CI_TEMPLATEDATES'. [SQLSTATE
>> > 01000]
>> > DBCC results for 'cinfo.CI_TEMPLATEDAYS'. [SQLSTATE 01000]
>> > There are 143 rows in 1 pages for object 'cinfo.CI_TEMPLATEDAYS'. [SQLSTATE
>> > 01000]
>> > DBCC results for 'cinfo.CI_TEMPLATES'. [SQLSTATE 01000]
>> > There are 9 rows in 1 pages for object 'cinfo.CI_TEMPLATES'. [SQLSTATE 01000]
>> > DBCC results for 'cinfo.CI_TIMEINFO'. [SQLSTATE 01000]
>> > There are 0 rows in 1 pages for object 'cinfo.CI_TIMEINFO'. [SQLSTATE 01000]
>> > DBCC results for 'cinfo.CI_USERS'. [SQLSTATE 01000]
>> > There are 51 rows in 5 pages for object 'cinfo.CI_USERS'. [SQLSTATE 01000]
>> > DBCC results for 'cinfo.CI_CHANNEL_INFO'. [SQLSTATE 01000]
>> > There are 0 rows in 1 pages for object 'cinfo.CI_CHANNEL_INFO'. [SQLSTATE
>> > 01000]
>> > DBCC results for 'cinfo.CI_ARCHIVEDOBJECTS'. [SQLSTATE 01000]
>> > There are 0 rows in 1 pages for object 'cinfo.CI_ARCHIVEDOBJECTS'. [SQLSTATE
>> > 01000]
>> > DBCC results for 'dtproperties'. [SQLSTATE 01000]
>> > There are 0 rows in 1 pages for object 'dtproperties'. [SQLSTATE 01000]
>> > CHECKDB found 0 allocation errors and 0 consistency errors in database
>> > 'cinfo'. [SQLSTATE 01000]
>> > DBCC execution completed. If DBCC printed error messages, contact your
>> > system administrator. [SQLSTATE 01000]
>> >
>> >
>> > "Paul S Randal [MS]" wrote:
>> >
>> >> Can you post the output? As far as I'm aware, the integrity check runs DBCC
>> >> CHECKDB.
>> >>
>> >> --
>> >> Paul Randal
>> >> Dev Lead, Microsoft SQL Server Storage Engine
>> >>
>> >> This posting is provided "AS IS" with no warranties, and confers no rights.
>> >>
>> >> "Ron" <Ron@.discussions.microsoft.com> wrote in message
>> >> news:03075079-DA30-47EE-9550-E792A8E4EB1D@.microsoft.com...
>> >> > No different results.
>> >> >
>> >> > Because the Integrity with Indexes via the maintenance plan produces
>> >> > different output than a DBCC checkdb database, I wanted to know if both
>> >> are
>> >> > doing the same thing.
>> >> >
>> >> > I'm thinking of replacing the integrity with a DBCC checkdb, but would
>> >> like
>> >> > to know what's the difference between the two besides the output.
>> >> >
>> >> > "Paul S Randal [MS]" wrote:
>> >> >
>> >> > > What about if you manually run DBCC CHECKDB ('database') WITH
>> >> NO_INFOMSGS?
>> >> > > Do the outputs match then?
>> >> > >
>> >> > > --
>> >> > > Paul Randal
>> >> > > Dev Lead, Microsoft SQL Server Storage Engine
>> >> > >
>> >> > > This posting is provided "AS IS" with no warranties, and confers no
>> >> rights.
>> >> > >
>> >> > > "Ron" <Ron@.discussions.microsoft.com> wrote in message
>> >> > > news:9E360D8A-D225-45C8-A5F7-D8671E46F417@.microsoft.com...
>> >> > > > Is there a difference running checkdb -DBCC checkdb ('database') and
>> >> > > running
>> >> > > > the Integrity with Indexes option of a maintenance plan? The checkdb
>> >> > > output
>> >> > > > shows detail while the integrity output shows almost no detail.
>> >> > > >
>> >> > > > Thanks
>> >> > > >
>> >> > > > Ron
>> >> > >
>> >> > >
>> >> > >
>> >>
>> >>
>> >>
>>|||You can also find the SQL commands that the maintenance plan
runs for whatever options are selected in the following
article:
http://www.sql-server-performance.com/ak_inside_sql_server_maintenance_plans.asp
-Sue
On Tue, 15 Feb 2005 06:55:06 -0800, Ron
<Ron@.discussions.microsoft.com> wrote:
>I'm not sure I follow. When dbcc checkdb runs with NO_INFOMSGS it doesn't
>look like the Integrity output.
>I guess my question is simply "Does the Integrity (with indexes) job from
>the maintenance plan do exactly what DBCC checkdb does?"
>"Tibor Karaszi" wrote:
>> Seems like maint wiz doesn't add WITH NO_INFOMSGS to the DBCC commend...
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>> http://www.sqlug.se/
>>
>> "Ron" <Ron@.discussions.microsoft.com> wrote in message
>> news:57E3528C-7953-47CE-BB5B-19C35199C094@.microsoft.com...
>> > Here the Integrity output:
>> > 1] Database ABCD: Check Data and Index Linkage...
>> >
>> >
>> >
>> > (null)
>> > (null)
>> > ** Execution Time: 0 hrs, 0 mins, 1 secs **
>> >
>> > Here's the DBCC checkdb output :
>> > Job 'DBCC checkdb' : Step 1, 'CheckDB Cinfo' : Began Executing 2005-02-13
>> > 04:00:00
>> >
>> > DBCC results for 'Cinfo'. [SQLSTATE 01000]
>> > DBCC results for 'sysobjects'. [SQLSTATE 01000]
>> > There are 71 rows in 1 pages for object 'sysobjects'. [SQLSTATE 01000]
>> > DBCC results for 'sysindexes'. [SQLSTATE 01000]
>> > There are 125 rows in 5 pages for object 'sysindexes'. [SQLSTATE 01000]
>> > DBCC results for 'syscolumns'. [SQLSTATE 01000]
>> > There are 514 rows in 9 pages for object 'syscolumns'. [SQLSTATE 01000]
>> > DBCC results for 'systypes'. [SQLSTATE 01000]
>> > There are 26 rows in 1 pages for object 'systypes'. [SQLSTATE 01000]
>> > DBCC results for 'syscomments'. [SQLSTATE 01000]
>> > There are 113 rows in 10 pages for object 'syscomments'. [SQLSTATE 01000]
>> > DBCC results for 'sysfiles1'. [SQLSTATE 01000]
>> > There are 2 rows in 1 pages for object 'sysfiles1'. [SQLSTATE 01000]
>> > DBCC results for 'syspermissions'. [SQLSTATE 01000]
>> > There are 37 rows in 1 pages for object 'syspermissions'. [SQLSTATE 01000]
>> > DBCC results for 'sysusers'. [SQLSTATE 01000]
>> > There are 17 rows in 1 pages for object 'sysusers'. [SQLSTATE 01000]
>> > DBCC results for 'sysproperties'. [SQLSTATE 01000]
>> > There are 0 rows in 0 pages for object 'sysproperties'. [SQLSTATE 01000]
>> > DBCC results for 'sysdepends'. [SQLSTATE 01000]
>> > There are 422 rows in 2 pages for object 'sysdepends'. [SQLSTATE 01000]
>> > DBCC results for 'sysreferences'. [SQLSTATE 01000]
>> > There are 0 rows in 1 pages for object 'sysreferences'. [SQLSTATE 01000]
>> > DBCC results for 'sysfulltextcatalogs'. [SQLSTATE 01000]
>> > There are 0 rows in 1 pages for object 'sysfulltextcatalogs'. [SQLSTATE 01000]
>> > DBCC results for 'sysfulltextnotify'. [SQLSTATE 01000]
>> > There are 0 rows in 0 pages for object 'sysfulltextnotify'. [SQLSTATE 01000]
>> > DBCC results for 'sysfilegroups'. [SQLSTATE 01000]
>> > There are 1 rows in 1 pages for object 'sysfilegroups'. [SQLSTATE 01000]
>> > DBCC results for 'cinfo.CI_APS'. [SQLSTATE 01000]
>> > There are 1 rows in 1 pages for object 'cinfo.CI_APS'. [SQLSTATE 01000]
>> > DBCC results for 'cinfo.CI_AUDITTRACE'. [SQLSTATE 01000]
>> > There are 0 rows in 1 pages for object 'cinfo.CI_AUDITTRACE'. [SQLSTATE 01000]
>> > DBCC results for 'cinfo.CI_CLSMACHINES'. [SQLSTATE 01000]
>> > There are 2 rows in 1 pages for object 'cinfo.CI_CLSMACHINES'. [SQLSTATE
>> > 01000]
>> > DBCC results for 'cinfo.CI_EVENTS'. [SQLSTATE 01000]
>> > There are 2 rows in 1 pages for object 'cinfo.CI_EVENTS'. [SQLSTATE 01000]
>> > DBCC results for 'cinfo.CI_GOVINFO'. [SQLSTATE 01000]
>> > There are 0 rows in 1 pages for object 'cinfo.CI_GOVINFO'. [SQLSTATE 01000]
>> > DBCC results for 'cinfo.CI_GRPINFO'. [SQLSTATE 01000]
>> > There are 7 rows in 2 pages for object 'cinfo.CI_GRPINFO'. [SQLSTATE 01000]
>> > DBCC results for 'cinfo.CI_GRPUSERS'. [SQLSTATE 01000]
>> > There are 106 rows in 2 pages for object 'cinfo.CI_GRPUSERS'. [SQLSTATE 01000]
>> > DBCC results for 'cinfo.CI_HISTORY'. [SQLSTATE 01000]
>> > There are 0 rows in 1 pages for object 'cinfo.CI_HISTORY'. [SQLSTATE 01000]
>> > DBCC results for 'cinfo.CI_INFOOBJECTS'. [SQLSTATE 01000]
>> > There are 589 rows in 22 pages for object 'cinfo.CI_INFOOBJECTS'. [SQLSTATE
>> > 01000]
>> > DBCC results for 'cinfo.CI_ISPLUGINS'. [SQLSTATE 01000]
>> > There are 0 rows in 1 pages for object 'cinfo.CI_ISPLUGINS'. [SQLSTATE 01000]
>> > DBCC results for 'cinfo.CI_MACHAVAIL'. [SQLSTATE 01000]
>> > There are 0 rows in 1 pages for object 'cinfo.CI_MACHAVAIL'. [SQLSTATE 01000]
>> > DBCC results for 'cinfo.CI_MACHINECLASS'. [SQLSTATE 01000]
>> > There are 0 rows in 1 pages for object 'cinfo.CI_MACHINECLASS'. [SQLSTATE
>> > 01000]
>> > DBCC results for 'cinfo.CI_MACHINEGROUP'. [SQLSTATE 01000]
>> > There are 2 rows in 1 pages for object 'cinfo.CI_MACHINEGROUP'. [SQLSTATE
>> > 01000]
>> > DBCC results for 'cinfo.CI_MACHINV'. [SQLSTATE 01000]
>> > There are 2 rows in 1 pages for object 'cinfo.CI_MACHINV'. [SQLSTATE 01000]
>> > DBCC results for 'cinfo.CI_NEXTID'. [SQLSTATE 01000]
>> > There are 1 rows in 1 pages for object 'cinfo.CI_NEXTID'. [SQLSTATE 01000]
>> > DBCC results for 'cinfo.CI_RESTRICTIONS'. [SQLSTATE 01000]
>> > There are 0 rows in 1 pages for object 'cinfo.CI_RESTRICTIONS'. [SQLSTATE
>> > 01000]
>> > DBCC results for 'cinfo.CI_RIGHTROLES'. [SQLSTATE 01000]
>> > There are 145 rows in 1 pages for object 'cinfo.CI_RIGHTROLES'. [SQLSTATE
>> > 01000]
>> > DBCC results for 'cinfo.CI_RUNTIMEIMAGE'. [SQLSTATE 01000]
>> > There are 2080 rows in 101 pages for object 'cinfo.CI_RUNTIMEIMAGE'.
>> > [SQLSTATE 01000]
>> > DBCC results for 'cinfo.CI_SCHEDULES'. [SQLSTATE 01000]
>> > There are 0 rows in 1 pages for object 'cinfo.CI_SCHEDULES'. [SQLSTATE 01000]
>> > DBCC results for 'cinfo.CI_SECRIGHTS'. [SQLSTATE 01000]
>> > There are 1397 rows in 12 pages for object 'cinfo.CI_SECRIGHTS'. [SQLSTATE
>> > 01000]
>> > DBCC results for 'cinfo.CI_SPECIALDATES'. [SQLSTATE 01000]
>> > There are 0 rows in 1 pages for object 'cinfo.CI_SPECIALDATES'. [SQLSTATE
>> > 01000]
>> > DBCC results for 'cinfo.CI_SPECIALDAYS'. [SQLSTATE 01000]
>> > There are 0 rows in 1 pages for object 'cinfo.CI_SPECIALDAYS'. [SQLSTATE
>> > 01000]
>> > DBCC results for 'cinfo.CI_TEMPLATEDATES'. [SQLSTATE 01000]
>> > There are 458 rows in 4 pages for object 'cinfo.CI_TEMPLATEDATES'. [SQLSTATE
>> > 01000]
>> > DBCC results for 'cinfo.CI_TEMPLATEDAYS'. [SQLSTATE 01000]
>> > There are 143 rows in 1 pages for object 'cinfo.CI_TEMPLATEDAYS'. [SQLSTATE
>> > 01000]
>> > DBCC results for 'cinfo.CI_TEMPLATES'. [SQLSTATE 01000]
>> > There are 9 rows in 1 pages for object 'cinfo.CI_TEMPLATES'. [SQLSTATE 01000]
>> > DBCC results for 'cinfo.CI_TIMEINFO'. [SQLSTATE 01000]
>> > There are 0 rows in 1 pages for object 'cinfo.CI_TIMEINFO'. [SQLSTATE 01000]
>> > DBCC results for 'cinfo.CI_USERS'. [SQLSTATE 01000]
>> > There are 51 rows in 5 pages for object 'cinfo.CI_USERS'. [SQLSTATE 01000]
>> > DBCC results for 'cinfo.CI_CHANNEL_INFO'. [SQLSTATE 01000]
>> > There are 0 rows in 1 pages for object 'cinfo.CI_CHANNEL_INFO'. [SQLSTATE
>> > 01000]
>> > DBCC results for 'cinfo.CI_ARCHIVEDOBJECTS'. [SQLSTATE 01000]
>> > There are 0 rows in 1 pages for object 'cinfo.CI_ARCHIVEDOBJECTS'. [SQLSTATE
>> > 01000]
>> > DBCC results for 'dtproperties'. [SQLSTATE 01000]
>> > There are 0 rows in 1 pages for object 'dtproperties'. [SQLSTATE 01000]
>> > CHECKDB found 0 allocation errors and 0 consistency errors in database
>> > 'cinfo'. [SQLSTATE 01000]
>> > DBCC execution completed. If DBCC printed error messages, contact your
>> > system administrator. [SQLSTATE 01000]
>> >
>> >
>> > "Paul S Randal [MS]" wrote:
>> >
>> >> Can you post the output? As far as I'm aware, the integrity check runs DBCC
>> >> CHECKDB.
>> >>
>> >> --
>> >> Paul Randal
>> >> Dev Lead, Microsoft SQL Server Storage Engine
>> >>
>> >> This posting is provided "AS IS" with no warranties, and confers no rights.
>> >>
>> >> "Ron" <Ron@.discussions.microsoft.com> wrote in message
>> >> news:03075079-DA30-47EE-9550-E792A8E4EB1D@.microsoft.com...
>> >> > No different results.
>> >> >
>> >> > Because the Integrity with Indexes via the maintenance plan produces
>> >> > different output than a DBCC checkdb database, I wanted to know if both
>> >> are
>> >> > doing the same thing.
>> >> >
>> >> > I'm thinking of replacing the integrity with a DBCC checkdb, but would
>> >> like
>> >> > to know what's the difference between the two besides the output.
>> >> >
>> >> > "Paul S Randal [MS]" wrote:
>> >> >
>> >> > > What about if you manually run DBCC CHECKDB ('database') WITH
>> >> NO_INFOMSGS?
>> >> > > Do the outputs match then?
>> >> > >
>> >> > > --
>> >> > > Paul Randal
>> >> > > Dev Lead, Microsoft SQL Server Storage Engine
>> >> > >
>> >> > > This posting is provided "AS IS" with no warranties, and confers no
>> >> rights.
>> >> > >
>> >> > > "Ron" <Ron@.discussions.microsoft.com> wrote in message
>> >> > > news:9E360D8A-D225-45C8-A5F7-D8671E46F417@.microsoft.com...
>> >> > > > Is there a difference running checkdb -DBCC checkdb ('database') and
>> >> > > running
>> >> > > > the Integrity with Indexes option of a maintenance plan? The checkdb
>> >> > > output
>> >> > > > shows detail while the integrity output shows almost no detail.
>> >> > > >
>> >> > > > Thanks
>> >> > > >
>> >> > > > Ron
>> >> > >
>> >> > >
>> >> > >
>> >>
>> >>
>> >>
>>|||And to answer your question, the integrity job uses DBCC CHECKDB so it's
doing exactly the same as a manual DBCC CHECKDB.
--
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:qd8411pgobfai7a405kjpisvroftt9a9ap@.4ax.com...
> You can also find the SQL commands that the maintenance plan
> runs for whatever options are selected in the following
> article:
>
http://www.sql-server-performance.com/ak_inside_sql_server_maintenance_plans.asp
> -Sue
> On Tue, 15 Feb 2005 06:55:06 -0800, Ron
> <Ron@.discussions.microsoft.com> wrote:
> >I'm not sure I follow. When dbcc checkdb runs with NO_INFOMSGS it
doesn't
> >look like the Integrity output.
> >
> >I guess my question is simply "Does the Integrity (with indexes) job from
> >the maintenance plan do exactly what DBCC checkdb does?"
> >
> >"Tibor Karaszi" wrote:
> >
> >> Seems like maint wiz doesn't add WITH NO_INFOMSGS to the DBCC
commend...
> >>
> >> --
> >> Tibor Karaszi, SQL Server MVP
> >> http://www.karaszi.com/sqlserver/default.asp
> >> http://www.solidqualitylearning.com/
> >> http://www.sqlug.se/
> >>
> >>
> >> "Ron" <Ron@.discussions.microsoft.com> wrote in message
> >> news:57E3528C-7953-47CE-BB5B-19C35199C094@.microsoft.com...
> >> > Here the Integrity output:
> >> > 1] Database ABCD: Check Data and Index Linkage...
> >> >
> >> >
> >> >
> >> > (null)
> >> > (null)
> >> > ** Execution Time: 0 hrs, 0 mins, 1 secs **
> >> >
> >> > Here's the DBCC checkdb output :
> >> > Job 'DBCC checkdb' : Step 1, 'CheckDB Cinfo' : Began Executing
2005-02-13
> >> > 04:00:00
> >> >
> >> > DBCC results for 'Cinfo'. [SQLSTATE 01000]
> >> > DBCC results for 'sysobjects'. [SQLSTATE 01000]
> >> > There are 71 rows in 1 pages for object 'sysobjects'. [SQLSTATE
01000]
> >> > DBCC results for 'sysindexes'. [SQLSTATE 01000]
> >> > There are 125 rows in 5 pages for object 'sysindexes'. [SQLSTATE
01000]
> >> > DBCC results for 'syscolumns'. [SQLSTATE 01000]
> >> > There are 514 rows in 9 pages for object 'syscolumns'. [SQLSTATE
01000]
> >> > DBCC results for 'systypes'. [SQLSTATE 01000]
> >> > There are 26 rows in 1 pages for object 'systypes'. [SQLSTATE 01000]
> >> > DBCC results for 'syscomments'. [SQLSTATE 01000]
> >> > There are 113 rows in 10 pages for object 'syscomments'. [SQLSTATE
01000]
> >> > DBCC results for 'sysfiles1'. [SQLSTATE 01000]
> >> > There are 2 rows in 1 pages for object 'sysfiles1'. [SQLSTATE 01000]
> >> > DBCC results for 'syspermissions'. [SQLSTATE 01000]
> >> > There are 37 rows in 1 pages for object 'syspermissions'. [SQLSTATE
01000]
> >> > DBCC results for 'sysusers'. [SQLSTATE 01000]
> >> > There are 17 rows in 1 pages for object 'sysusers'. [SQLSTATE 01000]
> >> > DBCC results for 'sysproperties'. [SQLSTATE 01000]
> >> > There are 0 rows in 0 pages for object 'sysproperties'. [SQLSTATE
01000]
> >> > DBCC results for 'sysdepends'. [SQLSTATE 01000]
> >> > There are 422 rows in 2 pages for object 'sysdepends'. [SQLSTATE
01000]
> >> > DBCC results for 'sysreferences'. [SQLSTATE 01000]
> >> > There are 0 rows in 1 pages for object 'sysreferences'. [SQLSTATE
01000]
> >> > DBCC results for 'sysfulltextcatalogs'. [SQLSTATE 01000]
> >> > There are 0 rows in 1 pages for object 'sysfulltextcatalogs'.
[SQLSTATE 01000]
> >> > DBCC results for 'sysfulltextnotify'. [SQLSTATE 01000]
> >> > There are 0 rows in 0 pages for object 'sysfulltextnotify'. [SQLSTATE
01000]
> >> > DBCC results for 'sysfilegroups'. [SQLSTATE 01000]
> >> > There are 1 rows in 1 pages for object 'sysfilegroups'. [SQLSTATE
01000]
> >> > DBCC results for 'cinfo.CI_APS'. [SQLSTATE 01000]
> >> > There are 1 rows in 1 pages for object 'cinfo.CI_APS'. [SQLSTATE
01000]
> >> > DBCC results for 'cinfo.CI_AUDITTRACE'. [SQLSTATE 01000]
> >> > There are 0 rows in 1 pages for object 'cinfo.CI_AUDITTRACE'.
[SQLSTATE 01000]
> >> > DBCC results for 'cinfo.CI_CLSMACHINES'. [SQLSTATE 01000]
> >> > There are 2 rows in 1 pages for object 'cinfo.CI_CLSMACHINES'.
[SQLSTATE
> >> > 01000]
> >> > DBCC results for 'cinfo.CI_EVENTS'. [SQLSTATE 01000]
> >> > There are 2 rows in 1 pages for object 'cinfo.CI_EVENTS'. [SQLSTATE
01000]
> >> > DBCC results for 'cinfo.CI_GOVINFO'. [SQLSTATE 01000]
> >> > There are 0 rows in 1 pages for object 'cinfo.CI_GOVINFO'. [SQLSTATE
01000]
> >> > DBCC results for 'cinfo.CI_GRPINFO'. [SQLSTATE 01000]
> >> > There are 7 rows in 2 pages for object 'cinfo.CI_GRPINFO'. [SQLSTATE
01000]
> >> > DBCC results for 'cinfo.CI_GRPUSERS'. [SQLSTATE 01000]
> >> > There are 106 rows in 2 pages for object 'cinfo.CI_GRPUSERS'.
[SQLSTATE 01000]
> >> > DBCC results for 'cinfo.CI_HISTORY'. [SQLSTATE 01000]
> >> > There are 0 rows in 1 pages for object 'cinfo.CI_HISTORY'. [SQLSTATE
01000]
> >> > DBCC results for 'cinfo.CI_INFOOBJECTS'. [SQLSTATE 01000]
> >> > There are 589 rows in 22 pages for object 'cinfo.CI_INFOOBJECTS'.
[SQLSTATE
> >> > 01000]
> >> > DBCC results for 'cinfo.CI_ISPLUGINS'. [SQLSTATE 01000]
> >> > There are 0 rows in 1 pages for object 'cinfo.CI_ISPLUGINS'.
[SQLSTATE 01000]
> >> > DBCC results for 'cinfo.CI_MACHAVAIL'. [SQLSTATE 01000]
> >> > There are 0 rows in 1 pages for object 'cinfo.CI_MACHAVAIL'.
[SQLSTATE 01000]
> >> > DBCC results for 'cinfo.CI_MACHINECLASS'. [SQLSTATE 01000]
> >> > There are 0 rows in 1 pages for object 'cinfo.CI_MACHINECLASS'.
[SQLSTATE
> >> > 01000]
> >> > DBCC results for 'cinfo.CI_MACHINEGROUP'. [SQLSTATE 01000]
> >> > There are 2 rows in 1 pages for object 'cinfo.CI_MACHINEGROUP'.
[SQLSTATE
> >> > 01000]
> >> > DBCC results for 'cinfo.CI_MACHINV'. [SQLSTATE 01000]
> >> > There are 2 rows in 1 pages for object 'cinfo.CI_MACHINV'. [SQLSTATE
01000]
> >> > DBCC results for 'cinfo.CI_NEXTID'. [SQLSTATE 01000]
> >> > There are 1 rows in 1 pages for object 'cinfo.CI_NEXTID'. [SQLSTATE
01000]
> >> > DBCC results for 'cinfo.CI_RESTRICTIONS'. [SQLSTATE 01000]
> >> > There are 0 rows in 1 pages for object 'cinfo.CI_RESTRICTIONS'.
[SQLSTATE
> >> > 01000]
> >> > DBCC results for 'cinfo.CI_RIGHTROLES'. [SQLSTATE 01000]
> >> > There are 145 rows in 1 pages for object 'cinfo.CI_RIGHTROLES'.
[SQLSTATE
> >> > 01000]
> >> > DBCC results for 'cinfo.CI_RUNTIMEIMAGE'. [SQLSTATE 01000]
> >> > There are 2080 rows in 101 pages for object 'cinfo.CI_RUNTIMEIMAGE'.
> >> > [SQLSTATE 01000]
> >> > DBCC results for 'cinfo.CI_SCHEDULES'. [SQLSTATE 01000]
> >> > There are 0 rows in 1 pages for object 'cinfo.CI_SCHEDULES'.
[SQLSTATE 01000]
> >> > DBCC results for 'cinfo.CI_SECRIGHTS'. [SQLSTATE 01000]
> >> > There are 1397 rows in 12 pages for object 'cinfo.CI_SECRIGHTS'.
[SQLSTATE
> >> > 01000]
> >> > DBCC results for 'cinfo.CI_SPECIALDATES'. [SQLSTATE 01000]
> >> > There are 0 rows in 1 pages for object 'cinfo.CI_SPECIALDATES'.
[SQLSTATE
> >> > 01000]
> >> > DBCC results for 'cinfo.CI_SPECIALDAYS'. [SQLSTATE 01000]
> >> > There are 0 rows in 1 pages for object 'cinfo.CI_SPECIALDAYS'.
[SQLSTATE
> >> > 01000]
> >> > DBCC results for 'cinfo.CI_TEMPLATEDATES'. [SQLSTATE 01000]
> >> > There are 458 rows in 4 pages for object 'cinfo.CI_TEMPLATEDATES'.
[SQLSTATE
> >> > 01000]
> >> > DBCC results for 'cinfo.CI_TEMPLATEDAYS'. [SQLSTATE 01000]
> >> > There are 143 rows in 1 pages for object 'cinfo.CI_TEMPLATEDAYS'.
[SQLSTATE
> >> > 01000]
> >> > DBCC results for 'cinfo.CI_TEMPLATES'. [SQLSTATE 01000]
> >> > There are 9 rows in 1 pages for object 'cinfo.CI_TEMPLATES'.
[SQLSTATE 01000]
> >> > DBCC results for 'cinfo.CI_TIMEINFO'. [SQLSTATE 01000]
> >> > There are 0 rows in 1 pages for object 'cinfo.CI_TIMEINFO'. [SQLSTATE
01000]
> >> > DBCC results for 'cinfo.CI_USERS'. [SQLSTATE 01000]
> >> > There are 51 rows in 5 pages for object 'cinfo.CI_USERS'. [SQLSTATE
01000]
> >> > DBCC results for 'cinfo.CI_CHANNEL_INFO'. [SQLSTATE 01000]
> >> > There are 0 rows in 1 pages for object 'cinfo.CI_CHANNEL_INFO'.
[SQLSTATE
> >> > 01000]
> >> > DBCC results for 'cinfo.CI_ARCHIVEDOBJECTS'. [SQLSTATE 01000]
> >> > There are 0 rows in 1 pages for object 'cinfo.CI_ARCHIVEDOBJECTS'.
[SQLSTATE
> >> > 01000]
> >> > DBCC results for 'dtproperties'. [SQLSTATE 01000]
> >> > There are 0 rows in 1 pages for object 'dtproperties'. [SQLSTATE
01000]
> >> > CHECKDB found 0 allocation errors and 0 consistency errors in
database
> >> > 'cinfo'. [SQLSTATE 01000]
> >> > DBCC execution completed. If DBCC printed error messages, contact
your
> >> > system administrator. [SQLSTATE 01000]
> >> >
> >> >
> >> > "Paul S Randal [MS]" wrote:
> >> >
> >> >> Can you post the output? As far as I'm aware, the integrity check
runs DBCC
> >> >> CHECKDB.
> >> >>
> >> >> --
> >> >> Paul Randal
> >> >> Dev Lead, Microsoft SQL Server Storage Engine
> >> >>
> >> >> This posting is provided "AS IS" with no warranties, and confers no
rights.
> >> >>
> >> >> "Ron" <Ron@.discussions.microsoft.com> wrote in message
> >> >> news:03075079-DA30-47EE-9550-E792A8E4EB1D@.microsoft.com...
> >> >> > No different results.
> >> >> >
> >> >> > Because the Integrity with Indexes via the maintenance plan
produces
> >> >> > different output than a DBCC checkdb database, I wanted to know if
both
> >> >> are
> >> >> > doing the same thing.
> >> >> >
> >> >> > I'm thinking of replacing the integrity with a DBCC checkdb, but
would
> >> >> like
> >> >> > to know what's the difference between the two besides the output.
> >> >> >
> >> >> > "Paul S Randal [MS]" wrote:
> >> >> >
> >> >> > > What about if you manually run DBCC CHECKDB ('database') WITH
> >> >> NO_INFOMSGS?
> >> >> > > Do the outputs match then?
> >> >> > >
> >> >> > > --
> >> >> > > Paul Randal
> >> >> > > Dev Lead, Microsoft SQL Server Storage Engine
> >> >> > >
> >> >> > > This posting is provided "AS IS" with no warranties, and confers
no
> >> >> rights.
> >> >> > >
> >> >> > > "Ron" <Ron@.discussions.microsoft.com> wrote in message
> >> >> > > news:9E360D8A-D225-45C8-A5F7-D8671E46F417@.microsoft.com...
> >> >> > > > Is there a difference running checkdb -DBCC checkdb
('database') and
> >> >> > > running
> >> >> > > > the Integrity with Indexes option of a maintenance plan? The
checkdb
> >> >> > > output
> >> >> > > > shows detail while the integrity output shows almost no
detail.
> >> >> > > >
> >> >> > > > Thanks
> >> >> > > >
> >> >> > > > Ron
> >> >> > >
> >> >> > >
> >> >> > >
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>
>|||Thanks Everyone!
"Paul S Randal [MS]" wrote:
> And to answer your question, the integrity job uses DBCC CHECKDB so it's
> doing exactly the same as a manual DBCC CHECKDB.
> --
> Paul Randal
> Dev Lead, Microsoft SQL Server Storage Engine
> This posting is provided "AS IS" with no warranties, and confers no rights.
> "Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
> news:qd8411pgobfai7a405kjpisvroftt9a9ap@.4ax.com...
> > You can also find the SQL commands that the maintenance plan
> > runs for whatever options are selected in the following
> > article:
> >
> http://www.sql-server-performance.com/ak_inside_sql_server_maintenance_plans.asp
> >
> > -Sue
> >
> > On Tue, 15 Feb 2005 06:55:06 -0800, Ron
> > <Ron@.discussions.microsoft.com> wrote:
> >
> > >I'm not sure I follow. When dbcc checkdb runs with NO_INFOMSGS it
> doesn't
> > >look like the Integrity output.
> > >
> > >I guess my question is simply "Does the Integrity (with indexes) job from
> > >the maintenance plan do exactly what DBCC checkdb does?"
> > >
> > >"Tibor Karaszi" wrote:
> > >
> > >> Seems like maint wiz doesn't add WITH NO_INFOMSGS to the DBCC
> commend...
> > >>
> > >> --
> > >> Tibor Karaszi, SQL Server MVP
> > >> http://www.karaszi.com/sqlserver/default.asp
> > >> http://www.solidqualitylearning.com/
> > >> http://www.sqlug.se/
> > >>
> > >>
> > >> "Ron" <Ron@.discussions.microsoft.com> wrote in message
> > >> news:57E3528C-7953-47CE-BB5B-19C35199C094@.microsoft.com...
> > >> > Here the Integrity output:
> > >> > 1] Database ABCD: Check Data and Index Linkage...
> > >> >
> > >> >
> > >> >
> > >> > (null)
> > >> > (null)
> > >> > ** Execution Time: 0 hrs, 0 mins, 1 secs **
> > >> >
> > >> > Here's the DBCC checkdb output :
> > >> > Job 'DBCC checkdb' : Step 1, 'CheckDB Cinfo' : Began Executing
> 2005-02-13
> > >> > 04:00:00
> > >> >
> > >> > DBCC results for 'Cinfo'. [SQLSTATE 01000]
> > >> > DBCC results for 'sysobjects'. [SQLSTATE 01000]
> > >> > There are 71 rows in 1 pages for object 'sysobjects'. [SQLSTATE
> 01000]
> > >> > DBCC results for 'sysindexes'. [SQLSTATE 01000]
> > >> > There are 125 rows in 5 pages for object 'sysindexes'. [SQLSTATE
> 01000]
> > >> > DBCC results for 'syscolumns'. [SQLSTATE 01000]
> > >> > There are 514 rows in 9 pages for object 'syscolumns'. [SQLSTATE
> 01000]
> > >> > DBCC results for 'systypes'. [SQLSTATE 01000]
> > >> > There are 26 rows in 1 pages for object 'systypes'. [SQLSTATE 01000]
> > >> > DBCC results for 'syscomments'. [SQLSTATE 01000]
> > >> > There are 113 rows in 10 pages for object 'syscomments'. [SQLSTATE
> 01000]
> > >> > DBCC results for 'sysfiles1'. [SQLSTATE 01000]
> > >> > There are 2 rows in 1 pages for object 'sysfiles1'. [SQLSTATE 01000]
> > >> > DBCC results for 'syspermissions'. [SQLSTATE 01000]
> > >> > There are 37 rows in 1 pages for object 'syspermissions'. [SQLSTATE
> 01000]
> > >> > DBCC results for 'sysusers'. [SQLSTATE 01000]
> > >> > There are 17 rows in 1 pages for object 'sysusers'. [SQLSTATE 01000]
> > >> > DBCC results for 'sysproperties'. [SQLSTATE 01000]
> > >> > There are 0 rows in 0 pages for object 'sysproperties'. [SQLSTATE
> 01000]
> > >> > DBCC results for 'sysdepends'. [SQLSTATE 01000]
> > >> > There are 422 rows in 2 pages for object 'sysdepends'. [SQLSTATE
> 01000]
> > >> > DBCC results for 'sysreferences'. [SQLSTATE 01000]
> > >> > There are 0 rows in 1 pages for object 'sysreferences'. [SQLSTATE
> 01000]
> > >> > DBCC results for 'sysfulltextcatalogs'. [SQLSTATE 01000]
> > >> > There are 0 rows in 1 pages for object 'sysfulltextcatalogs'.
> [SQLSTATE 01000]
> > >> > DBCC results for 'sysfulltextnotify'. [SQLSTATE 01000]
> > >> > There are 0 rows in 0 pages for object 'sysfulltextnotify'. [SQLSTATE
> 01000]
> > >> > DBCC results for 'sysfilegroups'. [SQLSTATE 01000]
> > >> > There are 1 rows in 1 pages for object 'sysfilegroups'. [SQLSTATE
> 01000]
> > >> > DBCC results for 'cinfo.CI_APS'. [SQLSTATE 01000]
> > >> > There are 1 rows in 1 pages for object 'cinfo.CI_APS'. [SQLSTATE
> 01000]
> > >> > DBCC results for 'cinfo.CI_AUDITTRACE'. [SQLSTATE 01000]
> > >> > There are 0 rows in 1 pages for object 'cinfo.CI_AUDITTRACE'.
> [SQLSTATE 01000]
> > >> > DBCC results for 'cinfo.CI_CLSMACHINES'. [SQLSTATE 01000]
> > >> > There are 2 rows in 1 pages for object 'cinfo.CI_CLSMACHINES'.
> [SQLSTATE
> > >> > 01000]
> > >> > DBCC results for 'cinfo.CI_EVENTS'. [SQLSTATE 01000]
> > >> > There are 2 rows in 1 pages for object 'cinfo.CI_EVENTS'. [SQLSTATE
> 01000]
> > >> > DBCC results for 'cinfo.CI_GOVINFO'. [SQLSTATE 01000]
> > >> > There are 0 rows in 1 pages for object 'cinfo.CI_GOVINFO'. [SQLSTATE
> 01000]
> > >> > DBCC results for 'cinfo.CI_GRPINFO'. [SQLSTATE 01000]
> > >> > There are 7 rows in 2 pages for object 'cinfo.CI_GRPINFO'. [SQLSTATE
> 01000]
> > >> > DBCC results for 'cinfo.CI_GRPUSERS'. [SQLSTATE 01000]
> > >> > There are 106 rows in 2 pages for object 'cinfo.CI_GRPUSERS'.
> [SQLSTATE 01000]
> > >> > DBCC results for 'cinfo.CI_HISTORY'. [SQLSTATE 01000]
> > >> > There are 0 rows in 1 pages for object 'cinfo.CI_HISTORY'. [SQLSTATE
> 01000]
> > >> > DBCC results for 'cinfo.CI_INFOOBJECTS'. [SQLSTATE 01000]
> > >> > There are 589 rows in 22 pages for object 'cinfo.CI_INFOOBJECTS'.
> [SQLSTATE
> > >> > 01000]
> > >> > DBCC results for 'cinfo.CI_ISPLUGINS'. [SQLSTATE 01000]
> > >> > There are 0 rows in 1 pages for object 'cinfo.CI_ISPLUGINS'.
> [SQLSTATE 01000]
> > >> > DBCC results for 'cinfo.CI_MACHAVAIL'. [SQLSTATE 01000]
> > >> > There are 0 rows in 1 pages for object 'cinfo.CI_MACHAVAIL'.
> [SQLSTATE 01000]
> > >> > DBCC results for 'cinfo.CI_MACHINECLASS'. [SQLSTATE 01000]
> > >> > There are 0 rows in 1 pages for object 'cinfo.CI_MACHINECLASS'.
> [SQLSTATE
> > >> > 01000]
> > >> > DBCC results for 'cinfo.CI_MACHINEGROUP'. [SQLSTATE 01000]
> > >> > There are 2 rows in 1 pages for object 'cinfo.CI_MACHINEGROUP'.
> [SQLSTATE
> > >> > 01000]
> > >> > DBCC results for 'cinfo.CI_MACHINV'. [SQLSTATE 01000]
> > >> > There are 2 rows in 1 pages for object 'cinfo.CI_MACHINV'. [SQLSTATE
> 01000]
> > >> > DBCC results for 'cinfo.CI_NEXTID'. [SQLSTATE 01000]
> > >> > There are 1 rows in 1 pages for object 'cinfo.CI_NEXTID'. [SQLSTATE
> 01000]
> > >> > DBCC results for 'cinfo.CI_RESTRICTIONS'. [SQLSTATE 01000]
> > >> > There are 0 rows in 1 pages for object 'cinfo.CI_RESTRICTIONS'.
> [SQLSTATE
> > >> > 01000]
> > >> > DBCC results for 'cinfo.CI_RIGHTROLES'. [SQLSTATE 01000]
> > >> > There are 145 rows in 1 pages for object 'cinfo.CI_RIGHTROLES'.
> [SQLSTATE
> > >> > 01000]
> > >> > DBCC results for 'cinfo.CI_RUNTIMEIMAGE'. [SQLSTATE 01000]
> > >> > There are 2080 rows in 101 pages for object 'cinfo.CI_RUNTIMEIMAGE'.
> > >> > [SQLSTATE 01000]
> > >> > DBCC results for 'cinfo.CI_SCHEDULES'. [SQLSTATE 01000]
> > >> > There are 0 rows in 1 pages for object 'cinfo.CI_SCHEDULES'.
> [SQLSTATE 01000]
> > >> > DBCC results for 'cinfo.CI_SECRIGHTS'. [SQLSTATE 01000]
> > >> > There are 1397 rows in 12 pages for object 'cinfo.CI_SECRIGHTS'.
> [SQLSTATE
> > >> > 01000]
> > >> > DBCC results for 'cinfo.CI_SPECIALDATES'. [SQLSTATE 01000]
> > >> > There are 0 rows in 1 pages for object 'cinfo.CI_SPECIALDATES'.
> [SQLSTATE
> > >> > 01000]
> > >> > DBCC results for 'cinfo.CI_SPECIALDAYS'. [SQLSTATE 01000]
> > >> > There are 0 rows in 1 pages for object 'cinfo.CI_SPECIALDAYS'.
> [SQLSTATE
> > >> > 01000]
> > >> > DBCC results for 'cinfo.CI_TEMPLATEDATES'. [SQLSTATE 01000]
> > >> > There are 458 rows in 4 pages for object 'cinfo.CI_TEMPLATEDATES'.
> [SQLSTATE
> > >> > 01000]
> > >> > DBCC results for 'cinfo.CI_TEMPLATEDAYS'. [SQLSTATE 01000]
> > >> > There are 143 rows in 1 pages for object 'cinfo.CI_TEMPLATEDAYS'.
> [SQLSTATE
> > >> > 01000]
> > >> > DBCC results for 'cinfo.CI_TEMPLATES'. [SQLSTATE 01000]
> > >> > There are 9 rows in 1 pages for object 'cinfo.CI_TEMPLATES'.
> [SQLSTATE 01000]
> > >> > DBCC results for 'cinfo.CI_TIMEINFO'. [SQLSTATE 01000]
> > >> > There are 0 rows in 1 pages for object 'cinfo.CI_TIMEINFO'. [SQLSTATE
> 01000]
> > >> > DBCC results for 'cinfo.CI_USERS'. [SQLSTATE 01000]
> > >> > There are 51 rows in 5 pages for object 'cinfo.CI_USERS'. [SQLSTATE
> 01000]
> > >> > DBCC results for 'cinfo.CI_CHANNEL_INFO'. [SQLSTATE 01000]
> > >> > There are 0 rows in 1 pages for object 'cinfo.CI_CHANNEL_INFO'.
> [SQLSTATE
> > >> > 01000]
> > >> > DBCC results for 'cinfo.CI_ARCHIVEDOBJECTS'. [SQLSTATE 01000]
> > >> > There are 0 rows in 1 pages for object 'cinfo.CI_ARCHIVEDOBJECTS'.
> [SQLSTATE
> > >> > 01000]
> > >> > DBCC results for 'dtproperties'. [SQLSTATE 01000]
> > >> > There are 0 rows in 1 pages for object 'dtproperties'. [SQLSTATE
> 01000]
> > >> > CHECKDB found 0 allocation errors and 0 consistency errors in
> database
> > >> > 'cinfo'. [SQLSTATE 01000]
> > >> > DBCC execution completed. If DBCC printed error messages, contact
> your
> > >> > system administrator. [SQLSTATE 01000]
> > >> >
> > >> >
> > >> > "Paul S Randal [MS]" wrote:
> > >> >
> > >> >> Can you post the output? As far as I'm aware, the integrity check
> runs DBCC
> > >> >> CHECKDB.
> > >> >>
> > >> >> --
> > >> >> Paul Randal
> > >> >> Dev Lead, Microsoft SQL Server Storage Engine
> > >> >>
> > >> >> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> > >> >>
> > >> >> "Ron" <Ron@.discussions.microsoft.com> wrote in message
> > >> >> news:03075079-DA30-47EE-9550-E792A8E4EB1D@.microsoft.com...
> > >> >> > No different results.
> > >> >> >
> > >> >> > Because the Integrity with Indexes via the maintenance plan
> produces
> > >> >> > different output than a DBCC checkdb database, I wanted to know if
> both
> > >> >> are
> > >> >> > doing the same thing.
> > >> >> >
> > >> >> > I'm thinking of replacing the integrity with a DBCC checkdb, but
> would
> > >> >> like
> > >> >> > to know what's the difference between the two besides the output.
> > >> >> >
> > >> >> > "Paul S Randal [MS]" wrote:
> > >> >> >
> > >> >> > > What about if you manually run DBCC CHECKDB ('database') WITH
> > >> >> NO_INFOMSGS?
> > >> >> > > Do the outputs match then?
> > >> >> > >
> > >> >> > > --
> > >> >> > > Paul Randal
> > >> >> > > Dev Lead, Microsoft SQL Server Storage Engine
> > >> >> > >
> > >> >> > > This posting is provided "AS IS" with no warranties, and confers
> no
> > >> >> rights.
> > >> >> > >
> > >> >> > > "Ron" <Ron@.discussions.microsoft.com> wrote in message
> > >> >> > > news:9E360D8A-D225-45C8-A5F7-D8671E46F417@.microsoft.com...
> > >> >> > > > Is there a difference running checkdb -DBCC checkdb
> ('database') and
> > >> >> > > running
> > >> >> > > > the Integrity with Indexes option of a maintenance plan? The
> checkdb
> > >> >> > > output
> > >> >> > > > shows detail while the integrity output shows almost no
> detail.
> > >> >> > > >
> > >> >> > > > Thanks
> > >> >> > > >
> > >> >> > > > Ron
> > >> >> > >
> > >> >> > >
> > >> >> > >
> > >> >>
> > >> >>
> > >> >>
> > >>
> > >>
> > >>
> >
>
>

Sunday, March 25, 2012

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

Tuesday, February 14, 2012

Checkdb vs Integrity with indexes

Checkdb vs Integrity with indexes

check sql licence

Blog Archive

About Me