Skip to Content

It’s time for mini-celebration as we are now 50 on www.twitter.com/sapbwtweet. Thanks to all of you who have decided to be part of it and hopefully more shall be joining in. We hope to put in lot more content there as we move forward and will continue with this weekly micro-blog / tweet.  

SAPBWtweet 

Tweet#5 

This one comes from a colleague of mine at Wipro ( Vishal HemantSanghvi)  Use table – RRKMULTIPROVHINT and see substantial query performance improvement on Multiproviders with more than 5 cubes which are part providers (partitioned on similar characteristics).Usually the query needs to fetch the data only from a couple of part providers. So, if the query has restrictions on the characteristic which is/are used to partition the MultiProvider, the OLAP processor checks only for those part cubes and returns the data to the query. 

Wanna try… check for more details –

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/751be690-0201-0010-5e80-f4f92fb4e4ab?overridelayout=true

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.  

To report this post you need to login first.

6 Comments

You must be Logged on to comment or reply to a post.

    1. Vikash Agrawal Post author
      🙂 yes it should have been.

      Glad you liked the concept, there has been bit of discussion while we started it.

      Look forward to your continued support.

      Regards

      Vikash

      (0) 

Leave a Reply