setting up a succesful production and development environment

[ncs]

I am currently working with a production database that has exceeded the original estimations. In an attempt to limit or stay on top of the tables created, I have created several users with limited privilages. The only problem is, the developers have created several temp and junk tables within their own schema that are entirely too large.

What is the best way to set up a development environment to allow testing prior to populating the production database?

Several of the main tables used in processing contain over 50 million records and counting......

[sreddy]

Clarify me first! You have production with Junk tables OR you have development with junk tables you are trying to cleanup ?

[ncs]

I have junk tables within production under the devloper instance.

[sreddy]

Here we are dealing with terminology. Production database and developer schema ? OR Production server and developer instance(database) ?

[ncs]

It is a production server. There are 3 different schemas within the database itself. The developers were restricted to a "temp" schema to try and cut down updates to vital tables. Instead, there are several junk tables that have been created from the main tables.

[tamilselvan]

First of all you should not use PRDN and DEVL schemas in the same server.
Buy one NT server for $3000 and use it for development.

Otherwise , You should give quota on each tablespace for the DEVL team.

[ncs]

I do agree with you but the purchase and allocation of the boxes was totally out of my hands. That is half the problem...it is essentially regaining control of the database and doing clean up after the fact because of the way someone decided to implement this project.
Any suggestions?