Calling DBCC CheckDB from job

• Loundy

  SSCertifiable

  Points: 6080

  More actions

  April 10, 2012 at 5:26 am

  #267148

  Hi All,

  If I call DBCC CheckDB from a JOB and the integrity check fails (for what ever reason) does the error bubble up and cause the job to fail?

  Cheers,

  [font="Times New Roman"]There's no kill switch on awesome![/font]

• spaghettidba

  SSC Guru

  Points: 105732

  More actions

  April 10, 2012 at 7:20 am

  #1471186

  Nope. You could tweak my consistency check procedure[/url] to fit your needs.

  -- Gianluca Sartori

• Loundy

  SSCertifiable

  Points: 6080

  More actions

  April 10, 2012 at 9:02 am

  #1471265

  Gianluca Sartori (4/10/2012)

  ---

  Nope. You could tweak my consistency check procedure[/url] to fit your needs.

  Thanks for the reply - nice post too.

  However, i've done some searching around and have found a nice msdn blog which suggests that an agent job will fail http://blogs.msdn.com/b/cindygross/archive/2010/06/13/dbcc-checkdb-database-integrity.aspx

  i'll do some testing by creating a test database, corrupting a page and running the checkdb command to see what happens http://www.littlekendra.com/2011/01/24/corrupthexeditor/

  [font="Times New Roman"]There's no kill switch on awesome![/font]

• Loundy

  SSCertifiable

  Points: 6080

  More actions

  April 10, 2012 at 9:56 am

  #1471311

  I can confirm that if DBCC CheckDB errors during an agent job then the agent will throw an error

  I followed the post above to corrupt a database and my job threw the error.

  This is what my job ran: EXEC sp_MSforeachdb "USE [?]; DBCC CHECKDB WITH PHYSICAL_ONLY";

  [font="Times New Roman"]There's no kill switch on awesome![/font]

• spaghettidba

  SSC Guru

  Points: 105732

  More actions

  April 10, 2012 at 3:42 pm

  #1471564

  Totally misread your question, sorry.

  I thought you wanted to avoid the job failure...

  -- Gianluca Sartori