Skip to main content

Posts

How to do Server Caching in OBIEE

  Why OBIEE Server Caching? 1. Improve Speed of Queries 2. Reduce Network I/O 3. Reduce Database Processing 4. Reduce System Cost (charge back environments) 5. Reduce OBIEE Server Processing Caching Strategy 1. Volatility of Data 2. Granularity of Data 3. Predictability of Changes 4. Volume of Queries 5. Purging 6. Seed Cache Volatility of Data in Caching Strategy Volatility pertains to the frequency of data change in your environment. Volatile data changes more frequently (relative) than non-volatile data. Typically, the benefits of OBIEE server caching diminish as the data becomes more volatile. In other words, the amount of effort and processes to keep the cache synchronized with the data outweigh the benefits. In volatile environments, effort should be concentrated to performance tuning at the database level through a well-designed data model, physical architecture, indexing, and database caching strategy. Granularity in Caching Strategy  Tied directly to volatility i...

How to do Performance Tuning in OBIEE

  Performance Tuning Checklist  1.Browser version, Network Connection, Memory, Proxy Server 2. Web/Chart Cache Settings 3. NQSConfig.IniSettings,QueryCache ,PhysicalConnections,Metadata Configuration, Query  Plan                                        4. Materialized Views, Fragments, Indexes, Aggregates. Database Tuning There are a number of options for tuning a database for OLAP reporting. These concepts will not work well in an OLTP environment.    Tuning Options   1) Denormalize data – Denormalizing data can reduce the number of joins a query needs to perform.  Thus, reducing query response time.   2) Indexing •Index all primary and foreign keys •Index columns used frequently in drill-down or hierarchies • Use B-Tree and Bitmap indexes where appropriate.   3) Partitioning – For example, if a large amount of your queries cont...