You have a lot of newsgroups in your post. I am removing all except one.
--
"Rose" <rosebernardo_at_yahoo.com> wrote in message
news:d200c71d.0311081723.4a3acd71_at_posting.google.com...
> I am working for the Business Investigation Department. They requested
> a database link to production so they can perform their research to
> the production environment through this database link.
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
database.
> 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
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?)!
> 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.
Everytime you use the database link , you are hitting/impacting! the
production environment.
>
> I believe this whole thing to be crazy. Can someone give me some very
> good technical explanation and/or point me to somewhere I can get a
> technical paper of something I can give to my boss to stop my boss?
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
database.
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
database).
Received on Sat Nov 08 2003 - 23:40:42 CST
