First of all sorry with my english. I have a VB6 application running with a SQL SERVER 2005 SP2 (on WINDOWS 2003). The application connect to SQL with sqlncli library, like: "Provider=SQLNCLI;Data Source=xxxx;Initial Catalog=xxxx;User Id=xxxx;Password=xxxx;" .CursorLocation = adUseClient .ConnectionTimeout = 20 All work fine, but in some moments, some SPs (3 or 4) starts to receive Time Out (only under the application). If i execute them with QA and same parameters they run excellent, but under application i received Time Out. The SPs are huge SELECTs with some SubConsultants. The selects are over (aprox) 20 tables, some with 1.000 files others with 10.000 and one with 1.000.000 files. Using SQL Profiler, the Selects (SPs) show (average, when run OK): CPU: 1400, Reads: 191.000, writes: 0, Duration: 7.000 and show (average, when NOT run OK): CPU: 1.190.000, Reads: 21.165.000, writes: 0, Duration: 4.700.000 When TimeOut appears, it only disappears doing a Full Maintenance of the database (Shrink, ReIndex, StatsUpdate, etc). But somethimes SPs starts to work again without do anything! [:S]. I dontÂ´t undestandt why if under application i received TimeOut, at same time under QA i can run SP without any problem! The database have: about 800MB, 150MB FreeSpace, AutoClose FALSE, Auto Create Statistics: TRUE, Auto Shrink: FALSE, Auto Update Statistics: TRUE, Auto Update Statistics Async.: FALSE Thanks, i hope someone help me. Predo!