Don't use a database stage for a lookup. Period. I don't care what database we're talking about, it's the least performant way to do that.
Use a hashed file. They are the heart and soul of Server jobs, so leverage them. And before you ask - no, there's absolutely no reason to put all 20M source records in it first. Put only what you need there for each run. Load the keys from your source file into a work table and use that to constrain your build sql for the hashed file.
Low performance in the access the Informix
Moderators: chulett, rschirm, roy
You missed my point... and it's not impossible, but if you want to believe that, fine.
Work on tuning the reference lookup query then, perhaps an index is in order to supprt the query? I don't believe you have any choice but to use ODBC for Informix, so do your best to make the reference lookup query as 'performant' as possible.
Work on tuning the reference lookup query then, perhaps an index is in order to supprt the query? I don't believe you have any choice but to use ODBC for Informix, so do your best to make the reference lookup query as 'performant' as possible.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
-
- Participant
- Posts: 176
- Joined: Wed Nov 15, 2006 5:48 am