Archives of the TeradataForum
Message Posted: Wed, 21 Apr 2004 @ 14:39:54 GMT
There was a thread on this a few months back that may offer some help:
The only real alternatives seemed to be working with aliasing where possible to reduce the fully qualified size or break one large view into 2 or more separate ones where a main view joins them all together. The latter just requiring significant explain analysis to insure performance doesn't take a hit.
For a different approach, perhaps you could put your case logic into a look-up type table that could be joined to if the resulting where clause could be made smaller than the case statement? If nothing else, this would be much easier to maintain than a view definition if the data ever changes.
|Copyright 2016 - All Rights Reserved|
|Last Modified: 27 Dec 2016|