Juan, Unfortunately, that solution requires that you have enough disk space to hold an entire copy of production, not to mention the archive logs that will be generated by deleting data. I'm looking for clever solutions to this problem. I suppose writing your own referentially-correct ETL from Production to Test is one way. That's sort of what the DataBee product does, I think. Subsetting a production DB for test would be an excellent new feature for 10g! Best regards, David B. Wagoner Database Administrator -----Original Message----- From: Juan Cachito Reyes Pacheco [mailto:jreyes@xxxxxxxxxxxxxxxx] Sent: Monday, March 01, 2004 1:44 PM To: oracle-l@xxxxxxxxxxxxx Subject: Re: Methods to Create Smaller Test DB from Production? You can copy the production database, the optimal You can delete records, and make this faster, and export import statistics to get performance test more accurate to reality. ----- Original Message ----- From: David Wagoner <mailto:dwagoner@xxxxxxxxxxxxxxxxxx> To: ORACLE-L (E-mail) <mailto:oracle-l@xxxxxxxxxxxxx> Sent: Monday, March 01, 2004 2:37 PM Subject: Methods to Create Smaller Test DB from Production? I know many of you have addressed this same issue... What is a good method to create a smaller test database from Production? I've read about the commercial product called DataBee for doing this, but what other methods are you guys using? With all of the expertise in this list, there are bound to be some interesting solutions. Best regards, David B. Wagoner Database Administrator