Community Spring Cleaning week is here! Join your fellow Maveryx in digging through your old posts and marking comments on them as solved. Learn more here!

Alteryx Designer Desktop Discussions

Find answers, ask questions, and share expertise about Alteryx Designer Desktop and Intelligence Suite.

Connect In-DB appears to be caching records, not picking up changes in the underlying DB.

PaulFields2
8 - Asteroid

Help!

 

I am using a Connect In-DB Alteryx to pull records from Data Source A, see if they already exist in Data Source B, and insert those that don't.  To test the join node for each of the ~20 comparison fields I'm using, I'm making small changes to existing records in Data Source B so there won't be a full match.

 

The problem is that these changes to Data Source B are NOT being pulled in on the next run of the work flow by my Connect In-DB node.  If I delete all records from Data Source B, then I can see that change, but minor adjustments to field values for existing records aren't getting picked up.

 

What's going on (caching?), and how can I stop it?

 

Gratefully,

2 REPLIES 2
BrandonB
Alteryx
Alteryx

Are you referring to the caching in the Browse In-DB tool where you are viewing the data In-Database? https://help.alteryx.com/current/designer/browse-db-tool

 

You should be able to uncheck the box for "Enable Caching" and it will query the data from the database every time rather than the cached data

 

browse in-db.png

 

 

PaulFields2
8 - Asteroid

Found that this was caused by a DB setting to cache table content.  Even when I reset it to no-cache, it reverts to cache again after every new record.  Never seen this before and pretty odd to my way of thinking. 

 

Has ANYONE ever seen this behavior between Alteryx and Oracle?

Labels