HELP! Maintenance plan failure on ARITHABORT and QUOTED_IDENTIFIER

This has been going on for some time now. The only significant db change we
can track it to time-wise is the creation of a schema bound view for a
temporary project. This has since been deleted but the error continues so
we don't believe there to be any relation. I include the result of our
maintenance plan log here. I do not understand how it got so far into the
index rebuilds if the error is truly correct as these are database options
not table options.
Does anyone have any idea why these errors would be generated' I'm quite
concerned. I manually rebuilt the indexes from the last table listed
through all other tables in the database and received no errors.
Greatly appreciate any ideas you may have...
[1] Database IBOTree: Index Rebuild (leaving 10%% free space)...
Rebuilding indexes for table 'atempdnrefunds'
Rebuilding indexes for table 'Audit1'
Rebuilding indexes for table 'BellevueDN2004Refunds'
Rebuilding indexes for table 'helpsql'
Rebuilding indexes for table 'IBONumbersUsed'
Rebuilding indexes for table 'IBOPasswords'
Rebuilding indexes for table 'IBOTree'
Rebuilding indexes for table 'IBOTreeWithNames'
Rebuilding indexes for table 'kateupdate'
Rebuilding indexes for table 'New Table'
Rebuilding indexes for table 'Resultss'
Rebuilding indexes for table 'tblAddressQueries'
Rebuilding indexes for table 'tblAppControl'
Rebuilding indexes for table 'tblAppModules'
Rebuilding indexes for table 'tblAttendeeLegCounter'
Rebuilding indexes for table 'tblBAccomodations'
Rebuilding indexes for table 'tblBAppHotel'
Rebuilding indexes for table 'tblBApplication'
Rebuilding indexes for table 'tblBAppLocations'
Rebuilding indexes for table 'tblBAttendeeMeetings'
Rebuilding indexes for table 'tblBAttendees'
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 1934: [Microsoft]&#
91;ODBC SQL
Server Driver][SQL Server]DBCC failed because the following SET options
have
incorrect settings: 'QUOTED_IDENTIFIER, ARITHABORT'.You have a table with a calculated column or possible an indexed view.
These need certain SET conditions to be set when you access them in order
for them to work properly. The maintenance wizard can not deal correctly
with those. The solution is to create your own Reindex job that has the
settings properly set.
Andrew J. Kelly SQL MVP
"Tim Greenwood" <tim_greenwood@.yahoo.com> wrote in message
news:OzPUQRSXEHA.3988@.tk2msftngp13.phx.gbl...
> This has been going on for some time now. The only significant db change
we
> can track it to time-wise is the creation of a schema bound view for a
> temporary project. This has since been deleted but the error continues so
> we don't believe there to be any relation. I include the result of our
> maintenance plan log here. I do not understand how it got so far into the
> index rebuilds if the error is truly correct as these are database options
> not table options.
> Does anyone have any idea why these errors would be generated' I'm quite
> concerned. I manually rebuilt the indexes from the last table listed
> through all other tables in the database and received no errors.
> Greatly appreciate any ideas you may have...
> [1] Database IBOTree: Index Rebuild (leaving 10%% free space)...
> Rebuilding indexes for table 'atempdnrefunds'
> Rebuilding indexes for table 'Audit1'
> Rebuilding indexes for table 'BellevueDN2004Refunds'
> Rebuilding indexes for table 'helpsql'
> Rebuilding indexes for table 'IBONumbersUsed'
> Rebuilding indexes for table 'IBOPasswords'
> Rebuilding indexes for table 'IBOTree'
> Rebuilding indexes for table 'IBOTreeWithNames'
> Rebuilding indexes for table 'kateupdate'
> Rebuilding indexes for table 'New Table'
> Rebuilding indexes for table 'Resultss'
> Rebuilding indexes for table 'tblAddressQueries'
> Rebuilding indexes for table 'tblAppControl'
> Rebuilding indexes for table 'tblAppModules'
> Rebuilding indexes for table 'tblAttendeeLegCounter'
> Rebuilding indexes for table 'tblBAccomodations'
> Rebuilding indexes for table 'tblBAppHotel'
> Rebuilding indexes for table 'tblBApplication'
> Rebuilding indexes for table 'tblBAppLocations'
> Rebuilding indexes for table 'tblBAttendeeMeetings'
> Rebuilding indexes for table 'tblBAttendees'
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 1934: [Microsoft][ODB
C
SQL
> Server Driver][SQL Server]DBCC failed because the following SET options[/vbcol
]
have[vbcol=seagreen]
> incorrect settings: 'QUOTED_IDENTIFIER, ARITHABORT'.
>
>|||Thanks for the quick response. Indeed the table it fails at has several
calculated columns. I guess what confuses me is I would have assumed the
maintenance wizard was using the same dbcc dbreindex functionality that I
use from my own jobs which work fine.
Thanks again
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:eE9kesSXEHA.2636@.TK2MSFTNGP10.phx.gbl...
> You have a table with a calculated column or possible an indexed view.
> These need certain SET conditions to be set when you access them in order
> for them to work properly. The maintenance wizard can not deal correctly
> with those. The solution is to create your own Reindex job that has the
> settings properly set.
> --
> Andrew J. Kelly SQL MVP
>
> "Tim Greenwood" <tim_greenwood@.yahoo.com> wrote in message
> news:OzPUQRSXEHA.3988@.tk2msftngp13.phx.gbl...
change[vbcol=seagreen]
> we
so[vbcol=seagreen]
the[vbcol=seagreen]
options[vbcol=seagreen]
quite[vbcol=seagreen]
> SQL
> have
>|||It does use the same DBCC but it sets it's environment incorrectly and it's
hard coded.
Andrew J. Kelly SQL MVP
"Tim Greenwood" <tim_greenwood@.yahoo.com> wrote in message
news:u82%23pAVXEHA.4000@.TK2MSFTNGP09.phx.gbl...
> Thanks for the quick response. Indeed the table it fails at has several
> calculated columns. I guess what confuses me is I would have assumed the
> maintenance wizard was using the same dbcc dbreindex functionality that I
> use from my own jobs which work fine.
> Thanks again
>
> "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
> news:eE9kesSXEHA.2636@.TK2MSFTNGP10.phx.gbl...
order[vbcol=seagreen]
correctly[vbcol=seagreen]
> change
continues[vbcol=seagreen]
> so
our[vbcol=seagreen]
> the
> options
> quite
[Microsoft][ODBC[vbcol=seagreen]
options[vbcol=seagreen]
>sql