Thursday, February 14, 2013

The Ten Commandments Of OBIEE Projects

  1. Thou shalt not take the name of Oracle Support in vain no matter how many times your SR is bounced back to you for non-essential additional details
  2. Thou shalt not make a dashboard that requires scrolling down eight times;  nor fashion a report that returns more than 50,000 rows for exporting to the evil Excel.   
  3. Honor thy Project Manager when he or she does not get involved in technical design decisions for this is a great and righteous occasion.
  4. Thou shalt not claim credit for thy brilliant OBIEE hacks that came from a Google search
  5. Thou shalt respect the eyesight of an aging workforce by not creating reports using 6 point type.
  6. Remember the dimensional model and be true to its purity and sanctity.   Turn your back on the unholy bridge tables and snowflake schemas. STAR_TRANSFORMATION_ENABLED = DIVINE;
  7. Thou shalt not kill server response time by avoiding aggregate tables in your RPD design and disabling caching;
  8. Give thanks daily for a DBA who responds joyfully to requests without questioning thy intelligence and heritage
  9. Thou shalt not bear false witness by claiming that the RPD is "self-documenting". 
  10. Remember the "go live" day, to keep it holy, for it may seem like a heavenly place right up until the words "Phase 2" are pronounced.


  1. Cache is bad. Should only be used as the final frontier of tuning AFTER ALL OF the networks, hardware components, applications, RPD and SQL has been tuned to the point of no more tuning.

  2. Thou shalt not covet cache as a tuning option.