Jim Lawrence (AccessD)
accessd at shaw.ca
Thu Jun 12 20:36:59 CDT 2003
Hi Tina: Large and complex queries are bound to start bouncing off system limits. The best way around this is to limit the query grouping and use temp files instead. The complexity is down, speed is back to normal and all that is needed is a bit of programming to manage and delete the temp files when the process is finished. This method should push a full job down to about half and hour. HTH Jim -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Tina Norris Fields Sent: Thursday, June 12, 2003 6:06 AM To: accessd at databaseadvisors.com Subject: [AccessD] Make-Table Queries Combined Hi List, A friend's company has this situation: A particular report is actually based on about 32 make-table queries. Running them one at a time works well, but requires someone to run each one in sequence. My friend combined these small queries into a big one that gathers them all together. He finds that when it gets to about the 14th query, everything slows down to a crawl. In fact, it may take up to 12 hours for the large combining query to finish its job. I don't know anything more about this situation. Does anyone here know why this happens? Is it something like the system has to keep everything in memory until the query finishes? Thanks for your thoughts. Tina _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com