I seriously doubt that the database is already configured with these options, as there are very little views defined and they are not indexed views.

Thanks again :)

>Not a view, but an indexed view (or a materialized view). They are two different animals. An indexed view is like a poor-man's analysis cube. You are flattening the normalized tables to make queries run much faster. You will be bypassing the joins and 80% of the work that the optimizer performs when generating an execution plan. The whole query will be one or more index scans.
>
>The downside is that you have to maintain a set of configuration options in the database or individually on any object that interacts with the view. And the index(es) will eat up a lot of disk space.
>
>If your database isn't already configured with these options, it could be a lot of work to perform an impact assessment of the changes.