Post reply

SQL 2016 SP3 CHECKDB WITH EXTENDED_LOGICAL_CHECKS problem.

  • September 19, 2021 at 6:37 pm

    #3930980

    I got the same on SQL 2019 with latest CU12.

    DBCC CHECKDB ([msdb]) WITH NO_INFOMSGS, ALL_ERRORMSGS, DATA_PURITY;

    PRINT @@ERROR;

    -- result: 0

    DBCC CHECKDB ([msdb]) WITH NO_INFOMSGS, ALL_ERRORMSGS, DATA_PURITY, EXTENDED_LOGICAL_CHECKS;

    PRINT @@ERROR;

    -- result: 2706

    • This reply was modified 4 years, 1 months ago by sterling3721.

  • September 20, 2021 at 9:41 am

    #3931082

    You are right. I missed it because our two SQL2019 servers were created after I had spotted the problem in SQL2017 so used the test restore routine which ignored error 2706.

    I have also noticed that the error is there again in SQL2017 CU26.

     

Viewing 2 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply