Hi Steve, A few "first glance" suggestions... I'd always use the Joiner. With the right format it has some funky things for improving performance, such as the cache size, prefetch, and "trim key" settings. Take a look at the Joiner page on fmepedia for info on how these work. http://www.fmepedia.com/index.php/Joiner
The other thing is that in a 1:M join you are creating lists, and lists can be a big performance hit. On the ListExploder make sure you are using "List Element Attributes" as the attributes to keep, and not "All Attributes". If you use "All Attributes" then you are carrying around a complete copy of all the list information on every feature. eg match one feature to 1000 records and explode that list using "All Attributes" and you'll have 1000 features, each containing 1000 sets of attributes - that's a lot. And if you are carrying geometry columns around this way you'll kill the translation pretty quickly. You can also find some information on performance tuning on fmepedia: http://www.fmepedia.com/index.php/FME_Performance_Tuning This page has a whole lot of info on interpreting a log file to see where the time is going. It might be that the database is eating up time as well as FME. Hope this helps as a starting point. I don't know what other folk will say, they might disagree. But from my experience I believe Joiner is as efficient as any other method, Regards, Mark Mark Ireland, Senior Product Specialist Safe Software Inc. Surrey, BC, CANADA [EMAIL PROTECTED] http://www.safe.com Solutions for Spatial Data Translation, Distribution and Access --- In [email protected], "snelsons2006" <[EMAIL PROTECTED]> wrote: > > Hi guys, > My source data is a PGDB (.mdb) and I have tables that I would like > to pull data from. This PGDB contains all our Automatic Passenger > Counting information since March - so it's a pretty large DB and > it's taking a huge amount of time to read the tables I need, do some > joins using the JOINER and LISTEXPLODER - in fact my process is > crapping out now because I don't have enough space on my desktop. > > So - there's the background - here's my question. What is the most > effective way of joining tables and esp, 1:M tables using FME? I > realize that doing all the joins in workbench may not be the best, > so I'd like to try to run SQL requests because I think then the > query is handled outside of FME??? (Is this correct?). > > Should I be using SQLEXECUTOR? It seems to me that I need to have > my source DB tables as SourceDatasets in FMW, to point into the > SQLEXECUTOR. This seems to be counter productive, because it > appears FME needs to read the tables first, before it runs the > SQLEXECUTOR. Is there a better way to make all the joins? > > Thanks again everyone for any comments or suggestions, > Steve > For insights into what's up at Safe Software and what's on the development horizon, visit Safe's blog at spatial-etl.blogspot.com. Love FME? Then open your diary to March 6-7, 2008 and write this... "Second Worldwide FME User Conference - Must Attend!" See http://www.safe.com/company/fmeuc2008/index.php for more details. Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/fme/ <*> Your email settings: Individual Email | Traditional <*> To change settings online go to: http://groups.yahoo.com/group/fme/join (Yahoo! ID required) <*> To change settings via email: mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
