title: Should we put try catch with function if we just want to log the exception?
body: <p>In asp.net application, all the exception that occurs and are not inside try catch can be handled by application_error.</p>
  
  <p>If we just need to log the exception along with its stack trace, and we need not make any other decision/logic inside catch, why should we put try catch at application/bl or dal layer functions? Is there any reason to put try/catch with every database call function?</p>
  
  <p>For example we have hundreds of function in  DAL layer that executes following code:</p>
  
  <pre><code>try
  {
    //open db connection, execute stored procedure
  }
  catch
  {
    //log error
  }
  </code></pre>
  
  <p>In case we get any exception from stored procedure OR in opening database connection, we get an exception but we are not doing anything except for logging these errors. We don't have very critical data-storage/retrieval requirement. We are logging error just to be alerted and fix it later. Is this correct to put catch in every such function?</p>