Re: DATABASE LINKS

Rose wrote:

> They requested
> a database link to production so they can perform their research to
> the production environment through this database link.
> Their investigation consists of procedures that read files of any
> number between 50,000 to 1,000,000 records and perform queries against
> the production database - one by one. Since their customers make about
> twenty to thirty different requests every day, they don't have time to
> make up test data. Therefore they also wish to test their procedure
> with production data using this same databalink link.

I'd not do this. The risk of messing up the production database is too high should they do more than reading, and depending on the machines and the databases configuration you may run into serious performance problems with big queries - which both are a definite nono for the production database.

What I'd do is the following: Set up another seperate machine and run a mirror database on it, either by doing a daily export/import from production to mirror or by linking the mirror database directly to the production database. (The latter has the additional advantage that, should the production machine fail, you can switch to the mirror machine quickly and call it the new production machine. It requires more administrative effort though to set up.) Then let them do their research on the mirror database, in an additional seperate tablespace and under an additional seperate user.

Yours,
Stephan Received on Sun Nov 09 2003 - 17:04:03 CST