Archives of the TeradataForum
Message Posted: Fri, 25 Apr 2003 @ 08:46:24 GMT
I think you got this error message because your user does not have PERM SPACE. A join index - just like any of the other NCR indices - is implemented as a second table (which explain the overhead you get upon loading, etc).
You should be able to use SUM & COUNT as join indices are Teradatas answer to Oracles materialized views - basically aggregate tables that maintain themselves as they will automatically reflect the changes in the underlying tables.
(Don't know about rank & case though...)
All, when I first experimented with join indexes in the very frist version of V2R4 we began to have problems with our database randomly creating crashdumps & needing to be restarted. The problems subsided after we stopped using JI. (No formal relationship between those events had been established - so it might have been a coincidence - but obviously the shop I was at was very reluctant to ever try JI again...) Can anybody speak to if they experienced similar problems? - or testify that they didn't? (Maybe in addition with the Version they are running on).
Also, is there some sort of formula that helps you determine the overhead in space & load-time that you get from adding a join index?
Any input would be appreciated!
|Copyright 2016 - All Rights Reserved|
|Last Modified: 27 Dec 2016|