RE: Materialized Views

Markus, MV's are really useful when You are using analytical applications that are able to generate ad-hoc DSS queries automatically for end-user (like Business Objects) In such situations, DBA can create pre-aggregated MV's of underlying huge fact tables for most-used types of queries so that the database server could route queries from huge fact table to pre-aggregated tables - MV's If application has control over which table to use (pre-aggregated or original), then I don't see very big difference between having MV and 'manually' creating pre-aggregated table and updating it'd data in a batch job. Another approach is to use analytical applications (like Informix MetaCube, which is still alive), which are aware of pre-aggregate tables and allow to redirect ad-hoc analytical queries from original tables to pre-aggregated tables at the application level. In that case, MV's are not necessary. That is, clever application doesn't require MV. As for the support, I don't see any significant difference between supporting MV's and 'manually' supporting aggregate table. Interesting, are there other aggregate-aware Business Intellegence applicationce in the market except MetaCube? ------------------------------------------ Alexey Sonkin > -----Original Message----- > From: Markus Bschorer [mailto:mb@worxbox.com] > > Hi, > > I heard somthing about materialized views for oracle and sql-Server. I > think, this technique is very interesting, especially when you have to > join > certain "less-change"-tables very often. > > Is there any comparable technique for Informix (IDS 9.4)? > > Thanks in advance! > > Bye > Markus > > sending to informix-list