When working with TSQL I often get ambiguous error messages which would be more helpful if they referred to the exact code location or statement causing the error. For example "Please check your syntax and database connectivity". Is there a good way to debug or Trace generic error messages like this?
I read about the Trace feature but it looks too complicated for me: Help with SQL Trace