i previously have an experience on debugging stored procedures especially those that involve dynamic sql generation and execution.  my experience told me that debugging stored procedure of this type is better with visual studio compared to query analyzer.  i encountered a problem with query analyzer before reporting truncating varchar variables when reported in the locals window and visual studio reports a more complete variable information.

i tried both last night and to my surprise, my watch window for the dynamically generated sql string was truncated at 128 character for both query analyzer and visual studio 2003 debugger.  i used the print commands to know what's the underlying value of the query by the way.  anybody here who has confirmed this as fixed in sql server 2005 management studio or vs 2005 stored procedure debugger?

---

Posted 11-15-2006 9:42 AM by jokiz