Re: retrieve foreign keys list

There's always the problem with Oracle of what can be done and what should be done.

In these cases, the developer should have considered performance (as always) and operated to minimise the impact on production.

e.g.when remote table is not too extreme

    create local table nologging as
    select from remote_table;
or

    export from production out of hours
    import into development

You can't blame a screwdriver if it
doesn't do a good job of hammering
in nails.

--
Jonathan Lewis

Host to The Co-operative Oracle Users' FAQ
http://www.jlcomp.demon.co.uk/faq/ind_faq/html

Author of:
Practical Oracle 8i: Building Efficient Databases
See http://www.jlcomp.demon.co.uk/book_rev.html

Seminars on getting the best out of Oracle
See http://www.jlcomp.demon.co.uk/seminar.html


mel wrote in message <3b2e2038$0$356$45beb828_at_newscene.com>...


>

>Thomas what about situations where u join tables accross links, espically

 when


>the query brings over millions of rows.

>

>we had 2 situations that were problmes with links

>

>1 - user used link on dev machine (where he had create and insert right)

 to


>porduction where he had only read rights.  He did insert into a dev table

>selecting from production table.  That table had over 100 million rows

 leading


>to space problem on dev and bad network performance til lwe killed it.

>

>2.  Trying to do a join of a dev table with a prod talbe, the query brought

>over prod table and then joined it on dev side.  prod tale was over 20

 million


>rows

>

>

>also with datalinks word gets around and eveybody want to use it.

>

>

>Also Tom when is the release date on your book?  Can't wait :)

>