The OneStream Community is temporarily frozen until June 29th due to the ongoing maintenance. Please read the blog post here to learn more.
Forum Discussion
Solved
Direct Connect Loads into OneStream
When loading data into OneStream, our longest workflow takes ~40 minutes to load. We would like to try to kick off the 5 direct connect loads within this workflow to start simultaneously instead of s...
Hi Kelley, we just did actually.
It is important that the workflow steps are in different workflows (different workflow steps in 1 workflow don’t run in parallel). You also need to make the load ID (the first item of your load file) dynamic.
OneStream advises to have a max of 3 in parallel per server so you could create two dm jobs to two different servers with both 3 threads (that’s what we do).
We also use the direct load (if you don’t expect tranformation issues) that is also 20 to 30% faster with large data sets.
Next to that the transformation itself is important so you could check the log after the load what takes most time. If it is the parsing or the writing to cube then parallel will help you, if it is the complex transformation then you can try to fix that in the SQL/ source.
Keep in mind that direct connects does not have a drill back capability, also it is kind of like an all-or-nothing sort of load. If you got level 2 data units in multiple workflows that need to be sibling workflow profiles (similar to what is there currently).
Shameless plug: We do have a chapter on direct connects in our upcoming book.
Thank you Celvin. Do you need a “proofreader” for that chapter? LOL!
I meant direct load (not direct connect). It only keeps one Table in Stage (only summary is kept).
