Recent content by PeterBickford

Sigh. I've added the joint index, and it seems like it helped some folks, but not others. Anyone have any other ideas as to what might be happening?

I'm afraid it's separate indexes. Is Jet not able to take performance advantage of it in this manner? If so, does anyone know the SQL to create and drop a composite index? (Since I'd have to do patch up on the fly for existing customers). -Pete

To PHV: Thanks for the article on ShowPlan. Here's the output of that join: - Inputs to Query - Table 'Issues' Table 'Update_Issues' - End inputs to Query - 01) Sort table 'Update_Issues' 02) Sort table 'Issues' 03) Outer Join result of '01)' to result of '02)' using Merge Join...

To PCLewis: I realize the post is getting long, so you may have missed it: The Join is along Title and FullIssue, both of which are indexed varchar fields. There are memo fields in the query result set, but they aren't part of the join criteria.

I appreciate the idea on messing with the memo fields, but remember, the query I'm currently worried about (as opposed to the one I *suspect*, but can't verify may be related) exhibits this behavior only sporadically. It appears to be resource-related, and compacting *seems* to prevent it from...

I am able to recreate this (sporadically) on numerous machines, both in-house and via reports from customers. The in-house machines all undergo weekly virus checks, etc., and I feel confident they're clean. The problem (particularly with the latter database I described, assuming it's the same...

There's really no pattern that I can discern, although Compacting just before the slow run >seems< to prevent the problem (although this also involves a database close/reopen, so it's hard to tell whether the underlying condition is system resource-based, whether simply reducing the size of the...

It's on a standalone PC, with exclusive access to the tables, and only a single user. No other processor-intensive activities are running (the task in question is accounting for about 48% of the 52% CPU load throughout). There are likely only a handful (< 200 null records) <I.e., records which...

Hi folks, Working with a MS Access 2002-format database, I'm firing off the following query (VB format): SQL = "SELECT UI FROM Issues I RIGHT JOIN Update_Issues UI ON (I.FullIssue = UI.FullIssue) AND (I.Title = UI.Title)" & vbCrLf & _ "WHERE I.FullIssue IS NULL" & vbCrLf & _ "ORDER BY...