We are seeing an 8152 truncation message on one server that is not showing
on another server. This message should be showing up as we are trying to
squeeze 9 characters into a 7 character column. As this showed up in
Acceptance testing when it works in Development I was wondering what options
could be set to stop the warning. To the best of my knowledge the stored
proc has the same ANSI settings set in both servers.

I believe that it would be the ANSI_WARNINGS setting.

Thanks

Chris

> Acceptance testing when it works in Development I was wondering what
> options could be set to stop the warning. To the best of my knowledge the
> stored proc has the same ANSI settings set in both servers.
>
> I believe that it would be the ANSI_WARNINGS setting.

ANSI_NULLS and QUOTED_IDENTIFIERS are locked in when the stored procedure is
created. However, ANSI_WARNINGS is connection specific and is typically set
at the connection level using SET ANSI_WARNINGS ON. Note that an ODBC DSNs
have a checkbox to set this so perhaps that is the difference.

--
Hope this s.

Dan Guzman
SQL Server MVP
http://weblogs.sqlteam.com/dang/

"Chris Wood" <anonymous@microsoft.com> wrote in message
news:%23zmWQB6DJHA.4720@TK2MSFTNGP02.phx.gbl...
> We are seeing an 8152 truncation message on one server that is not showing
> on another server. This message should be showing up as we are trying to
> squeeze 9 characters into a 7 character column. As this showed up in
> Acceptance testing when it works in Development I was wondering what
> options could be set to stop the warning. To the best of my knowledge the
> stored proc has the same ANSI settings set in both servers.
>
> I believe that it would be the ANSI_WARNINGS setting.
>
> Thanks
>
> Chris
>

Thanks Dan.

The only difference I can see is that development is using Standard Edition
and the acceptance server is using Enterprise Edition. Could this make the
difference?

Thanks

Chris

"Dan Guzman" <guzmanda@nospam-online.sbcglobal.net> wrote in message
news:upws1AEEJHA.680@TK2MSFTNGP03.phx.gbl...
>> Acceptance testing when it works in Development I was wondering what
>> options could be set to stop the warning. To the best of my knowledge the
>> stored proc has the same ANSI settings set in both servers.
>>
>> I believe that it would be the ANSI_WARNINGS setting.
>
> ANSI_NULLS and QUOTED_IDENTIFIERS are locked in when the stored procedure
> is created. However, ANSI_WARNINGS is connection specific and is
> typically set at the connection level using SET ANSI_WARNINGS ON. Note
> that an ODBC DSNs have a checkbox to set this so perhaps that is the
> difference.
>
> --
> Hope this s.
>
> Dan Guzman
> SQL Server MVP
> http://weblogs.sqlteam.com/dang/
>
> "Chris Wood" <anonymous@microsoft.com> wrote in message
> news:%23zmWQB6DJHA.4720@TK2MSFTNGP02.phx.gbl...
>> We are seeing an 8152 truncation message on one server that is not
>> showing on another server. This message should be showing up as we are
>> trying to squeeze 9 characters into a 7 character column. As this showed
>> up in Acceptance testing when it works in Development I was wondering
>> what options could be set to stop the warning. To the best of my
>> knowledge the stored proc has the same ANSI settings set in both servers.
>>
>> I believe that it would be the ANSI_WARNINGS setting.
>>
>> Thanks
>>
>> Chris
>>
>

> The only difference I can see is that development is using Standard
> Edition and the acceptance server is using Enterprise Edition. Could this
> make the difference?

I can't think of what the edition would make a difference here. You might
check sys.dm_exec_sessions in both environments to verify the session
settings are as expected.

--
Hope this s.

Dan Guzman
SQL Server MVP
http://weblogs.sqlteam.com/dang/

"Chris Wood" <anonymous@microsoft.com> wrote in message
news:%23gwxOy1EJHA.4712@TK2MSFTNGP02.phx.gbl...
> Thanks Dan.
>
> The only difference I can see is that development is using Standard
> Edition and the acceptance server is using Enterprise Edition. Could this
> make the difference?
>
> Thanks
>
> Chris
>
> "Dan Guzman" <guzmanda@nospam-online.sbcglobal.net> wrote in message
> news:upws1AEEJHA.680@TK2MSFTNGP03.phx.gbl...
>>> Acceptance testing when it works in Development I was wondering what
>>> options could be set to stop the warning. To the best of my knowledge
>>> the stored proc has the same ANSI settings set in both servers.
>>>
>>> I believe that it would be the ANSI_WARNINGS setting.
>>
>> ANSI_NULLS and QUOTED_IDENTIFIERS are locked in when the stored procedure
>> is created. However, ANSI_WARNINGS is connection specific and is
>> typically set at the connection level using SET ANSI_WARNINGS ON. Note
>> that an ODBC DSNs have a checkbox to set this so perhaps that is the
>> difference.
>>
>> --
>> Hope this s.
>>
>> Dan Guzman
>> SQL Server MVP
>> http://weblogs.sqlteam.com/dang/
>>
>> "Chris Wood" <anonymous@microsoft.com> wrote in message
>> news:%23zmWQB6DJHA.4720@TK2MSFTNGP02.phx.gbl...
>>> We are seeing an 8152 truncation message on one server that is not
>>> showing on another server. This message should be showing up as we are
>>> trying to squeeze 9 characters into a 7 character column. As this showed
>>> up in Acceptance testing when it works in Development I was wondering
>>> what options could be set to stop the warning. To the best of my
>>> knowledge the stored proc has the same ANSI settings set in both
>>> servers.
>>>
>>> I believe that it would be the ANSI_WARNINGS setting.
>>>
>>> Thanks
>>>
>>> Chris
>>>
>>
>
>