1. How do you set up a database to automatically handle efficient growth (automatic addition of datafiles) in Windows?
2. How should the tablespaces themselves be configured? (how should they be named, automatic growth, etc.?)

We are strictly a development shop and are creating an application for a customer that uses 10g. We are looking for the minimal setup for our Windows 2003, non-RAID server, that will allow us to simulate data loads. We want to load about 100 gb worth of data to tune indexes and our queries. I know that this is by no means anywhere close to the type of server that should handle this type of load, but a bad performing query is universal. We have run into 4gb limitations for the size of table space files before and are looking for a way to overcome that with minimal maintenance while we are performing our tests.