DBCC CHECKDB Problem -- sql server clients

canaries
4/29/2004 4:41:10 AM

There was nothing running. To isolate, I made a copy of
the database and renamed it. There was nothing hitting
the database when the DBCC was running during the two
different scenarios.

[quoted text, click to view]

Andrew J. Kelly
4/29/2004 7:38:08 AM

Try adding SET NOCOUNT ON at the beginning of the job step.

--
Andrew J. Kelly SQL MVP

[quoted text, click to view]

canaries
4/29/2004 8:59:05 AM

I checked out the connection properties for Query Analyzer
and used the same settings for the job. It still takes
the long time.

[quoted text, click to view]

Jacco Schalkwijk
4/29/2004 11:13:09 AM

Is there anything else running when you run the job? DBCC CHECKDB takes out
locks on the objects it checks, so it might have to wait for locks to be
released by other connections.

--
Jacco Schalkwijk
SQL Server MVP

[quoted text, click to view]

Got something to say? Click here to post a reply to this thread.

Don't see what you're looking for? Try a search.

View other messages about sql server clients

sql server clients : DBCC CHECKDB Problem