ORACLE INTERNALS

Do you love SQL*Plus but hate that you can’t use it with other, non-Oracle databases?  Do you wish you could more easily migrate some of your MySQL or Postgres applications to Oracle?  If so, stay tuned, because my next few blog entries are going to show you how to do just that.  But first, I want to throw a little teaser out there for the SQL*Plus crowd…

Let’s face it, SQL*Plus is an awesome tool.  And, it’s a tool everyone who’s had to manage databases from multiple RDBMS vendors wishes they could use against all of them.  Well, if you’re using Postgres, MySQL, SQL Server, or DB2 and are tired of using cheap, JDBC-driven SQL*Plus knock-offs, my next blog entry will show you how to interface the real SQL*Plus with each of those systems using nothing but Instant Client, a couple libraries, and a little ingenuity.

If you’ve read EnterpriseDB’s latest press release, you’ll notice a new feature called Infinite Cache.  While it may sound revolutionary, it is not a new technology.  In fact, it was done for MySQL quite awhile ago under the Waffle Grid project.

While I consider this type of caching relatively simple, I don’t want Oracle to be left out.  As such, I’m going to join the fray by throwing my own project, Mercury Distributed Cache for Oracle, into the mix.

Similar to Waffle Grid for MySQL and Infinite Cache for EnterpriseDB, Mercury supplements the Oracle buffer cache with optimized, network-based data block storage to reduce the amount of read-related disk I/O which must be performed when working with large-scale databases.

For the time being, please forward all Mercury-related questions directly to me via email.