Home/ Questions/Q 7065549
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-28T04:58:11+00:00

this error showed up in C# code, while using a Stored proc on SQL

  • 0

this error showed up in C# code, while using a Stored proc on SQL 2005. The error not showing up while running the stored proc from mgmt studio. so far it sounds some like casting issues b/w stored procedure ‘s returend value vs C# usage…

The WEIRD THING is, when i just recomiled the SP, NO CHANGE DONE only ran the ALTER proc command again with 0 changs, and the error disappeared in the C# code.
does that make any sense? that just recomiling the SP caused the error to disappear.
thanks.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    When a stored procedure is defined, a number of key SET statements in play are burned into that sproc (so that it behaves the same for callers). This can impact the behaviour of the sproc; suppressing warnings, causing errors, causing different behaviour, causing it to not trust persisted-calculated-indexed columns (and recalc per row), etc.

    It sounds to me like the SET statements in play when it was originally created were not suitable; by recreating it you set them to whatever was active the second time. Same TSQL; same sproc – but different SET options: different outcome.

    Since the SET options can be set as defaults in SSMS, this might mean whoever created it the first time had a non-standard setup.

    In particular, this affects ANSI_NULLS and QUOTED_IDENTIFIER.

    • 0