hide warning from query analyser

When I renaming tables,columns below message comes to Query Analayaser
Result Window.
Is there any way to hide it,
because this may hit performance if there are 1000's of columns updated
Thanks
Caution: Changing any part of an object name could break scripts and stored
procedures.
The COLUMN was renamed to 'F28'.
Caution: Changing any part of an object name could break scripts and stored
procedures.
The COLUMN was renamed to 'F27'.
Caution: Changing any part of an object name could break scripts and stored
procedures.
The COLUMN was renamed to 'F26'.
Caution: Changing any part of an object name could break scripts and stored
procedures.
The COLUMN was renamed to 'F31'.Did you try SET ANSI_WANRINGS OFF? I forget the list of warnings that this
suppresses, I know it's not all of them...
"Abraham" <binu_ca@.yahoo.com> wrote in message
news:OP9FBW1ODHA.3700@.tk2msftngp13.phx.gbl...
> When I renaming tables,columns below message comes to Query Analayaser
> Result Window.
> Is there any way to hide it,
> because this may hit performance if there are 1000's of columns updated
> Thanks
> Caution: Changing any part of an object name could break scripts and
stored
> procedures.
> The COLUMN was renamed to 'F28'.
> Caution: Changing any part of an object name could break scripts and
stored
> procedures.
> The COLUMN was renamed to 'F27'.
> Caution: Changing any part of an object name could break scripts and
stored
> procedures.
> The COLUMN was renamed to 'F26'.
> Caution: Changing any part of an object name could break scripts and
stored
> procedures.
> The COLUMN was renamed to 'F31'.
>|||that one's a raiserror, so no. Why would performance of an object rename
process be a concern?
"Aaron Bertrand - MVP" <aaron@.TRASHaspfaq.com> wrote in message
news:Oj3WJb1ODHA.704@.tk2msftngp13.phx.gbl...
> Did you try SET ANSI_WANRINGS OFF? I forget the list of warnings that
this
> suppresses, I know it's not all of them...
>
> "Abraham" <binu_ca@.yahoo.com> wrote in message
> news:OP9FBW1ODHA.3700@.tk2msftngp13.phx.gbl...
> > When I renaming tables,columns below message comes to Query Analayaser
> > Result Window.
> > Is there any way to hide it,
> > because this may hit performance if there are 1000's of columns updated
> > Thanks
> >
> > Caution: Changing any part of an object name could break scripts and
> stored
> > procedures.
> > The COLUMN was renamed to 'F28'.
> > Caution: Changing any part of an object name could break scripts and
> stored
> > procedures.
> > The COLUMN was renamed to 'F27'.
> > Caution: Changing any part of an object name could break scripts and
> stored
> > procedures.
> > The COLUMN was renamed to 'F26'.
> > Caution: Changing any part of an object name could break scripts and
> stored
> > procedures.
> > The COLUMN was renamed to 'F31'.
> >
> >
>|||I don't know of any way to turn off this message.
> because this may hit performance if there are 1000's of columns updated
If you are frequently renaming lots of columns then maybe you should rethink
whether that is really the best solution. I can't think of a reason why you
would want to do this regularly.
--
David Portas
--
Please reply only to the newsgroup
--
"Abraham" <binu_ca@.yahoo.com> wrote in message
news:OP9FBW1ODHA.3700@.tk2msftngp13.phx.gbl...
> When I renaming tables,columns below message comes to Query Analayaser
> Result Window.
> Is there any way to hide it,
> because this may hit performance if there are 1000's of columns updated
> Thanks
> Caution: Changing any part of an object name could break scripts and
stored
> procedures.
> The COLUMN was renamed to 'F28'.
> Caution: Changing any part of an object name could break scripts and
stored
> procedures.
> The COLUMN was renamed to 'F27'.
> Caution: Changing any part of an object name could break scripts and
stored
> procedures.
> The COLUMN was renamed to 'F26'.
> Caution: Changing any part of an object name could break scripts and
stored
> procedures.
> The COLUMN was renamed to 'F31'.
>