ANSI_PADDING Deprecated

I have a few questions regarding the ANSI_PADDING option. I see, according
to MSDN (http://msdn2.microsoft.com/en-us/library/ms187403.aspx), that this
option is deprecated:

> This feature will be removed in a future version of Microsoft SQL
> Server. Avoid using this feature in new development work, and
> plan to modify applications that currently use this feature.
My questions are:
1) What will this setting be fixed to once it is no longer supported?
According to MSDN, their recommendation is that we always have it set to ON,
and it states the default value is also ON. So I would assume that it will
be fixed to ON once it is no longer supported, but I don't see this
explicitly stated anywhere.
2) What will happen to existing databases with columns defined with this
option turned on? Will they be converted such that the columns will have
ANSI_PADDING ON, or will the OFF setting be preserved? I would assume that
they will be converted, but again, this is not explicitly stated anywhere.
If this information is listed somewhere, please direct me to the reference.
Thanks in advance for your time.
Jerad
Thanks for your response, Tibor. I will follow your advise, and submit
feedback via BOL.
Thanks again.
Jerad
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:e$4zIM%23aHHA.2076@.TK2MSFTNGP04.phx.gbl...
> Jerad,
> 1)
> I suggest you do a feedback on that BOL page. They should document what
the setting will be when it
> is deprecated.
> I can bet a large sum that it will be ON. The Sybase heritage had the OFF
behavior, where ANSI SQL
> has the ON behavior. So, in some version (possibly 6.0) we could use this
setting to change the
> behavior. Over time, the ANSI (ON) behavior has become more and more
dominating (tools defaulting to
> this etc). Considering that some features require ON behavior (indexed
views etc), and ANSI SQL is
> ON, this will be ON when deprecated. But of course, the text should tell
us that, so I suggest you
> BOL feedback.
>
> 2) I have a feeling that no-one know at this moment what happens to
existing databases when the
> setting is deprecated. This is probably one of the things that MS need to
work out with the
> customers during beta. So, this I can understand why they can't comment on
at this moment. But I
> suggest you mention this in your BOL feedback. You never know, they might
already know what will
> happen...
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Jerad Rose" <no@.spam.com> wrote in message
news:uRheZ08aHHA.348@.TK2MSFTNGP02.phx.gbl...[vbcol=seagreen]
according to MSDN[vbcol=seagreen]
option is deprecated:[vbcol=seagreen]
According to MSDN, their[vbcol=seagreen]
default value is also ON.[vbcol=seagreen]
supported, but I don't see this[vbcol=seagreen]
option turned on? Will[vbcol=seagreen]
will the OFF setting be[vbcol=seagreen]
is not explicitly stated[vbcol=seagreen]
reference.
>
|||> I can bet a large sum that it will be ON.
Tibor, I hope someone took you up on your bet. In fact, the setting will
always be ON. The topic is unclear (Thanks, Jerad, for submitting your
feedback). What's actually being deprecated is the ability to set the option
to OFF.

> 2) I have a feeling that no-one know at this moment what happens to
> existing databases when the setting is deprecated.
Again, you're correct. The migration/upgrade story for this is likely not
firmly in place given that doesn't go into effect for another two releases.
Gail Erickson [MS]
SQL Server Documentation Team
This posting is provided "AS IS" with no warranties, and confers no rights
Download the latest version of Books Online from
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:e$4zIM%23aHHA.2076@.TK2MSFTNGP04.phx.gbl...
> Jerad,
> 1)
> I suggest you do a feedback on that BOL page. They should document what
> the setting will be when it is deprecated.
> I can bet a large sum that it will be ON. The Sybase heritage had the OFF
> behavior, where ANSI SQL has the ON behavior. So, in some version
> (possibly 6.0) we could use this setting to change the behavior. Over
> time, the ANSI (ON) behavior has become more and more dominating (tools
> defaulting to this etc). Considering that some features require ON
> behavior (indexed views etc), and ANSI SQL is ON, this will be ON when
> deprecated. But of course, the text should tell us that, so I suggest you
> BOL feedback.
>
> 2) I have a feeling that no-one know at this moment what happens to
> existing databases when the setting is deprecated. This is probably one of
> the things that MS need to work out with the customers during beta. So,
> this I can understand why they can't comment on at this moment. But I
> suggest you mention this in your BOL feedback. You never know, they might
> already know what will happen...
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Jerad Rose" <no@.spam.com> wrote in message
> news:uRheZ08aHHA.348@.TK2MSFTNGP02.phx.gbl...
>