1 / 14

How Not to Build an Oracle Application (Top Ten List of Things NOT to DO) Kerry Osborne

How Not to Build an Oracle Application (Top Ten List of Things NOT to DO) Kerry Osborne Senior Oracle Guy Blog: kerryosborne.oracle-guy.com. Who am I?. I added this slide because everyone else had one! Started working with Oracle in 1983 Developer and DBA and Trainer

judith
Download Presentation

How Not to Build an Oracle Application (Top Ten List of Things NOT to DO) Kerry Osborne

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. How Not to Build an Oracle Application (Top Ten List of Things NOT to DO) Kerry Osborne Senior Oracle Guy Blog: kerryosborne.oracle-guy.com

  2. Who am I? I added this slide because everyone else had one! • Started working with Oracle in 1983 • Developer and DBA and Trainer • Became a consultant around 1987 • Started a little company, grew it, shrunk it, sold it • Started another little company • … • Never worked directly for Oracle • Not certified in anything • Don’t even know what the Oak Table is?

  3. Basis for this talk? My Totally Unscientific Survey • Hundreds of Oracle projects • Hundreds of Oracle professionals • Selective memory (I don’t remember all of them) You can observe a lot just by watching. ~ Yogi Berra

  4. Top 10 List- Things Not To Do • 1. Hire Developers that Don’t Know SQL • Get good XYZ programmers – let the DBA’s tune the SQL

  5. Top 10 List- Things Not To Do • 2. Write a db access layer to isolate the developers Now your in the tool business!

  6. Top 10 List - Things Not To Do • 3. Generate a new session for every sql statement 10,000 traces in a single batch window

  7. Top 10 List - Things Not To Do • 4. Issue a commit after every statement (even better – do it more often than that) JDBC, ODBC – have a built in option to commit after each statement – autocommit Log File Sync – turned out to be the number one event at one client

  8. Top 10 List - Things Not To Do • 5. Don’t allow Cost Based Optimizer to do it’s job • Use Rule Based • Hint everything • Use bad statistics

  9. Top 10 List - Things Not To Do • 6. Use an unpopular tool/language • Get one that no one has experience with • Or better yet, write your own

  10. Top 10 List - Things Not To Do • 7. Don’t use tools you already own • Spend a lot of money on a sexy tool • Spend a lot of time learning how to use it • Use it for everything

  11. Top 10 List - Things Not To Do • 8. If it isn’t fast enough, throw hardware at it • I suggest starting with disk • Then CPU’s • Then memory

  12. Top 10 List - Things Not To Do 9. Don’t Worry About Concurrency • Oracle is really good at it • So why should you worry

  13. Top 10 List - Things Not To Do 10. Do everything one row at a time • Why do something once • When you can do it 100 times

  14. Questions? Kerry.Osborne@enkitec.com

More Related