How Cost-Based Optimization Works: A Guide for Developers
You may have heard that you don't need to know HOW to access the data when writing code to talk to relational databases. True, but not in the way that most people think it means. If you write the right statement, the optimizer will make sure you get the right answer. However, there are many reasons why the optimizer might not get to that answer in the best way.
If you learn a little bit about how the optimizer "thinks" and how it analyzes the problems you give it, you will soon be able to predict when and why it will make mistakes and what you can do to get it to take a reasonable execution path.
Big Tools for a Small Project
Myths about small projects that use big tools, like Oracle Database, will be busted during this presentation.
Oracle is often seen as a big tool, so small projects don't bother to look into it. . NET developers don't like Oracle tools, which are part of the stack of tools they use.
Pimping SQL Developer and SQL Developer Data Modeler
Every development shop is different, which can sometimes make it hard to use tools. Both SQL Developer and Data Modeler have a number of ways to make changes. These changes can be as simple or as complicated as you want, and they can help you fit the tools into any environment. Some are as easy as a different color to remind the user which is the production and which is development.
Some could walk over a data model and have the computer write code for them. The most complicated tool can change anything. Have you ever thought of a command that SQL Plus scripting should have? Want to have table APIs made automatically?