Databases
StackOverflow2013
Postsdbo
POMS Access data export performance is horrible
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POMS Access data export performance is horrible
    primarykey
    data
    text
    <p>I'm using Access 2007. I have a query that accesses a table with a few hundred thousand records in it, which I am joining to another table via an inner join based on two fields. The joining fields are indexed in both tables, and the sort column is also indexed. When I run the query straight up, the result set opens up in about 2 seconds or less. When I try to Export the query results (via right-click, Export, to Text), Access spends (quite literally) hours doing I-don't-know-what before it brings up the export wizard. And then when I make the required changes to the format (making it tab-delimited instead of comma/quote), that's another several hours for the change to take place before I can click the "Start the Export" button, which of course takes several more hours yet. During the hours where it's sitting and thinking, it does keep the CPU pegged at about 50% activity.</p> <p>Any idea what's going on, or how I can bring this back into the realm of reasonable performance? I did reboot and run it with no other programs open, verified all my indexes, re-checked the query, re-ran it straight up (which again took ~2 seconds), and then immediately re-tried exporting it (which still hasn't presented the wizard screen after ~30 minutes).</p> <pre><code>table 1: AP_Open ID (primary key) Vend_No (indexed, dups) Vouch_No Vouch_date (indexed, dups) a bunch of other stuff CompanyCode (indexed, dups) table 2: Vendors Vend_No (indexed, dups) Vend_Name a bunch of other stuff CompanyCode (indexed, dups) query: select ap_open.vend_no, ap_open.vouch_no, ap_open.vouch_date, vendors.vend_name (etc--about 40 fields) From AP_Open INNER JOIN Vendors ON (AP_Open.companyCode = Vendors.CompanyCode) AND (AP_Open.Vend_No = Vendors.Vend_No) ORDER BY AP_Open.Vouch_date; </code></pre>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USHellion
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. COHave you installed all the fixes? For example http://support.microsoft.com/kb/957690 fixes slow export to RTF. You might like to look at : http://allenbrowne.com/access2007.html
      singulars
      1. POMS Access data export performance is horrible
      1. USFionnuala
    2. COIf you want to know what's actually going on, use SHOWPLAN -- Google on "Jet SHOWPLAN" for instructions. This will show the Jet query optimizer's execution plan.
      singulars
      1. POMS Access data export performance is horrible
      1. USDavid-W-Fenton
    3. COSomewhere along the line, there's some kind of setting that controls how many rows the export wizard looks at to guess the data types of the columns. It sounds like it's set to look at all the rows, instead of the first few. I haven't a clue where to look for that, though!
      singulars
      1. POMS Access data export performance is horrible
      1. USDavid-W-Fenton
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload