title: Asp.Net App Pool Overlapped Recycling Timing?
body: <p>As best I can tell when a worker process recycles:</p>
  
  <p>a) a new one spins up before the old one shuts down
  b) the old one shuts down once all the active requests its servicing completes</p>
  
  <p>Is the above accurate?</p>
  
  <p>If so, I have data that I store in SQL once Application_End() fires from the global.ascx file. I pull this data back in when Application_Start() fires.</p>
  
  <p>The problem is based on my testing, the new worker process fires the Application_Start() before my old worker process gets a chance to complete its Application_End().</p>
  
  <p>What are best practices for handling this situation?</p>
  
  <p>cheers in advance</p>
  
  <p>edit: I just noticed a feature on IIS 7 'Disabled Overlapped Recycle' - I'm guessing this is the best route</p>