10g (1) 11c (1) 11g (5) 12c (4) 3.0 (1) ApEx (4) Cloud (11) database (10) DBA (1) EBR (1) EC2 (2) education (3) EOUC (1) ExaData (1) F2F (1) Forms (7) java (1) language (2) memorabilia (2) Metalink vs MOS (4) multi-cultural (4) on-line communities (1) oracle (7) performance (5) projects (1) reciproke (1) Reports (2) RUP (1) sales (2) services (5) silence (1) SOA (3) SQL Server (3) standards (6) Sun (1) support (6) W8 (1) WebLogic Server (5)

Thursday, September 26, 2013

To ExaData or not to ExaData

that is the question. Several years ago ExaData platform came along. When should you go for that platform?

I do not really the beginning of the ExaData product release it was stated that it was aimed at Business Intelligence [BI] applications and not OnLine Transaction Processing [OLTP] applications. Now when Cloud computing is more and more not just a buzz word but a reality things might have changed. They have changed, the new applicances are aimed at OLTP. Which is a natural step in the ExaData product line.

However...there are troubles for the non database guys...

There are of course implications on applications. Some tips over here. But there could be more. And then Tom Kyte is not addressing the DataBase Administrators [DBA] but the developers of the applications. The transition - yes transition not migration :-) - to ExaData from a traditional Oracle DataBase solution have implications on the application.

That is not necessarliy the primary focus for the DBAs, they see the advantages from their point of view in disk space mangagement and such things that DBAs should and are caring for.

No comments: