SL King Provider: Performance bottleneck when using partitioned indexes in Oracle
|Reported by:||sgamperl||Owned by:||haris|
There is a performance bottleneck when a partitioned index is created on an Oracle table. The Oracle tables have millions of rows and there exists about 1000 partitions per table. When we use these schema in a MapGuide map, the DescribeSchema command is very slow. I think the problem is the join to the USER_SDO_INDEX_INFO and the join to the USER_SDO_INDEX_METADATA table. Why is this join necessary for describing the schema? Maybe a option would be to specify the bounds of a feature class within the KingFdoViews or use the SDO_GEOM_METADATA information for the bounds.