Hi Khurram,
Thank you very much for quick response and also the link. I have one more question. The below query gives the result as shown
sel tablename,definedcombinedpartitions,maxcombinedpartitions from dbc.PartitioningConstraintsV WHERE databasename = 'Inform_User' and tablename in ('TABLEA', 'TABLEB')
TableName,DefinedCombinedPartitions,MaxCombinedPartitions
TABLEB, 8012, 8012
ABLEA, 972, 972
from the results my Understanding is that there are 8012 and 972 partitions already created. But the explain query still does all row scan. So is this also due to contents given in the above link?
Thanks,
Sharat Balaji
Hi Khurram,
Thank you very much for quick response and also the link. I have one more question. The below query gives the result as shown
sel tablename,definedcombinedpartitions,maxcombinedpartitions from dbc.PartitioningConstraintsV WHERE databasename = 'Inform_User' and tablename in ('TABLEA', 'TABLEB')
TableName,DefinedCombinedPartitions,MaxCombinedPartitions
TABLEB, 8012, 8012
ABLEA, 972, 972
from the results my Understanding is that there are 8012 and 972 partitions already created. But the explain query still does all row scan. So is this also due to contents given in the above link?
Thanks,
Sharat Balaji