Results 1 to 3 of 3
  1. #1
    Join Date
    Apr 2006

    Red face Unanswered: Integrity check and optimization job failed

    I found the following error in my maintenance plan please help me on this

    Under maintenace plan history i found this error:-

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

    and jobs failed with following error

    i found this error in job history of optimization & integrity check jobs:-

    Executed as user: XXXX\admin. sqlmaint.exe failed. [SQLSTATE 42000] (Error 22029). The step failed.

    Please help me find out the solution

    Thanks in advance



  2. #2
    Join Date
    Nov 2004
    on the wrong server
    Provided Answers: 6
    do not use maintenance plans. setup your own jobs for this stuff. easier to troubleshoot and you have more granular control.
    “If one brings so much courage to this world the world has to kill them or break them, so of course it kills them. The world breaks every one and afterward many are strong at the broken places. But those that will not break it kills. It kills the very good and the very gentle and the very brave impartially. If you are none of these you can be sure it will kill you too but there will be no special hurry.” Earnest Hemingway, A Farewell To Arms.

  3. #3
    Join Date
    Jun 2003
    Provided Answers: 1
    This error isn't caused by the maintenance plan, but rather occurs within the job the maintenance plan creates. The error is generated by UPDATE STATISTICS, and in my experience is related to attempts to update the stats on a table that is used to record or maintain table statistics (such as a table within the msdb database). Unfortunately, I have not been able to reliably reproduce the problem in order to debug it. When I run UPDATE STATS on the offending table a second time, it always completes succesfully. So far, it has not bothered my enough to make me want to delve into it any deeper.
    If it's not practically useful, then it's practically useless.

    blindman "sqlblindman"

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts