Maintenance Plan Failure

SQL Server 2000 sp3a, running on Windows 2003 server, sp1.
I have two jobs, based on maintenance plans, that have been running fine for
over two years. One updates statistics for a database, and the other rebuilds
indexes. Yesterday, they both started failing. The only info I can get is
from the Maintenance Plan History, both messages are similar:
[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'.
and
[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'.
quoted_identifier is set to 1, and has not been changed. Nothing has changed
at all with the database and server.
I created two new plans to duplicate the above, and each of them fails with
the same messages.
I have no clue as to why these all of a sudden started to fail, and any
assistance would be greatly appreciated.
TomTSorry for the double post, I got a message saying the post was unsuccessful,
and posted again (and got the same message, by the way)...
"TomT" wrote:
> SQL Server 2000 sp3a, running on Windows 2003 server, sp1.
> I have two jobs, based on maintenance plans, that have been running fine for
> over two years. One updates statistics for a database, and the other rebuilds
> indexes. Yesterday, they both started failing. The only info I can get is
> from the Maintenance Plan History, both messages are similar:
> [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'.
> and
> [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'.
> quoted_identifier is set to 1, and has not been changed. Nothing has changed
> at all with the database and server.
> I created two new plans to duplicate the above, and each of them fails with
> the same messages.
> I have no clue as to why these all of a sudden started to fail, and any
> assistance would be greatly appreciated.
> TomT|||Hi Tom,
That's OK, I am composing a reply to that thread :)
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.