Dynamic Table creation

I'm looking for arguments to stop developers using dynamic creation of tables in their packages to hold results of ad-hoc queries - each query creating a seperate table which is kept until the end-user has had a chance to look at the results. We currently have 16Gb (of tables alone) for the users to query, so result sets could be big! I've put the usual arguments of: not being able to tune tables; worries about large number of undeleted tables filling the tablespaces; bad design; security problems and so on, but I've had to compromise by allowing them to be created in a seperate tablespace to minimise impact on other users and programs.  

Has anyone else had any experience of this - it just feels wrong to me!

Dave Lane (dlane_at_pt.lu) Received on Wed Mar 03 1999 - 18:06:50 CST