Reply to thread

Message: [QUOTE="Sylvain Lafontaine, post: 10155402"] You can solve the time-out by increasing the maximum time allowed. I don't know MS Project, so I cannot tell you how to increase this time-out. However, in your case, maybe you have a problem on the server side because of a missing index. If SQL-Server is doing a full table scan because of a missing index on either RESC.func_biz_num or SCH.TIME_FY_DATE; this could explains a lot. Using these two indexes as the clustering index for the tables could also change a lot of thing in term of performance. Not using a clustering index or using it exclusively for the primary key is not necessarily the best thing to do. You should absolutely run these queries in the Query Analyser or the SQL-Server Management Studio to take a look at the query plans generated by SQL-Server for each of these cases. Make sure also that the statistics have been updated and that the query plan cache has been purged. [/QUOTE]