Log Buffer #266, A Carnival of the Vanities for DBAs

Apr 6, 2012 / By Fahd Mirza

Tags: , , ,

The purpose of technology is to make life easier and more quality-oriented. It is this virtue of technology that makes it evergreen and sustainable. Its unique feature is its innovative nature. Technology blogging is a way for the technologists to rant about technology and throw light at known and unknown corners with new angles. This Log Buffer Edition covers those angles and more. Enjoy!


Oracle:

Chris Antongnini blogs about the purpose of COMMIT_WAIT and COMMIT_LOGGING parameters from the real world.

What happens to tablespaces that are read-only on the source during an RMAN duplication (not for standby)? Martin Bach asks.

Charles Hooper takes another view at the failed logon attempts.

According to Dominic Delmolino, there’s convincing and then there’s curiosity.

Karen Morton is not sure about the best practices.

SQL Server:

Chris Shaw tells us what the MVP Award is not.

There are six performance tuning mistakes you don’t want to make, according to Thomas LaRock.

James Serra blogs about SQL Server 2012: multidimensional vs tabular.

Many companies came pretty close to needing to implement their DR plans yesterday, and many of them probably didn’t even realize it.

Jack Vamvas lucidly explains a technical glitch.

MySQL:

Ovais Tariq is discussing join optimizations in MySQL 5.6 and MariaDB 5.5.

How important can a primary key be for MySQL performance?

How should Mondrian get table and column statistics? Julian Hyde asks.

Have you ever wanted to get a list of indexes and their columns for all tables in a MySQL database without having to iterate over SHOW INDEXES FROM ‘[table]‘? Aaron Brown shows a couple of ways.

Frederik Konietzny describes how to setup gitorious on ubuntu server 11.10.

Leave a Reply

  • (will not be published)

XHTML: You can use these tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>