title: Should database insertions, updates and deletions be wrapped in try/catch?
body: <p>I always use a try catch when i am dealing with database related operations for eg.</p>
  
  <pre><code>try
  {
   DataContext.AddtoObjectname(obj);
   DataContext.SaveChanges();
  }
  catch(Exception e)
  {
   throw new Exception("Problems adding object" + e);
  }
  </code></pre>
  
  <p>But I read about try/catch affecting performance here - <br>
  <a href="https://stackoverflow.com/questions/1308432/do-try-catch-blocks-hurt-performance-when-exceptions-are-not-thrown">Do try/catch blocks hurt performance when exceptions are not thrown?</a><br>
  So should I add try catch for something I am doing above or should i opt otherwise.Thanks for your help.</p>