Keeping Google's In-house Database Ticking 79
An anonymous reader writes "ZDNet has a short but interesting piece on the what Google did with its 12GB database when it became a challenge for the finance department. The database was split into three, says Chris Schulze, technical program manager for Google — one for the current financial planning projections, one for the actual current data from existing HR and general ledger systems, and one storing historic information. The article says Google has been using a variety of products from Hyperion (recently bought by Oracle) to manage its internal financial systems since 2001."
Re:WTF WTF? (Score:5, Insightful)
Only 12GB? (Score:5, Insightful)
We have many databases that are larger here from MSSQL to Oracle, some around the 600GB mark.
What's so special about Google's database?
Re:WTF WTF? (Score:5, Insightful)
Plus, the "story" says that in order to manage such a large (*cough*) amount of data, the solution was to partition the database into 3 different parts. Now, I can see partitioning it for ease of management along functional areas, but certainly not because it grew to 12 whole gigabytes. If you can't handle chunks of data larger than 4 GB without partitioning it, you're in big trouble.
I'm guessing the "anonymous reader" who submitted this works for Hyperion.
Press release (Score:3, Insightful)
2. Sack Zonk (sorry man you post some good stories, this ones a stinker)
Glitch in the Matrix (Score:3, Insightful)
Uhmm, maybe it's some other Google, right...?
I can't be reading a press release from Google, the one that has more or less a copy of the whole Internet on its servers, whining about the difficulties of managing a small database on a slow Windows machine.