CHAN
asked on
Sybase IQ Questions
Hi
It would be a great help if anybody knows the answer for the following queries :
1. In a Sybase IQ Multiplex environment, which process synchronize the secondary nodes using TLV log.
2. In a column with FP index, where and how the row ids are maintained? How about in column with LF index?
3. Does the LF index get rebuilt after loading the data?
thanks
CS
It would be a great help if anybody knows the answer for the following queries :
1. In a Sybase IQ Multiplex environment, which process synchronize the secondary nodes using TLV log.
2. In a column with FP index, where and how the row ids are maintained? How about in column with LF index?
3. Does the LF index get rebuilt after loading the data?
thanks
CS
ASKER
Thanks Joe.
Whenever the failed secondary nodes comes back online, there is an internal process which will read TLV log from IQ store and sync the catalog store of that secondary node. Am I right?
Now I understand the ROWID concept in FP index . What about in LF index, is the ROWID attached to LF index column values?
Regards
CS
Whenever the failed secondary nodes comes back online, there is an internal process which will read TLV log from IQ store and sync the catalog store of that secondary node. Am I right?
Now I understand the ROWID concept in FP index . What about in LF index, is the ROWID attached to LF index column values?
Regards
CS
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks Joe.
Regards
CS
Regards
CS
2) The data is the FP index. There is always an FP on every column because that's where the column's data lives. The ROWID on every column is just the array entry. Remember IQ stores everything in columns, there is actually no real "row" anywhere. "Row #10" just means "the 10th entry in the FP array of column1 + the 10th entry in the FP array of column2" and so on. Is that making sense? The ROWID is not stored anywhere, just as the number of each array entry is also not stored anywhere, it is the data structure.
3) Every index is rebuilt during loads. Unlike traditional RDBMS, it is faster to index an empty table then load it than the other way around. Test it and see. :)