Question : SET ANSI_WARNINGS OFF - SQL 2005

I would like some advice on the SET ANSI_WARNINGS OFF.

I had a pretty complex query that was returning the "String or binary data would be truncated" error message so I dropped in SET ANSI_WARNINGS OFF. What (if any) are my issues with using this statement? Is there a more simple way of identifying the "String or binary data would be truncated" error message? Is it possible to see the truncated records to pin point what was the problem? I know there are alot of SQL gurus on this board ... so what I'm hoping for is a shortcut to get me past this message and advice on the pro's and con's to using the SET ANSI_WARNINGS OFF.

Answer : SET ANSI_WARNINGS OFF - SQL 2005

To my knowledge, you have to isolate the problem step by step.  

I'd simply just remove one SQL statement at a time until the problem disappears.  Then you've found the culprit SQL.  Then look for the places where truncation is likely to occur.  If need be, remove them one at a time until you get to the bottom of it.  

But it sounds, like you've arlready done that...I have no additional magic