Any advice for setting up a 'Testing' tablespace

I am wondering how to set up an efficient Tablespace for testing our applications. I don't want to be testing these against the on-line/live DB. I can't spare disk space that much right now. Therefore, 2 full replicated DBs are out of the question.

Could I create temporary tablespaces on a project-by-project basis which would only containe the data that I would be working with?

How would data updates on 2 replicas work? Would they have to be entered on both tablespaces or not?

What are some possibilities?

Thank you!
Mir. Received on Sat May 04 1996 - 00:00:00 CEST