SAP Business Warehouse

Partition count contest!

Let’s have a contest! One of my last blog posts started off a discussion (e.g. Bala posted his thought in a blog) about the importance of the partitioning feature for an SAP BW installation. No doubt about it – partitioning is something we use heavily for SAP BW. Breaking the work down into smaller pieces Partition count contest!

Question to SAP Support “Why is partition pruning not working in my BW on Oracle?”

Welcome to the problem As usual understanding, the meaning and the scope of the question is key for the answer to this question, recently filed by a customer. So, what is the customer complaining about? What does he mean by “partition pruning“? It’s a feature of the query optimizer to figure out, which partitions of Question to SAP Support “Why is partition pruning not working in my BW on Oracle?”

Small changes with big effects

For many BW performance relevant DB-features, it’s really all about the details of usage and implementation when it’s about the effect of those features. The following are two examples of rather small things that went wrong which had a big impact on the system performance. Two examples for BW on MaxDB The first two examples Small changes with big effects

BW on Oracle: a performance hunch I see more and more often…

Ok, once again reproducing a problem takes a lot of (waiting-)time for the query to finish. In the meantime I can also just write a super-short-blog post about a pretty common BW-on-Oracle performance hunch: Inappropriate database optimizer statistics. (yes, ‘inappropriate’ not ‘outdated’!) Usually, that means: if everything runs as it is supposed to, BW will BW on Oracle: a performance hunch I see more and more often…

A first (BW) issue…

In the second week working in BW support, I noticed that there was a problem reported by customers again and again. The customers complained about “database statistics update fails in process chains” or “brconnect run returns errors”. When checking the relevant log file entries for the actions there was always something like ERROR at line A first (BW) issue…