I have a workflow I've been using for a few years. It has In-DB tools including Connect In-DB, Data Stream In, Join In-DB, and Data Stream Out. Some normal tools are used prior to the Data Stream In tool which is set to create a temporary table, which is then joined In-DB with other data and so on.
The Data Stream In tool works if I copy JUST the Data Stream In and its upstream tools to another workflow and run it. However, in the larger workflow, it just runs for hours and never loads the data (normally the workflow takes a minute or two). It appears to be stopping at the Data Stream In tool based on putting Browse In-DB tools everywhere and seeing where the data is and isn't.
I did recently upgrade my computer and have to re-do all the database connections with the new tool (that was... fun...), but as I mentioned above the Data Stream In tool works with the new connections, just not when it's in the larger workflow!
I can't really share a workflow since it's all based on my company's databases and I'm not sure how to generalize. I'm not really sure how to troubleshoot this issue. Unfortunately I have minimal support internally for this kind of thing, and none at my organization for Alteryx. I appreciate any help or tips, I'm stuck on this one!
So there are a few reasons this could be happening:
1) AMP is misdirecting where your workflow error is occuring -> datastream-in is a sideeffect.
2) there is a field type which is different (or no data) in your workflow flowing to your Datastream-In. I would focus here. I would dump those browse In-DB tools because they are just extra queries and taking up space.
3) There is a permission difference between what you are running individually and what you are running in your workflow (double check the database set up).
I'd probably start by putting a select records tool (or sample tool) before my Datastream-in. Add an auto-field. Limit the data to 100 (or 100000) records. test. see if that helps. Add an output data tool to write a .yxdb next to your Datastream-in. Check if that works. If that's all working -> turn on your odbc logs in your odbc 64 config and then see what's happening.
User | Count |
---|---|
106 | |
85 | |
76 | |
54 | |
40 |