On 2008 Feb 22, at 8:10, Ron wrote:
I am trying to export a table to a .mer format: 6100 records, takes
HOURS!
Any recourse to this?
In my experience, the SORT of thing that takes a really long time
involves long strings of relationships, the sort where the foot
bone's connected to the ankle bone, the ankle bone's connected to the
shin bone, the shin bone's connected to the knee bone, the knee
bone's connected to the thigh bone, the thigh bone's connected to the
hip bone, the hip bone's connected to the back bone, and the back
bone's connected to the head bone. Then the head bone needs to know
what's going on down there at the foot bone.
Anything you can do to short-circuit such long strings will help.
Another thing that MAY cause this kind of slowdown is when your
calculated fields are being done "From the context of" some table
other than the native table in which they're defined. Eyeball each of
your calculation fields to be sure that the table listed in "Evaluate
from the context of" matches the table used for the fields in the
calculation itself, unless you have a REALLY good reason to do
otherwise.
Also, to the extent that you're capable of storing things as indexed,
that'll speed things up.
A minor thing to look for is whether your output character set
matches the platform you're on. Sometimes the Mac character set
doesn't speak clearly to the Windows operating system, and vice versa
(tho this is unlikely to result in the kind of massive slowdown
you're experiencing).
Finally, if you're so inclined, run a scalability test. Try exporting
6 records, then 61, then 610, and see if the time it takes increases
linearly or exponentially. That'll help indicate how much churn is
going on.