Bob:
I think there are a lot of things that could come into play. Personal preference,
database size, structure, etc.
I avoid manipulation of data(project table..., etc) within a production database so
that I do not need to pack/reload. The only time I use this approach is on a copy of
the database, so I can discard the copy when I am done, rather than try to recover
space.
If views are properly indexed, they should be very fast.
Sometimes I select data to a file or files and create a temporary database to do the
manipulation in. I have some situations where a Basic program does the manipulation to
create the result.
I prefer views. They are usually fast enough. I find the SQL code of a view or even a
series of views easier to understand later than a Basic program or any series of
commands.
Some people use Temporary tables, but I have not. Just no experience.
Hope this helps. It is only my personal preferences.
Jim Blackburn
Kodiak
Bob Powell wrote:
> is it better to create a view that is
> comprised of numerous other tables or views rather than
> projecting tables and then combining them in a table or
> final view that contains the final result? Are there any
> hard fast rules anywhere or is it just based on the
> structure of the database and what you are currently
> attempting to do?
>
> If you have a view that contains 6 tables is it
> better to let's say project three preliminary tables that
> you then combine with a view rather than using a view to
> combine all 6 tables initially? Hope I'm making sense.
> Anyone done any testing on this?
> ----------------------
> Bob Powell
> The Hotchkiss School
> Lakeville, Connecticut
> Systems Administrator
> [EMAIL PROTECTED]
