Recommendation on issuing DDL in applications

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 ? Received on Thu Aug 28 2003 - 02:08:17 CDT