I have doubt on these topics.
what is the difference between single table join index and hash index ?
among these which is the good performance ?
They are both created for goOd performance.
A hash index cannot have a partitioned primary index, but a single-table join index can.
A hash index must have a primary index, but a single-table join index can be created with
or without a primary index if it is column-partitioned.
A hash index cannot be column-partitioned, but a single-table join index can be column-partitioned.
I understood that we cannot define secondary indexes, aggregate functions and triggers,PPI.
but in single table join index can create aggregate functions(count(*),sum()), secondary indexes,PPI.
BUt i need ,among these which is the good performance,many people are asking this question.
Could u please explain ..
Thanks for your quick response Raja...
In multiload, why we need to specify work tables and why we dont specify work tables in fastload. what is the reason for work tables in multi load ?
could u please explain in detail.
could anyone explain performance tuning in detail steps, that would be helpful to me.
Hope you will give the response soon.
why we need to specify work tables in multiload, why we dont specify worktables in fastload ?
Can anyone tell me the reason...
please create a new topic for new questions.
You don't specify Worktables in FastLoad cause there are no Worktables in FastLoad :-)