enter image description hereI was running SQL Server 2016 SP3 with 2022/06/13 GDR. The new GDR on 2023/02/14 came out - I applied it on May 4th. My integrity scan SQL Agent Job went from 5 mins to 20+ overnight. Nothing else changed. Anyone else seen these issue? DBs on this server here are low usage.... SQL Sentry repository and some once a year used HANA transaction simulators. So its not like some DB doubled in size.

  • How does one add a screen shot to this question/post? It help explains the issue.
    – sherveyj
    May 12, 2023 at 16:14
  • I rebooted server yesterday - still same type of 22+ min runtime.
    – sherveyj
    May 13, 2023 at 15:13
  • To troubleshoot, you may find sp_WhoIsActive helpful, which you can run while the integrity checks are running. With it, you can see what the integrity checks are waiting on and if anything is blocking them. If you find anything relevant, you should add it to your Post. Alternatively, you may find reaching out to Microsoft Support would be your best bet for an answer here.
    – J.D.
    May 14, 2023 at 12:51

1 Answer 1


Yes - I use sp_whoisactive and sp_blitz* utilities from Machanic, Ozar/Darling. But it only shows standard IO waits on the checkdb. I ran the SQL Agent job manually during daytime hours and its 8mins 40 secs. So I'm closing this. I dont think its a GDR issue. And not spending $500 for a case with MS.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.