Re: One view per program?

Vicki,

I reviewed that section of the Redbook. The author of that section on
database best practices makes several statements which are confusing and
misleading. The backdrop was a recommendation to pull only columns that you
need into a program as opposed to selecting all columns via Select *, which
is generally good advice.

That section does not address modular programming, which is suggested by
your question "one View per program"? No, different types of applications
will have different database requirements.

I bet you will find some use-cases for having "one View per program", and
other use-cases for having multiple views per program.

We use hundreds of SQL Views. They work great for applications. But we have
run into some administrative headaches when trying to restore Views which
have multiple-table dependencies from backup sources to libraries other
than the ones where the Views originated. We often end up restoring the
physical files - then regenerating the Views from SQL DDL Source.

Nathan.