Is it advisable to use dynamic caching with a mapping that will decide on insert or update?
There are currently 997 thousand rows with 1 column primary key, 10 columns
I have another strategy that has 88 million rows with 1 column primary key, 25 columns.
Both I think would benefit by using the dynamic cache as I am the only insert update source.
Thanks As Always,
Thank You Nithya,
I need more clarification on this. As I understand, dynamic caching has to update RAM "cache" while it also updates Database, so this is two writes as aposed to updating only the Database in a static cache. If my information is accurate... My understanding is in conflict with improved performance.
This is a good question...I am sure you might be knowing about the basic purpose of Dynamic caching ( update the cache file during the load itself). Also, Dynamic lookup would do a column by column comparison to check if there is any difference is data bewteen incoming source and target column data. Updates are always a burden on database. By using dynamic lookup cache, you can avoid any unnecessary updates on the table. I beleive that this way, you can make better use of avialable resources.
hope this helps you a bit.