Hi there.
I'm attempting to implement MQTs to improve performance on some nasty
SQL.
In the Oracle world, if I recall, materialized views must use tables
as underlying objects - ie., they cannot be based on views.
Does the same hold in db2 (8.2 LUW, 8 z/OS)?
I'm looking in SQL reference 2 about the syntax for the fullselect,
and although I suspect by the wording that I am correct, I'm not
finding a specific statement such that an underlying object referenced
by the fullselect cannot be a view.
I'll keep looking...
Tx,
BD.
I'm attempting to implement MQTs to improve performance on some nasty
SQL.
In the Oracle world, if I recall, materialized views must use tables
as underlying objects - ie., they cannot be based on views.
Does the same hold in db2 (8.2 LUW, 8 z/OS)?
I'm looking in SQL reference 2 about the syntax for the fullselect,
and although I suspect by the wording that I am correct, I'm not
finding a specific statement such that an underlying object referenced
by the fullselect cannot be a view.
I'll keep looking...
Tx,
BD.
Comment