- Kevin Closson cancelled his session, which was a bummer, but life goes on.
- Oracle Optimizer Roundtable: Some members of the optimizer team answered the audience questions.
- Real-World Database Performance Roundtable: Members of this group answered questions from the audience on a variety of performance related subjects.
The roundtable sessions were pretty cool, but it feels a little like groundhog day sometimes. I think I could summarize much of the advice as follows:
- Design your database properly.
- Write good SQL. This is usually pretty easy if you have a good design.
- Use default settings and functionality, unless you hit an issue that forces you not to. Even then, don’t assume you can not use the defaults for other projects. Work on an exception basis, not a one-size-fits all approach.
- Newer versions of the database probably have features to eliminate or offset the problems seen in previous versions. If possible upgrade and make sure you understand the new features so you can apply them.
I don’t know about you, but this list has been true for as long as I’ve worked in Oracle. Unless you are working on systems requiring extreme performance or of extreme size, modern Oracle versions make life incredibly easy. It would be cool if people actually started taking the advice given by these guys every year…