Views vs joins

Question

Hi,
It may be a very basic question, but exploring blogs got me that there will not be much performance improvement if query is not used heavily.
But what if query is used heavily.
I have a query that is executing for several thousands of time(it is in loop).
This query uses join to 4 heavily populated table(with record count > 30 millions in each table [There is no mechanism to purge old data ] )
This query is taking consuming more time [though query is tuned and is using bind variables]. Basic level DBA investigation are already performed like gathering statistics, De-fragmenting, etc.
Sample Query :
SELECT   table1.col1, table2.col2
   FROM    table1,
                  table2,
                  table3,
                  table4
WHERE   cond1
AND          cond2
AND          cond3
AND          cond4
AND          cond5
ORDER BY table3.col1
Will creating a view be useful for above query and querying on that view be help to improve performance issue...?
CREATE OR REPLACE VIEW SOME_VIEW
AS
SELECT   table1.col1, table2.col2
   FROM    table1,
                  table2,
                  table3,
                  table4
Kindly guide/suggest.

Answer 1

Satyakunal wrote:
Thanks all for response!!!
We thought of eliminating this query from loop, However current design does not permits it.
As this is a part of application which is already live since years, design change would take time.
Anyways as suggested and I too felt that Iast alternative would be a design change.
I would say it's the first alternative.  If you cannot just change the code to avoid the looping (you haven't explained why) and replace with more pure SQL, and this requires a redesign of the database, then you are better to start thinking about how you are going to implement this redesign (in small steps or one big go as appropriate?) right now before the problem becomes an even bigger problem.  There's an English saying "A stitch in time saves nine"...  ( A stitch in time saves nine )