efficient at making joins? Are
the joins executed every time the view is used or is
the data cached somehow?
The other approach is for me to create a table to hold
the summary data and write application code that periodically
updates it.
Which alternative would be best?
Thanks,
Neil
to develop a summary of the data joined across
all the tables.
I can do this with a view, but I am concerned it will
take a lot of resources to perform all the joins required
by the view. Is a view efficient at making joins? Are
the joins executed every time the view is used or is
the data
Jim:
A view is no more or less efficient that the queries that
make it up. Each
time you invoke the view, you repeat all the joins.
That is what I was afraid of. With the large number
of tables I have, the joins are going to take a lot
of cycles to run.
Your solution of the summary table
