Skip to main content

Larry goes eXtreme!

Two years after the moment that Oracle went into Operating Systems - Unbreakable Linux - today Larry announced that Oracle (partnering with HP) will sell hardware also. And it's not a simple commodity server... It's the HP Oracle Database Machine. This beast contains 8 database servers (with 64 cores in total) and 14 eXadata servers (with 112 cores). And an enormous amount of storage: 1400 times more than the largest iPod! I think it could contain all mp3's in the world...
An eXadata Server (officially known as the HP Oracle Exadata Programmable Storage Server) contains 2 processors with 8 cores each, 12 disks, Enterprise Linux and - and this is the coolest part - Parallel Query processing capability for every disk. By bringing processing capability close to the storage, the amount of data going through the wires from a storage server to a database server is dramatically reduced - because results are passed instead of datablocks. Because of this architecure the performance will remain the same as the database is growing - just add some more servers and it will be fine. So this is the last piece of the grid-puzzle: Next to Fusion Middleware grid and Database Grid, Oracle can provide us now with Storage Grid.
The performance of this thing is gigantic: tests proved that queries will run 10 to 50 (!) times faster than on current available hardware.
And now ofcourse the closing question: What does it cost?
A Database Machine costs $650,000 - which is $4,000 per terabyte, and that is much cheaper than other storage around. Apart from that there is 'some' license involved for the software : $1,680,000 (and surely an annual fee of 15% of that amount). So it's not for free...but it can replace a room full of yout current hardware!
Post a Comment

Popular posts from this blog

Showing a success message after closing a modal dialog

APEX 5 comes with Modal Dialogs out of the box. Very neat. Especially for adding and changing data. And to minimise the number of time a user has to click, it could be useful to add a "Close Dialog" process after the actual data processing. When the data processing fails, the Dialog stays on top showing the error. When data processing runs fine, the Dialog is closed ... without any confirmation. And this might be scary for a shaky user.

So how can we provide the user some feedback? On Page 4 of the Sample Dialog Application you can see one solution: up on a Dialog Closed Event on the parent page it does a redirect to refresh the parent page appending the success message of the "Close Dialog" process. This has two drawbacks. First, it probably refreshes more than necessary. And second, if you're using multiple layers of dialogs (dialogs that open other dialogs) the message appears in the "parent dialog".
As an alternative you could follow these steps: 1…

APEX 5 New Static File Features

In APEX 4 you could upload files - like CSS files, JavaScript files, Images and whatever else you like - into the APEX Repository. When you navigate to Shared Components, there is a Files section that offers three different options:
CSS Files are always uploaded (and changed !) for the whole Workspace. For Images and Static Files (usually JavaScript) you could choose whether they should be available for the whole Workspace or for a specific Application only. And if you had a lot of files - e.g. a lot of images - then you had to go through the upload process one-by-one. But that's usually a one time only thing. If you make changes to the CSS and JavaScript files - and that's a continuous process in development - then you had to delete the existing file and upload the new one. Over and over again. And meanwhile fighting the cache of the webserver and your browser.  And another irritating issue: You couldn't use relative references in your CSS or JavaScript files as they just…

Using LDAP for Authentication and Authorization within APEX

One of my current customers would like to use their LDAP (Microsoft Active Directory) server for authentication and authorization of APEX applications. Of course we tried to set up a standard LDAP Authenication that's available within APEX. But we couldn't get that to work. Maybe it has to do with the fact that the client stored their Users within Groups within Groups within .... . Or maybe it doesn't do a full tree walk in the directory. Or maybe it is just because it is Microsoft - and not Oracle Internet Directory (OID). So we moved to a custom Authentication using the DBMS_LDAP functions (and some examples from the Pro Oracle Application Express book and Tim Hall - a.k.a. Oracle Base).

One of the issues we encountered that we wanted to use the user's login name, like "jdoe" and not his full name ("John Doe"). And the login name is stored in the "sAMAccountName" attribute. But authenticating using just "jdoe" didn't work. …