Log Buffer #194, A Carnival of The Vanities for DBAs
Jul 11, 2010 / By Vanessa Simmons
We’re well into summer and almost at our 200th edition of Log Buffer, a blog of blogs about the database world.
Remember if you find a link or interesting blog post that you think Log Buffer should mention, send a note to the editor at Log Buffer and be sure to include the link, and a short note outlining why you think that particular post would be of value to other DBAs, or what you learned from reading it.
Now on to our weekly reading in Log Buffer #194:
Oracle Exadata is a topic that is getting hotter and hotter. Following Pythian’s announcement of Exadata services Oracle’s Greg Rahn stresses how important it is to “capitalize on the opportunity to re-engineer with Exadata and fully exploit the power of the Oracle Database Machine platform”. Also speaking of Exadata, Kerry Osborne talks on his blog, about the Oracle 11g Release 2 new feature, Parallel Queuing, and how it applies to data warehousing workloads on Exadata. Marc Fielding begins his grand tour of Exadata, writing to share his implementation experience.
Jamie Thomson outlines a number of reasons why a SQL server or BI developer should learn .net. And with more activity on SQLblog.com, Jonathan Kehayias writes about a bug in SQL Server 2008 and why you shouldn’t create large tables in the Model Database.
On In Recovery, Paul Randal posts on Benchmarking: Introducing SSDs (Part 2 – Sequential Inserts), following his first set of tests and analysis of the results. In Part 1 and Part 1b he covers not overloaded log file array.
Barry Leslie announces PBMS is now in the Drizzle tree.
And to sum things up, Gwen Shapira shares a few of her favorite recent archives, a little older than our weekly news, but valuable nontheless.
Not strictly a database topic, but certainly an important lesson for data architects. Brian Carper shares the difficult life of an edge case. Keep him in mind next time you develop an online shop. The same Brian Carper shares why he migrated from MySQL to NoSQL (Tokyo Cabinet) and why he moved back to SQL (Postgres this time).