Re: VIEWS compared to Nodes as Windows into data

From: Dawn M. Wolthuis <>
Date: Thu, 29 Apr 2004 08:45:08 -0500
Message-ID: <c6r0tc$9f5$>

"Dawn M. Wolthuis" <> wrote in message news:c6m06j$r1h$
> Given a database application implemented in an RDBMS with 632 tables where
> we want to give Pat an online data catalog from which to shop for data
> values by way of metadata, we would likely provide a set of SQL VIEWS,
> correct?
> From what I have seen, if there is data in a supporting table XYZ that is
> only sometimes needed when reporting about a particular entity (such as
> Customers), then one might have two VIEWS of that data -- one with and one
> without XYZ joined in.

Is this an accurate perspective on SQL VIEWS? Are there "extra" VIEWS, more portals into the data, or whatever, created simply for performance reasons? Is there a DBMS that provides a better top level "data catalog" that doesn't include performance issues mixed with what data values you can "shop for" (query)?

Thanks. --dawn Received on Thu Apr 29 2004 - 15:45:08 CEST

Original text of this message