>As a test, do you still get timeouts when both are set to 0? That is supposed to be infinite. Also, I read online that for ADO.NET, there is a CommandTimeout property of the command object that defaults to 30 seconds. And of course 0 means infinite. You can also set this value at application level: System.Data.IDbCommand.CommandTimeout = 50 or whatever. I'm assuming you tried that already though...

Thanks, I put 0 and it solved the issue.

I just cannot understand however what takes SQL Server so long to process at first. This is causing me a problem. It does that on the first access to all the tables. Maybe someone knows a little bit more about what could cause this and how to optimize that.