Additional Blogs by Members
cancel
Showing results for 
Search instead for 
Did you mean: 
Former Member
0 Kudos

We have crossed another little milestone and we are more than 160 now on www.twitter.com/sapbwtweet. Many thanks for being there. Those of you who are still not there, be the part of group at www.twitter.com/sapbwtweet. We hope to put in lot more little tips and tricks there as we move forward and will continue with this weekly micro-blog / tweet.

 

Tweet#9 

 

Till now I have been trying to put some useful tip or trick in this block but this week I am not following the trend and putting a thought (not mine) across for discussion and your comments. 

 

This is what a friend of mine discussed while he was struggling with pretty high (critical and non-critical) volumes of data and critical and non-critical data was coming from same datasource.  Idea he proposed was –  

 

  1. Copy the standard datasource.
  2. Use both the datasources (standard and copied one) with more or less same transformations etc and same data target.
  3. Use different initialization for each datasource (one for critical data and another one for non-critical).
  4. Being two datasources, it shall have two delta queues and while extracting data reading data from delta queue shall be faster as delta queue data volume is less.
  5. Critical data upload can be prioritized.

 

Now the point of discussion is – Do you see any flip side to it?  

 

Needless to say try it on Sandbox, development system before attempting on production environment. 

 

See you next week!!!   

 

Disclaimer - Idea is to learn something in couple of seconds without going through lengthy blogs or articles. BW-Tweet hopes to exist with blogs and articles rather than replacing those. Also this is reproduction of concepts and in no way qualify as an original piece of work.

10 Comments