Skip to main content

OOW2006 - Day 1 (Monday) : Worst Practices Day

For me this Monday started with an (Developer) Keynote by Thomas Kurian: The next application platform. Thomas pointed out three main trends : SOA, Information Driven Architecture an Grid Computing Architecture. For the developers (about 1200 in the Grand Ballroom of the Hilton) he mentioned the tools Oracle offers for building applications on the 3-tier architecture (of course: JDev, SOA Suite and SQL Developer). The most important announcement was the availabilty of the Oracle Developer Depot, were you can easily download an install Java applications to facilitate code reuse and simplify the development process. Of course you can upload your work to this comunity. You can even win a meet and greet with Larry (or an HD TV) if your software is selected as "the best".

For the next session a headed over to Moscone for The Future of DB Technology by Andy Mendelsohn. He addressed (a.o.) the next interesting new products / features / options :
      Information Lifecycle Management
      How to match storage to the information lifecycle to minimize costs (put data that you need less often - or with less performance - on less expensive storage ) by using partitioning. For decision support Oracle offers the Oracle ILM Assistant, a free downloadable program that shows the gains and migration of implementing ILM.

      Database Vault
      Audit and manage the use of data by other users (even the DBA) under the motto "Keep your DBA out of the database".

      Online Application Upgrade (or Online Hot Patching)
      To assure 24x7 availability in Oracle 11 you can upgrade your database while users are using the application. Currently logged in users continue working in the pre upgrade version of the application, new logins will use the upgraded application. They even showed an impressive live demo of this feature!

      Database Capture (I think that was the name he used)
      A tool to capture SQL statements from one environment (e.g. Production) and run it in another (e.g. Test) and localize the differences in the CBO and/or capture statements in a pre upgrade version (e.g. Oracle 10g) and replay these statements in an upgraded version (e.g. Oracle 11) to spot the differences in execution plans - to facilitate the tuning pre- and post upgrade.

The third session this day was Developing PL/SQL Programs Using Automated Unit Testing by my honourable colleague Andrew Clarke. He used the utPLSQL framework ( http://utplsql.sourceforge.net, http://utplsql.oracledeveloper.nl) to facilitate Test Driven Development - an approach that is also strongly supported by Quests PL/SQL Evangelist Steven Feuerstein.

The fourth session was Database Worst Practices by Thomas Kyte. A very popular session, because although the session was sold out, 200 people stood in line to get in! Luckily for those who missed it, Tom repeated this gig on Thursday. In his own special way, with lots of humour, Tom gave a tongue-in-cheek presentation (which is not - yet - available on the Openworld Presentation Download site, but it is on asktom!).
The most important "worst practices" were:
      Never ever question authority
      You do not need bind variables
      You don't want to expose end users to errors (exception when others then null)
      Generic is better
      You don't need a design
      Create as many instance per server
      Reinvent database features
      No need to test
      Only use varchar
      Commit frequently
      No scalability needed, because nothing ever changes

The fifth and last session (who says that visiting OOW isn't hard work!) was called Unleashing the Power of Oracle Streams by Patricia McElroy. I wasn't familiar with Streams (a little with AQ), but was quite impressed with the capabilities of this feature (option?). Streams facilitates an asynchronous information sharing architecture by capturing, staging and consumption of data. IMHO the functionality is similar to the ESB but on the database tier instead of the middle tier. Because the processes run close to the data I expect that the throughput of Streams will be much higher (compared to using the ESB).

After all this hard work this evening was reserved for the OTN Night in the St Francis (just across the street from our hotel). By accident I first visited a Quest party on the 32nd floor of the hotel, with good food, free drinks and a splendid view of SF. When I came down to the 2nd floor the OTN Jeopardy game was still going on, where the contesters excellerated in giving wrong (or no) answers to difficult Oracle related questions (I did not get one right answer...) and everybody was having good time eating, drinking, talking, dancing and looking and the belly dancers (with snake).
Post a Comment

Popular posts from this blog

Push changed rows to an Interactive Grid

For pushing changes from the database to the end user, the regular solution is using websockets. A change in a record is detected - using a trigger or using the CQN (Change Query Notification) feature - and a notification is send to a websocket server. That websocket server broadcasts the notification over a channel to all browsers that are tuned in to that websocket channel. Then the browser reacts to that notification, usually showing an alert or refreshing a report. This trick is described on multiple sites, just Google for "oracle apex websockets" or similar.

So back in the old days, we used that notification in the browser to refresh the (interactive) report. But along comes the Interactive Grid (IG). While he full-refresh mechanism still works for IG, an IG has also the option to refresh just one row.  So wouldn't it be awesome that just the changed row(s) get refreshed upon a change in the database, instead of the whole report? Can we do it ... yes we can!
First i…

Refresh selected row(s) in an Interactive Grid

In my previous post I blogged about pushing changed rows from the dabatase into an Interactive Grid. The use case I'll cover right here is probably more common - and therefore more useful!

Until we had the IG, we showed the data in a report (Interactive or Classic). Changes to the data where made by popping up a form page, making changes, saving and refreshing the report upon closing the dialog. Or by clicking an icon / button / link in your report that makes some changes to the data (like changing a status) and ... refresh the report.  That all works fine, but the downsides are: The whole dataset is returned from the server to the client - again and again. And if your pagination size is large, that does lead to more and more network traffic, more interpretation by the browser and more waiting time for the end user.The "current record" might be out of focus after the refresh, especially by larger pagination sizes, as the first rows will be shown. Or (even worse) while you…

Dockerize your APEX development environment

Nowadays Docker is everywhere. It is one of the main components of Continuous Integration / Continuous Development environments. That alone indicates Docker has to be seen more as a Software Delivery Platform than as a replacement of a virtual machine.

However ...

If you are running an Oracle database using Docker on your local machine to develop some APEX application, you will probably not move that container is a whole to test and production environments. Because in that case you would not only deliver a new APEX application to the production environment - which is a good thing - but also overwrite the data in production with the data from your development environment. And that won't make your users very excited.
So in this set up you will be using Docker as a replacement of a Virtual Machine and not as a Delivery Platform.
And that's exactly the way Martin is using it as he described in this recent blog post. It is an ideal way to get up and running with an Oracle database …