Hello Group!
According to to KB article 301292
(http://support.microsoft.com/?kbid=301292), I have to set ARITHABORT,
CONCAT_NULL_YIELDS_NULL, QUOTED_IDENTIFIER, ANSI_NULLS, ANSI_PADDING, and
ANSI_WARNINGS to ON and NUMERIC_ROUNDABORT to OFF to be able to run DBCC
commands on tables with Indexes On Computed Columns.
.
It seems that this applies to Maintenance Plans as well. Is there a way to
fix that? How can I set those to the Connection SQL Agent is using?
I would not like to have to run a lot of script. All the ease in the
maintenance would go away...
Thanks,
Giovanni BassiThe only real fix that I know of right now is to create your own scheduled
job with your own DBCC's. That way you can do it any way you like.
--
Andrew J. Kelly
SQL Server MVP
"Giovanni Bassi" <gbassi@.coair.com> wrote in message
news:%23gHqrpTrDHA.2616@.TK2MSFTNGP09.phx.gbl...
> Hello Group!
> According to to KB article 301292
> (http://support.microsoft.com/?kbid=301292), I have to set ARITHABORT,
> CONCAT_NULL_YIELDS_NULL, QUOTED_IDENTIFIER, ANSI_NULLS, ANSI_PADDING, and
> ANSI_WARNINGS to ON and NUMERIC_ROUNDABORT to OFF to be able to run DBCC
> commands on tables with Indexes On Computed Columns.
> .
> It seems that this applies to Maintenance Plans as well. Is there a way to
> fix that? How can I set those to the Connection SQL Agent is using?
> I would not like to have to run a lot of script. All the ease in the
> maintenance would go away...
> Thanks,
> Giovanni Bassi
>|||That's the problem, Andrew. Then I loose all the ease of the maintenance
plans...
Microsoft should had thought of that...
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:%23Zla7yTrDHA.2480@.TK2MSFTNGP10.phx.gbl...
> The only real fix that I know of right now is to create your own scheduled
> job with your own DBCC's. That way you can do it any way you like.
> --
> Andrew J. Kelly
> SQL Server MVP
>
> "Giovanni Bassi" <gbassi@.coair.com> wrote in message
> news:%23gHqrpTrDHA.2616@.TK2MSFTNGP09.phx.gbl...
> > Hello Group!
> >
> > According to to KB article 301292
> > (http://support.microsoft.com/?kbid=301292), I have to set ARITHABORT,
> > CONCAT_NULL_YIELDS_NULL, QUOTED_IDENTIFIER, ANSI_NULLS, ANSI_PADDING,
and
> > ANSI_WARNINGS to ON and NUMERIC_ROUNDABORT to OFF to be able to run DBCC
> > commands on tables with Indexes On Computed Columns.
> > .
> > It seems that this applies to Maintenance Plans as well. Is there a way
to
> > fix that? How can I set those to the Connection SQL Agent is using?
> > I would not like to have to run a lot of script. All the ease in the
> > maintenance would go away...
> >
> > Thanks,
> >
> > Giovanni Bassi
> >
> >
>|||Usually when something is easy it looses flexibility. It really only takes
a few lines of code to replace what the MP does.
--
Andrew J. Kelly
SQL Server MVP
"Giovanni Bassi" <gbassi@.coair.com> wrote in message
news:eJEC%23qcrDHA.976@.tk2msftngp13.phx.gbl...
> That's the problem, Andrew. Then I loose all the ease of the maintenance
> plans...
> Microsoft should had thought of that...
>
>
> "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
> news:%23Zla7yTrDHA.2480@.TK2MSFTNGP10.phx.gbl...
> > The only real fix that I know of right now is to create your own
scheduled
> > job with your own DBCC's. That way you can do it any way you like.
> >
> > --
> >
> > Andrew J. Kelly
> > SQL Server MVP
> >
> >
> > "Giovanni Bassi" <gbassi@.coair.com> wrote in message
> > news:%23gHqrpTrDHA.2616@.TK2MSFTNGP09.phx.gbl...
> > > Hello Group!
> > >
> > > According to to KB article 301292
> > > (http://support.microsoft.com/?kbid=301292), I have to set ARITHABORT,
> > > CONCAT_NULL_YIELDS_NULL, QUOTED_IDENTIFIER, ANSI_NULLS, ANSI_PADDING,
> and
> > > ANSI_WARNINGS to ON and NUMERIC_ROUNDABORT to OFF to be able to run
DBCC
> > > commands on tables with Indexes On Computed Columns.
> > > .
> > > It seems that this applies to Maintenance Plans as well. Is there a
way
> to
> > > fix that? How can I set those to the Connection SQL Agent is using?
> > > I would not like to have to run a lot of script. All the ease in the
> > > maintenance would go away...
> > >
> > > Thanks,
> > >
> > > Giovanni Bassi
> > >
> > >
> >
> >
>
Wednesday, March 28, 2012
Maintenance Plan does not work with calculated columns
Labels:
according,
arithabort,
article,
calculated,
columns,
concat_null_yields_null,
database,
group,
http,
kbid301292,
maintenance,
microsoft,
mysql,
oracle,
plan,
server,
sql
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment