You have a lot of newsgroups in your post. I am removing all except one.
"Rose" <com> wrote in message
The last sentence above seems to indicate the Business Investigation
Department (what is this department ? an computer/IT or client department?)
wants to create a database link in a non-production database to a production
Again trying to make sure I understand you correctly... performing queriES
over a database link 50,000 to 1,000,000 times via a procedure (Plsql?)!
Everytime you use the database link , you are hitting/impacting! the
Is the above setup strictly for testing some new procedure in a test
database and then later moving it to production where the production setup
would not use a database link? If so, then it might be ok assuming EVERYONE
knows this is obviously impacting (and probably severely impacting!) the
production database everytime they test it in the test database.
Seems you should propose a better solution like copying the production data
(or a subset of it) to the test environment? Or setup the test database
tables in production and test in production without a database link
(assuming they don't mind impacting production because that is what the
database link proposal will do).
If not possible to copy production data to the test database(size?), then
they should just create the procedure and test in the production database.
It might be easier to setup the test database tables in the production
Anyway, the proposal will obviously impact production with the database link
(and this is ok?) and it will probably be more of an impact than if they
just do it staight into the production database without a database link
(assuming size is a problem and so data cannot be copied to the test