title: Any clever way to fix 'string or binary data would be truncated' warning with LINQ
body: <p>Is there a clever way to determine which field is causing 'string or binary data would be truncated' with LINQ.</p>
  
  <p>I've always ended up doing it manually by stepping through a debugger, but with a batch using 'SubmitChanges' I have to change my code to inserting a single row to find the culprit in a batch of rows. </p>
  
  <p>Am I missing something or in this day and age do I really have to still use a brute force method to find the problem.</p>
  
  <p>Please dont give me advice on avoiding this error in future (unless its something much cleverer than 'validate your data'). The source data is coming from a different system where I dont have full control anyway - plus I want to be lazy.</p>
  
  <p>PS. Does SQL Server 2008 actually tell me the field name. Please tell me it does! I'll upgrade!</p>