Re: Recommendation on issuing DDL in applications

Matthew Keene wrote:

> We have had a proposal at our site for an application which would
> create a temporary table dynamically, populate it and then drop it.
> My general feeling was that this is not a very good idea, but I was
> looking for some sort of evidence to support this (unfortunately 'the
> DBA says no' is not enough as a reason). I did some research on
> Metalink and on the web to come up with some reasons I could give them
> to persuade them not to do this, but the best that I could come up
> with was the following quote from the 9i Database Design Techniques
> manual
>
> "As a general database design rule, you should only use DDL statements
> for maintenance tasks, not during normal system operations. Therefore,
> in most systems, the frequency of new object creation and other DDL
> statements should be very small."
>
> Does anybody have any more specific information that I can use to
> frighten them away, oops, I mean rationally discourage them from this
> solution, or am I being unnecessarily alarmist ?

Your DBA is not qualified to have those three letters appended to his or her name.

Had this person even a minimal knowledge of Oracle architecture they would know that this an architecture based on working with other database products that do not have MVCC.

Send this person the links below my signature and suggest they take a course on the subject in which they claim, by virtue of their title, expertise.

You are correct that it is not a good idea. In fact it is a horrible idea. A good idea would be to have you take the DBA's job. I've little doubt you would do a better job.

--
Daniel Morgan
http://www.outreach.washington.edu/extinfo/certprog/oad/oad_crs.asp
http://www.outreach.washington.edu/extinfo/certprog/aoa/aoa_main.asp
damorgan_at_x.washington.edu
(replace 'x' with a 'u' to reply)