Log Buffer #117: A Carnival of the Vanities for DBAs

Posted in: Technical Track

Welcome to the 117th edition of Log Buffer, the weekly review of database blogs.

For those of you who don’t know me, my name is Nicklas Westerlund, and I’m a MySQL DBA with The Pythian Group. This is my first time writing Log Buffer, and I hope I’ll do it right.

Let’s start off with SQL Server, where Simon Sabin asks if you know what concurrency is and how to improve it. And on SatisticsIO, Jason Massie focuses on the SQL Server 2008 experience instead, which should provide more inside knowledge of the technology used.

Continuing on with SQL Server 2008, the engineering team is sending loads of engineers to the SQL PASS Conference, as the SQL Server Customer Advisory Team tells us in their post on what, in their opinion, just may be the best PASS Conference yet. And if you’re into meeting engineers, then perhaps you’d also like to know how that patching is done in SQL Server 2008, which PSS SQL informs us about.

The folks over at sqlserver-qa.net also give us an overview of the SQL Server Web Edition.

Let’s move over to Oracle, where there’s still a lot of buzz about Exadata, and let’s start with with the second part of the Exadata FAQ by Kevin Closson. In that post he also mentions his interview on the Exadata with Paul and Christo here at Pythian.

Continuing with the Exadata, the Oracle Insider Blog gives us the inside scoop of the Exadata announcement via a podcast interview with Rich Palmer of HP and Oracle’s Willie Hardie.

In other news, Jonathan Lewis talks about finding the root cause, in a different way.

Speaking of performance also brings me to the changes in Oracle 11g, where H.Tonguç Yılmaz talks about enhancements to ALTER TABLE … ADD COLUMN functionality.

And to round off the Oracle part, we should take a look at what Mark Rittman is saying about the Oracle BI Server query log file.

On the PostgreSQL side, depesz (Hubert Lubaczewski) talks about LC_COLLATE and LC_CTYPE in 8.4.

The Postgres OnLine Journal looks into how to delete functions, which they say can help if you need to streamline your SQL.

You can see the future of the Firebird DBMS, as captured and blogged about by Martijn Tonies, which was taken from the recent Firebird Conference 2008. Marco Cantù also offers his summary of the conference.

Now, let’s move on over to MySQL, where Jay Pipes has confirmed that he is leaving the MySQL Community team. Giuseppe Maxia announced that they are now seeking clone of Jay Pipes. But Jay is moving over to the Drizzle team instead.

As you may know, Drizzle is a more lightweight MySQL. Giuseppe looks at drizzling MySQL 6, with its performance improvements in subqueries. This seems very promising.

Over at the MySQL Performance Blog, Vadim takes a look at what is stored in the InnoDB buffer pool, and Ewen talks about why triggers are bad for replication.

As we are getting closer to April and the MySQL Conference & Expo, Jay reminds us to submit our papers.

Here at the Pythian Group Blog, Sheeri Cabral reports that the Community Contribution Agreement has changed to the standard Sun Agreement.

And as a closing item, does anyone remember the request (Google cache, as the page is offline) for donations to help Andrii Nikitin’s son Ivan? Well, Kaj Arno gives us some good news—Ivan is feeling better and better.

In closing, I’d like to thank you for your time in reading this, and I’ll pass the stick back over to David Edwards.

Have a good weekend everyone.

email
Want to talk with an expert? Schedule a call with our team to get the conversation started.

1 Comment. Leave new

David Edwards
October 3, 2008 12:24 pm

Thanks for the LB, Nick.

Re the stick: As much as I love it, I’m handing it right off to Ward Pond for next week’s LB #118. The stick—and Log Buffer—is for sharing, so I invite any database blogger to get in touch if they too want to get their hands on it. LB is good fun, and a great way to direct some more readers to your blog.

Cheers,
Dave.

Reply

Leave a Reply

Your email address will not be published. Required fields are marked *