Just a couple of ideas, other than changing timeout.
-Has query been optimized with proper indexes on all WHERE conditions and/or JOINS.
-Can the query be broken down into two or more subqueries and the result sets combined.
-Is the query correct? Make sure you are executing a Cartisian Join. Try to hard-code the WHERE condition to make sure the query works.
I used these two items to solve a problem in Oracle where a query against a million record table was taking 2 hours. I got it down to 10 minutes.
in the query properties. Click on the area where the tables are shown with the Properties window open. You'll see an entry for ODBC Timeout which will be set to your default (usually 60), you can change this to 0 which will allow the query to run until it is completed.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.