Read an Excerpt
I've written this book with the hope that it will serve as mylifetime technical contribution to my database administrator (DBA)brethren. It contains the sum knowledge and wisdom I've gathered thispast decade, both working on and speaking about data warehousing. Itdoes so purely from the DBA's perspective, solely for the DBA's needsand benefit.
While I've worked on many data warehousing projects, my three yearsat Electronic Data Systems (EDS) as the lead DBA for 7-ElevenCorporation's enterprise data warehouse provided my greatest learningexperience. 7-Eleven is a world leader in convenience retailing, withover 21,000 stores worldwide. The 7-Eleven enterprise data warehouse:
- Is multi-terabyte in size, with tables having hundreds of millionsor billions of rows.
- Is a true star schema design based on accurate business criteria andrequirements.
- Has average and maximum report runtimes of seven minutes and fourhours, respectively.
- Is operational 16X6 (i.e. the database is available 16 hours perday, 6 days per week).
- Has base data and aggregations that are no more than 24 hours old(i.e., updated daily).
While the 7-Eleven enterprise data warehouse may sound impressive,it was not that way from Day One. We started with Oracle 7.2 and a smallHewlett–Packard (HP) K-class server. We felt like genuine explorers aswe charted new territory for both EDS and 7-Eleven. There were fewreference books or white papers at that time with any detailed datawarehousing techniques. Plus, there were few DBAs who had alreadysuccessfully built multi-terabyte data warehouses with whom to network.Fortunately, EDS and 7-Eleven recognized this fact and embraced thetruly iterative nature of data warehousing development.
Since you are reading this book, it's safe to assume we can agreethat data warehousing is radically different than traditional onlinetransaction processing (OLTP) applications. Whereas OLTP database andapplication development is generally well-defined and thus easy tocontrol via policies and procedures, data warehousing is more iterativeand experimental. You need the freedom, support, and longevity tointelligently experiment ad-infinitum. With few universal golden rulesto apply, often the method of finding what works best for a given datawarehouse is to:
- Brainstorm for design or tuning ideas.
- Add those ideas to a persistent list of ideas.
- Try whichever ideas currently look promising.
- Record a history of ideas attempted and their results.
- Keep one good idea out of 10-20 tried per iteration.
- Repeat the cycle with an ever growing list of new ideas
As Thomas Peters states, "Life is pretty simple: You do some stuff.Most fails. Some works. You do more of what works." That's some of thebest advice I can recommend for successfully building a data warehouseas well.
Purpose
There are numerous data warehousing books out there, so why is thisone different? Simply put: its DBA focus on implementation details. Infact, the mission statement for this book is:
To serve as the DBA's definitive and detailed reference regardingthe successful design, construction, tuning, and maintenance of starschema data warehouses in Oracle 8i and 9i.
So how is this different from what's already out there? In general,I've found that most data warehousing books fall into one of threecategories:
- Conceptual—Primarily educational about theories andpractices, with very high-level information
- Overview—Catalogs of hardware, software, and databaseoptions, with few specific recommendations
- Cookbook—Detailed, DBA-oriented advice for all the datawarehouse development lifecycle stages
Respectively, "best-of-breed" examples for these three categoriesare:
- Data Warehouse Tool Kit: Practical Techniques for BuildingDimensional Data Warehouses by Ralph Kimball
- Oracle8 Data Warehousing by Gary Dodge and Tim Gorman
This book, primarily since no other book exists with this kind ofdetailed DBA advice
I mean no disrespect to these other categories or their books. Ihighly recommend Kimball's book to anyone new to data warehousing. Anduntil such time as this books debuts, I also highly recommend Dodge'sbook for DBAs.
Audience
This book is intended for physical DBAs—period, end of story. Thisbook assumes an extensive and detailed working knowledge of Oracletechnologies. Moreover, it presumes a keen awareness of hardware andsoftware options—often a skill possessed only by DBAs who also serve asat least the backup operating system (OS) administrator as well. Thatsaid, there are chapters that will be both applicable and beneficial toother members of the data warehousing team.
The sections on data modeling define how a DBA should interpret andextrapolate an entity relationship diagram (ERD) into a physicaldatabase design. So, this chapter would assist data modelers andapplication architects to understand how a DBA uses their input tocreate the underlying database structure.
Likewise, the sections on staging, promoting, and aggregating datadefine how a DBA should manage objects and processes to mostexpeditiously load massive amounts of data. So, this chapter would beboth educational and inspirational to extract, transform, and load (ETL)programmers tasked with loading a data warehouse.
And finally, the chapter on querying the data defines the indices,statistics, and plans necessary to deliver the best possible ad-hocquery runtimes. So, this chapter would assist business intelligencefront-end designers, who can appreciate how the database handles theircomplex, ad-hoc queries.