I think this is related to SQL Server. Basically, if I go in my Hit table, I see that this first hit takes 5 seconds instead of 0.2 second. That is the time the hit took to be processed. So, it went immediately in the hit but took longer to execute. I will activate a SQL trace and see how it goes the next time. So, on that particular SQL Server, there could be a setting that forces it to go to sleep if no hit against SQL Server has been done within two minutes. Could that be?