Opened 13 years ago
Last modified 13 years ago
#821 new defect
SL King Provider: Performance bottleneck when using partitioned indexes in Oracle
| Reported by: | sgamperl | Owned by: | haris |
|---|---|---|---|
| Priority: | major | Milestone: | 3.6.0 |
| Component: | KingOracle Provider | Version: | 3.6.0 |
| Severity: | 3 | Keywords: | |
| Cc: | External ID: |
Description
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.
Note:
See TracTickets
for help on using tickets.
I think the code that does the query to build the feature schema is here. Not sure if this helps much (esp if you don't know C++), but it's a starting point at least.