Integrity check fails yet full & transactional job successful

  • Hi Guys,

    The Integrity Check keeps failing yet the full & transactional backup job is successful.

    The error message I receive in the logs are:

    [128] Database <database name>: Check Data and Index Linkage...

    [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 1934: [Microsoft][ODBC SQL Server Driver][SQL Server]DBCC failed because the following SET options have incorrect settings: 'QUOTED_IDENTIFIER'.

    The following errors were found:

    [Microsoft][ODBC SQL Server Driver][SQL Server]DBCC failed because the following SET options have incorrect settings: 'QUOTED_IDENTIFIER'.

    ** Execution Time: 0 hrs, 0 mins, 1 secs **

    Any Ideas?

  • Indexed view and the wrong settings for quoted identifier I'm guessing.

    Can you run a manual checkDB, just to be sure the DB is clean?

    DBCC CheckDB(<Database name>) WITH No_INFOMSGS, ALL_ERRORMSGS

    If that fails with the same message, try turning quoted identifers on first then running it.

    btw, there's nothing unusual about integrity check failing and backup succeeding. Even when the integrity check fails because of corruption, there's a very good chance that the backup will succeed.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

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

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