title: Is connection pooling a must-have in ODP.NET?
body: <p>I am writing a nightly job to move data from SQL Server to Oracle using ODP.NET.</p>
  
  <p>We use around 100 connection objects(independent of data) and we don't expect more than 1500 rows to transfer in a single run(in total).
  The ODP.NET notes and materials I read never talk about keeping connection pooling off.</p>
  
  <p>In dev, I keep the connection pooling off and it just works fine.</p>
  
  <p>Is it advisable in the given scenario to keep the connection pooling off,(given all the connections are disposed properly after use)since:</p>
  
  <ol>
  <li><p>It is a nightly job and there wont be much load on the Oracle server.</p></li>
  <li><p>Connection Pooling might return stale connections, for which validate settings/exception handing needs to be done.</p></li>
  </ol>