Once again this week, you are holding the new edition of Log Buffer in your hands. From across the database planet, fresh and sizzling blog posts of Oracle, SQL Server and MySQL are presented just for you in Log Buffer #230. Enjoy and give your feedback in the comments.
Have you ever wondered about the V$OPEN_CURSOR view, the SESSION_CACHED_CURSORS parameter, and the two session-level statistics “session cursor cache count” and “session cursor cache hits”? Charles Hooper asks.
The Exadata IO Resource Manager (IORM) is a fundamental piece of the exadata database machine since the beginning. The function of the IORM is to guarantee a database and/or category (set via the database resource manager) gets the share of IO as defined in the resource plan at each storage server. Frits Hoogland has more.
Dough Burns shares some interesting tidbits.
Martin Wildake thinks that the Index Organized Tables(IOTs) are a much under-used and yet very useful feature of Oracle.
You open a ticket and wait… When you do get a reply it tells you to send information you’ve already posted, or suggests you try some workarounds you’ve already listed in the ticket as having not worked for you. Sounds familir? read on here.
Kevin Kline is considering himself lucky and sharing something he is reading which he believes that the readers will enjoy too.
Replication is the SQL equivalent of Marmite as far as many people are concerned (you either love it or hate it, Richard Douglas has more.
Do you get error 435 in the Application event log and your SQLAgent fails to start? Ryan Adams asserts that the reason you’re getting this error is that the SQLAgent error log and working directory file locations are not available.
It’s been clear for a while now that Sharepoint is at the heart of Microsoft’s BI strategy. Chris Webb shows the signs.
When does InnoDB compress and decompress pages? Mark Callaghan has the answer in this blog post.
Gerardo Narvaja has written a post about the capabilities and issues regarding MySQL SNMP agent.
Kentoku Shiba is pleased to announce the release of Spider storage engine version 2.26(beta) and Vertical Partitioning storage engine version 0.15(beta). Spider is a Storage Engine for database sharding. Vertical Partitioning is a Storage Engine for vertical partitioning for a table.
It is common practice in MySQL table design that fields are declared as NOT NULL but some non-sense DEFAULT values are specified for unknown field contents. In this article Shinguz show why this behavior is non optimal an why you should better declare a field to allow NULL values and use NULL values instead of some dummy values.
“List me all databases that have a current replication delay of more than 10 seconds.”
“Easy. Let’s fetch the data from Merlin.” And that is how it started.
Interested in working with Fahd? Schedule a tech call.