Best practices for tablespace/datafiles sizes???
441858Mar 14 2010 — edited Mar 16 2010Oracle 11gR2
Hi All,
I was wondering if there were any best practices for tablespace sizes and the number of datafiles in a tablespace? I'm thinking in terms of manageability and recovery.
The questions that come to mind are:
1. What is the max size you should let your tablespace reach before you create a new one?
2. What are the max number of datafiles you should have in a tablespace before you create a new tablespace? How many datafiles are too many? (related to the first one).
3. Are there any consequences of having very large tablespaces other than increased recovery times?
We are in the TBs so I'm just trying to figure a policy/rule that I should follow.
Thanks.