Trouble with index job failing

  • Hi all

    I have an issue with an index job failing on a database. Neither the database, nor the job have been changed for a very long time so I don't know why it has started happening.

    The error I get is as follows and it always directly after a specific table.

    [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, ARITHABORT'.

    From what I have found on Google (I'm very new to SQL administration) this can sometimes occur when there are cacluated columns is a table? But again, the table has not (apparently) changed at all.

    The calculated fields in this table are (I got this info from the dev team):

    Est_totalcostsmain

    Est_totalcostsrun

    Est_unitcostmain

    Est_unitcostrun

    If I run this and I see that these ‘may’ be indexed ? : (in the Name column)

    select *

    FROM sysindexes

    WHERE id = OBJECT_ID('Estimates_Model')

    _WA_Sys_est_TotalCostsMain_6CAF08B9

    _WA_Sys_est_TotalCostsRun_6CAF08B9

    _WA_Sys_est_UnitCostMain_6CAF08B9

    _WA_Sys_est_UnitCostRun_6CAF08B9

    I'm not sure how to fix/work around this issue. Can anyone point me in the right direction?

    Many thanks in advance

    Farren Minns

  • The entries in sysindexes for those columns are actually auto created column statistics, not indexes. SQL Server will build statistics for non-indexed columns when those columns are in a JOIN or WHERE clause.

    Have you upgraded MDAC recently?

    You can change some of the SET options in the ODBC configuration manager.

  • Check http://support.microsoft.com/?kbid=902388

    HTH!

    MJ

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

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