Databases Reference
In-Depth Information
In the preceding screenshot, you can see a small example of how you can use the
Logger package to instrument your code.
The steps that are performed are as follows:
1.
A procedure is created with the name
test
. This procedure takes two
arguments and the only thing that the procedure does is make calls to
the Logger package.
2.
The procedure is being executed in an anonymous block where the
arguments are being passed by using the named notation.
3.
Lastly the
logger_logs_5_min
view is queried to see what is being recorded.
There are many more columns available, including the complete callstack.
There are different opinions regarding logging in a production environment. Should
you have logging turned on all the time? I believe it should be turned on always.
The moment you need logging most is when something goes wrong. This moment is
impossible to predict, so keeping logging on is the only option. When you feel really
strongly about turning off logging in a production environment, the Logger package
also accommodates this. It is possible to install the
logger_no_op
(no operation)
version of the package. This is simply a shell that does not log anything in tables; it
does not even create the tables.
Eficient lookup tables
Properly designing the data model plays a crucial part in the success of your
application. An application can have a really good-looking interface, but when
the performance is very poor the users still won't be happy with the application.
To ensure your user has an overall positive experience, the application needs to
be visually attractive and responsive to the actions that the user carries out.
Designing the application begins with designing a logical
and physical data model. There are many types of database
objects, that can be used in an Oracle database, such as heap
tables, index organized tables, clusters, b-tree indexes, or
bitmap indexes. Each of these objects has its own usage. Before
implementing the physical data model, you should know each
of these object types and when to use them properly. You will
not be able to know which object type to choose, if you don't
know how the application is going to be used. Knowing how
the application is going to be used, in combination with the
available data objects, is key to the success of the application.
Your DBA should be able to help you in implementing the
proper database objects for your application.
