Others can answer this better, but-
In the very old days, you had to project tables. Now, with views and
temporary tables, it is rare you need project. The projected tables will
need indexes, and may take up a lot of space which can only be recovered
with a Reload.
Building the right view(s), in the right order, with the right indexes,
inner/outer joins, etal., takes some practice/skill. Post and example of
what you are trying to do and you will get some good responses.
Dennis
*****
At 10:41 AM 6/15/01 -0400, you wrote:
>
>Hello Everyone:
>
> Does anyone know if there is a document that
>explains the BEST way to deal with tables and views? What
>I mean is... 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]
>
>
>
Dennis Fleming
IISCO
http://www.TheBestCMMS.com
