Re: Problem with tablespace file size limit
Date: Thu, 20 Aug 2009 20:53:28 +1000
jstuglik wrote,on my timestamp of 20/08/2009 8:34 PM:
> Thank you very much for your help.
> It seems strange, I agree, that I don't want to add another datafile
> but there are some reasons to do that involving supporting of the
> application this DB is for. I think I will move some tables containing
> various statistics to another tablespace stored in another file.
> Those are the troublemakers - they are quite big and will grow
> constantly in time.
Hang on a tick: you don't want to add another file, but it's OK to add another tablespace(s) - with its(their) own file(s)?
I strongly suggest you move away from that train of thought: adding a datafile to a tablespace is the accepted and correct way to increase the capacity of a tablespace. Use it: it's there, it's standard, it won't change.
Besides if your concern is growing size, then you most definitely need to think in terms of adding files, rather than tablespaces: even the dedicated tablespaces will eventually need more files.
Unless of course you want to package averything into a self-contained set and then later on after install, as things grow, let dbas add files as needed? In that case, yes: package the large growth tables into their own tablespaces, the dbas will love your package as that is the way they like to isolate and contain large growth tables! Received on Thu Aug 20 2009 - 05:53:28 CDT