Error 1934 during index rebuild

Hi,
I have SQL Server 200 SP3a running on Windows Server
2003. During the optimization setp of my maintenance
plan, I see the following error:
[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'.
I saw an article in KB about creating indices on views,
which had a similar error message. The problem that I
have does not create indices on views, though. The table
being re-indexed is very simple, not many records
(thousand or so), and has only one index, which is a
clustered index on two integer values and a date. The
cluster is set to a 90% fill factor.
Other tables are re-indexed just fine in the DB, just
this one seems to be failing. The table does have null
fields, but they are not included in the index. There is
no primary key defined on the table.
Any help is greatly appreciated.
-- Jake
jwa@.beyond-ordinary.com> I have SQL Server 200 SP3a running on Windows Server
> 2003. During the optimization setp of my maintenance
> plan, I see the following error:
> [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'.
Is that index set on a computed column? See if it helps:
PRB: SET OPTION Considerations When Running DBCC with Indexes On Computed
Columns
http://support.microsoft.com/defaul...B;en-us;q301292
sincerely,
--
Sebastian K. Zaklada
Skilled Software
http://www.skilledsoftware.com
This posting is provided "AS IS" with no warranties, and confers no rights.|||Thanks for your reply! That makes sense, but I can not seem to get the
ARITHABORT flag set during the maintenance plan. I tried setting it in
the job's command script, but that didn't seem to have an affect.
The table doesn't have an index on the computed columns, but it does
have an index on a column that is used in a more than one computed
column in the table. Would have an affect'
Thanks again!
=======================================
Jacob W Anderson
Beyond Ordinary Software Solutions
http://www.beyond-ordinary.com
jwa@.beyond-ordinary.com
=======================================
*** Sent via Developersdex http://www.examnotes.net ***
Don't just participate in USENET...get rewarded for it!|||You can't use the maintenance plan for this, you must create your own
scheduled job to do it. That way you can set the settings however you wish.
This is a know problem with the MP.
Andrew J. Kelly
SQL Server MVP
"Jacob Anderson" <jwa@.beyond-ordinary.com> wrote in message
news:%23qhZxUz8DHA.1636@.TK2MSFTNGP12.phx.gbl...
> Thanks for your reply! That makes sense, but I can not seem to get the
> ARITHABORT flag set during the maintenance plan. I tried setting it in
> the job's command script, but that didn't seem to have an affect.
> The table doesn't have an index on the computed columns, but it does
> have an index on a column that is used in a more than one computed
> column in the table. Would have an affect'
> Thanks again!
> =======================================
> Jacob W Anderson
> Beyond Ordinary Software Solutions
> http://www.beyond-ordinary.com
> jwa@.beyond-ordinary.com
> =======================================
> *** Sent via Developersdex http://www.examnotes.net ***
> Don't just participate in USENET...get rewarded for it!