May 17th, 2010 by Stewart Bryson
I’m honored and excited to be speaking at the Suncoast Oracle Users Group (SOUG) monthly meeting on May 27th, 2010, at the PricewaterhouseCoopers facility at 3109 W. Martin Luther King Blvd., Tampa, FL 33607. Much appreciation to the Oracle Nerd Chet Justice for recruiting me to speak at this event. As I’m still very much a database developer and even a DBA at heart, Chet’s website has been a great resource for me over the years. I’d also like to thank Meeting Coordinator Mike Kemp for working with me to arrange the finer points.
The title of my presentation is The OLTP DBA’s Guide to Delivering a Dimensional Model. I gave this presentation for the first time at few years back at the UKOUG conference, which was my first time to attend there. I’m working on updating the material for 11g so it’s topical and current, and in doing this, it reminds me how much I LOVE this content. My entry into the world of Oracle BI was as a data warehouse architect and ETL developer, and as much as I love working with OBIEE and a lot of the front-room products, I’m still most passionate about the database, and what separates Oracle from the rest. Whenever I do high-level assessments for clients, I still devote a portion of the documented deliverables to some of the principles I discuss in this presentation: how best to deliver the core objects in a standard dimensional model: fact tables, dimension tables and aggregates. I’ll look at issues such as index and constraint management, partitioning, compression, and enhanced database optimization strategies in the Oracle database when querying a star schema (hint: star transformation and query rewrite).
As Mike mentioned in the meeting details, I offered to speak on a variety of topics, and though this was the one chosen, I’ll be happy to address other topics in the QA session afterwards. If you plan on attending, please RSVP on the link provided. Also, drop me a line via the comments on the blog and introduce yourself, and I’ll be sure and look out for you at the meeting.