Skip to Main Content

#SmartDB Office Hours

Free tips and training every month! Subscribe for reminders and more from Office Hours. FAQ

Header container

February 19, 2019

19:00 UTC   Start Times Around the World

Subscribe to be notified of changes to sessions and give us feedback!

Having trouble watching the video on this page? Open the video in your browser.


Should the database be used as a persistence layer only, or as a full-fledged processing engine that runs business logic too? We believe that “processing engine” is the right answer. Moreover, we believe that the database should be exposed to client-side programs only by a PL/SQL API. We call this approach the SmartDB paradigm, and we use this name as our Twitter hashtag. We argue that SmartDB is the proper way to build correct and secure applications on Oracle Database. We especially like that the approach brings, as a happy side-effect, best performance and maintainability.

Use these sessions to put any and all questions that you might have about SmartDB to Bryn Llewellyn and Toon Koppelaars.

Your Experts



    Toon has been part of the Oracle eco-system since 1987. He is currently a member of Oracle's Real-World Performance team. The RWP-team troubleshoots application performance issues in and around the DBMS. The way applications currently use the DBMS, is often at the root of these performance issues. Prior to joining the RWP team, Toon has been mainly involved in database application development. His special interests are: architecting applications for performance and scalability, database design, and business rules / constraints modeling (see his idea on SQL Assertions here He is a long-time champion of the Smart Database paradigm, i.e. using the database as a processing engine, and not just as a persistence layer.

All Sessions