The Mistakes of the Relational Camp: Mistake #1: The de-emphasis of physical database design
It is unlikely that application developers will develop highly performant and scalable applications if they don’t have access to performance metrics. EM Express in Oracle Database 12c has taken a step in the right direction by making it possible to give developers access to some performance metrics. From the interview with ACE Director Kyle Hailey in Oracle Magazine:
Oracle Database 12c introduces an administration console called Oracle Enterprise Manager Database Express, a “light” version of Oracle Enterprise Manager that developers can access through a browser. “Now DBAs can give the developers read-only access to a simplified database management console so they can see the impact of their code,” says Hailey.
This is a big change from the traditional setup, where the effect of code was seen only in the DBA’s world. “The DBA has this privileged access to see what’s happening with the database,” Hailey says. “He can see load go up and see who caused it, but the poor developer writes some code, runs some code, and maybe sees some text on a screen—but there’s no visual impact. The developer doesn’t know what’s going on in the database, and that’s not fair. The DBA comes and complains that the developers are making a mess, and the developer says, ‘How am I supposed to know?’ With [Oracle Enterprise Manager Database Express], developers will be able to see the effect of their code and, if there’s a problem, shut it down before the DBA comes calling.”
Instructions for giving EM Express access to non-administrative users are at http://docs.oracle.com/cd/E16655_01/server.121/e17643/em_manage.htm#BABHCDGA.
See also : No! to SQL and No! to NoSQL
The inventor of the relational model, Dr. Edgar “Ted” Codd believed that the suppression of physical database design details was the chief advantage of the relational model. He made the case in the very first sentence of the very first paper on the relational model saying “Future users of large data banks must be protected from having to know how the data is organized in the machine (the internal representation).” (“A Relational Model of Data for Large Shared Data Banks,” reprinted with permission in the 100th issue of the NoCOUG Journal.)
How likely is it that application developers will develop highly performant and scalable applications if they are shielded from the internal representation of data? The de-emphasis of physical database design was the biggest mistake of the relational camp and provided the opening for NoSQL…
View original post 452 more words