Oracle Scratchpad

One-day Developer

Back to main Tutorial Page


The one-day Developer course – Agenda

This is a course aimed at developers who wants to learn what the database can do to help them produce better applications. Its focus is very much on the database engine – what the engine hopes to be given as a workload. The tutorial covers overheads, structural features, coding strategies, indexing, and execution plans.

Although the course is intended for the more senior developers, it can also act as a rapid introduction to critical mechanisms of the database that the junior DBA should need to know..

Note – the material is about the database and using it properly; it is not about programming and programming languages. This day is most suitable for the enthusiastic developer who wants to be more aware of how the database and application can co-operate to work as efficiently as possible.

Session 1
1.5 hours


A basic introduction to the costs of the infrastructure that makes Oracle what it is. Topics include connection costs, network traffic, parsing and optimising costs, undo generation and use, and redo.

Break – coffee and informal discussion: 30 minutes
Session 2

1.5 hours

Coding Strategies

There are good ways to code and bad ways to code. This session demonstrates the problems with the bad coding strategies and shows how much difference it makes when you do it right.

Break – Lunch and informal discussion: 1 hour
Session 3

1.5 hours


A description of indexes, largely devoted to B-tree indexes, talking about structure, how they work, and the paths Oracle is able to take through them. Indications of how to get the most out of indexes, and minimise the cost of indexing, with warnings about side effects of the different strategies for making an index more useful.

Break – coffee and informal discussion: 30 minutes
Session 4

1.5 hours

Execution paths

In this session, we take an introductory view on how the cost based optimizer works, including a brief overview of the different join mechanisms. Then we examine execution paths and the developer-oriented ways of acquiring them. Finally we learn how to read and interpret execution paths.



Back to main Tutorial Page

Leave a Comment »

No comments yet.

RSS feed for comments on this post.

Comments and related questions are welcome.

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Website Powered by