Bob,
No hard rules that I know of...
I rely on views with as many as 9 tables/views with good results.
You may need to spend some time optimizing the underlying
indexes and the the view construct for performance sake, but it's
not a big deal.
With the new proj temporary table command there may be times
where it makes more sense to project those tables and base a
view from there (maybe you're dealing with a small data-subset that
you're quering often... so extracting it once may be better than a
view that's extracting that same dataset each time the view is
referenced)
Ben Petersen
On 15 Jun 2001, at 10:41, Bob Powell 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]
>
>
