RE: Processing thousands of records
- From: Jerry Whittle <JerryWhittle@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 21 Aug 2008 08:16:02 -0700
How long is 'forever' in this case?
The first thing that affect performance is how well the database is
designed. Are the tables properly normalized?
Next could be the query itself. There are a few tricks of the trade like
trying an Exists clause instead of an In clause. The flip side is that
sometimes the In will work better than the Exists so you need to try it both
ways. Then there is differences between UNION and UNION ALL queries. The same
goes for DISTINCT versus GROUP BY all the fields.
Then there's indexing. Do you have indexes on the fields where you have
criteria?
Show us the SQL. Open the query in design view. Next go to View, SQL View
and copy and past it here. Information on primary keys and relationships
would be a nice touch too. Also any indexes.
--
Jerry Whittle, Microsoft Access MVP
Light. Strong. Cheap. Pick two. Keith Bontrager - Bicycle Builder.
"Dave" wrote:
I have a query that someone had helped me with and it works great: However.
when I run this against 91,000 records the query runs forever.
When running queries against thousands of records, is there a tricks to do
this effectively. Obviously the process and memory limits calculations, but
are there tricks to handling a lot of data?
Thanks
Dave
- Follow-Ups:
- RE: Processing thousands of records
- From: Dave
- RE: Processing thousands of records
- From: Dave
- RE: Processing thousands of records
- Prev by Date: Re: Query returns nothing
- Next by Date: RE: Using previous data to calculate results
- Previous by thread: Re: Full Join Query/Union
- Next by thread: RE: Processing thousands of records
- Index(es):
Relevant Pages
|