Change the design

[suresh_dsx]

HI all,
we have 100 jobs in my project.
source/ Target --> oracle.
only 30 jobs are we are using source view (DS Quary) in the source oracle stage.
We created one view in the oracle. we splitted in to two views for simplicity.
we are using the second view in the DS Quary.
with in the quary we are joining with the Materlised view from the target table.
How can use that target table directily... If we need to access to the table we need to get DB Links beacuse different schema.
The final aim is to remove the DS Quary in the data stage.. we need to use only one view and also i want to care about tuning the view and also job with less resources.
can you please give some suggestions on this.

[ray.wurlod]

The best solution will be one that uses no views at all. Second best is to use materialized views.

If you use a standard view you have first to execute the SELECT statement that defines the view before you can even begin to select rows from the view (that is, from the result set of its defining query).

A materialized view only time-shifts this overhead.

If you can select from the base tables, your query constraints can be assisted by indexing. This will always yield the fastest delivery of rows.

[chulett]

How can use that target table directily... If we need to access to the table we need to get DB Links beacuse different schema.

You don't need a dblink to access a different schema - you'd need one to connect to a different instance however. Or to join tables from different instances as if they were in the same instance. Not all that speedily, of course.