Good input fellas,

Here's more to spark the debate..

I know there are some backup tools that wont accept files larger than 2gigs for an example; up until the latest release of Netbackup you couldn't backup files larger than 2 gig.

The main thing that I take into consideration when creating tablespaces is how big are they going to grow and the managability of the datafiles associated with them. Speaking from past experience, at one time I had a tablespace that was over 202 gigs in size with individual tables of 24 gigs. If I were to create that tablespace using 2 gig files it would be totally unmanageable. Even if I put some tables of that size (24gig) into their own tablespace you'd have 12 or more datafiles associated with that tablespace.

In a data warehouse enviornments it's not uncommon to have datafiles bigger than 2 gigs. Could you imagine having a 200 gig tablespace with 100 2 gig datafiles?

What it basically boils down to is size and manageablity of the database and the ability of OS to accept large file sizes.