Re: Database with large number of schema objects

If those dynamic tables an be dropped then you can reduce the burden on the backup and recovery by using the UNRECOVERABLE option while creating the tables. As obvious as it may sound, more schema objects means, your data dictionary will be large also, which calls for more space in your system tablespace.
The way you put, I am tempted to think that those dynamic tables can be dropped once its job is done. Do consider that you may get a solution.

HTH,
CM

In article <6khkr9$s9c$1_at_nnrp1.dejanews.com>,   mkaushik_at_harvestinc.com wrote:
>
>
> Among several options that we have for a specific problem,
> one solution calls for dynamically creating additional schema
> objects (mainly tables) Over time the number of tables would
> be 10,000+
>
> I am looking for information on the potential effects of a large
> number of schema objects on database performance or any other
> aspect of database administration and usage like backup, archival
> etc.
>
> Any experiences with databases with large number of schema objects ?
>
> - Malini Kaushik
>
> -----== Posted via Deja News, The Leader in Internet Discussion ==-----
> http://www.dejanews.com/ Now offering spam-free web-based newsreading
>

-----== Posted via Deja News, The Leader in Internet Discussion ==----- http://www.dejanews.com/ Now offering spam-free web-based newsreading Received on Fri May 29 1998 - 10:16:08 CDT