 |
 |
Archives of the TeradataForum
Message Posted: Mon, 11 Aug 2008 @ 22:02:53 GMT
| Subj: | | Re: Pros & Cons Of Complex Views In a Production / Batch Area |
| |
| From: | | gerrydaly |
In our environment, we have used, primarily, work tables to build up to the final table(s). However, with some recent changes, we have utilized
some very complex views. Our experience was that there were performance issues, particularly if the complexity of the join was not just on the
number of tables and the inclusion of outer joins, but in large numbers of case expressions that were doing the logic work our load processes had
been previously handling-- the CPU usage became a significant issue.
We ended up going with a model that is a hybrid. We have some rather complicated views that move the processing logic to the views themselves,
but then during the load the view is used as the source and a final table as the destination, with a simple SELECT * view overlayed on it for user
data access. This approach has proven to be successful-- better load times than the old approach without any degradation in data access.
| |
