Error Message on optimization plan in sqlserver 2000

I am not a SQL Server DBA but trying to figure this out,
The 'OptimizationsJob For Db Maintenance Plan' is failing with an
error -- When I checked the error message the index rebuild is failing
for one of the tables with an error of
[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'.
This table "t" exists in both our Dev and Prod Servers but I see this
issue only in the Prod server (the prod server has more data)...
I ran this query:
select * from sysobjects where type = 'V'
and objectproperty(id, 'IsIndexed') = 1
for any indexed views and returns null
What are my options?
TIA,
Mag
What about computed columns. If memory serves me, it is enough to have statistics on a computed
column for this error to happen.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
<aspiring22@.gmail.com> wrote in message news:1175025577.736504.80620@.b75g2000hsg.googlegro ups.com...
>I am not a SQL Server DBA but trying to figure this out,
> The 'OptimizationsJob For Db Maintenance Plan' is failing with an
> error -- When I checked the error message the index rebuild is failing
> for one of the tables with an error of
> [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'.
>
> This table "t" exists in both our Dev and Prod Servers but I see this
> issue only in the Prod server (the prod server has more data)...
> I ran this query:
> select * from sysobjects where type = 'V'
> and objectproperty(id, 'IsIndexed') = 1
> for any indexed views and returns null
>
> What are my options?
>
> TIA,
> Mag
>
|||On Mar 27, 3:09 pm, "Tibor Karaszi"
<tibor_please.no.email_kara...@.hotmail.nomail.com> wrote:
> What about computed columns. If memory serves me, it is enough to have statistics on a computed
> column for this error to happen.
> --
> Tibor Karaszi, SQL Server MVPhttp://www.karaszi.com/sqlserver/default.asphttp://www.solidqualitylearning.com/
>
> <aspirin...@.gmail.com> wrote in messagenews:1175025577.736504.80620@.b75g2000hsg.go oglegroups.com...
>
>
>
>
> - Show quoted text -
There is no computed columns on this table and how come the DEV/Test
instance is not showing the same exception...
|||> There is no computed columns on this table and how come the DEV/Test
> instance is not showing the same exception...
That could have been because auto-statistics could have been created on the dev server but not the
prod server.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
<aspiring22@.gmail.com> wrote in message
news:1175029664.750939.316180@.p77g2000hsh.googlegr oups.com...
> On Mar 27, 3:09 pm, "Tibor Karaszi"
> <tibor_please.no.email_kara...@.hotmail.nomail.com> wrote:
> There is no computed columns on this table and how come the DEV/Test
> instance is not showing the same exception...
>