Rittman Mead - Delivered Intelligence

Rittman Mead is proud to announce our sponsorship of the February meeting of the Atlanta BI Users Group, a regional special interest group with involvement from IOUG, ODTUG the IOUG BIWA SIG, and the Georgia Oracle Users Group (GOUSER). I’d like to thank Greg Lancaster and the entire BI team at Cox Communications for hosting [...]

I’m sitting in the Atlanta airport waiting for my flight to Denver to go to the RMOUG Training Days, which I described here. It’s snowing (again) in Atlanta, but not very much this time, and I think my flight will take off. To reiterate about RMOUG, Mark and I will be speaking about new features [...]

Hopefully you’ve read the introduction, Part 1, and Part 2. Those posts detailed methods for building fault-tolerant ETL code, with a strong bias in favor of using Oracle Database features. Now I’ll drill into the backup and recovery aspect of data warehousing fault tolerance, and tackle the age-old question of whether to ARCHIVELOG or NOARCHIVELOG [...]

In my last post, I described the First “R” in data warehouse fault tolerance: Resuming. As I mentioned in the introduction to this series, my goal is a triage approach where the simple things, such as space errors, are handled effortlessly without repercussions. But what happens when the errors are not so simple, and Oracle’s [...]

In the introduction to this series of posts, I spoke briefly about data warehouse fault tolerance and the unique challenges resulting from high data volumes combined the batch load window required to create them. I then defined the goal: a layered approach allowing simple errors to be caught early before they turn in to serious [...]