Spatial Performance Problem

Question

I'm new to GIS development, and hereby got a performance comparison.
Techs adopted time consumed to display the whole map in one time
ESRI SDE + Oracle Spatial 6 Mins
ESRI SDE + Oracle 1 Min 20 Sec
ESRI SDE + SQLSERVER 50 Sec
ESRI SDE + Shapefile 30 Sec
Shape file size 550M, totally 480k rows
Can anyone tell me why SDE + Spatial works so low performance than SDE + SQL SERVER, and what can I do to improve the performance when adopt just SDE + ORACLE(just for storage like normal RDBMS).
I don't think Oracle will work worse than SQL Server in SDE environment. But what should I pay attention to during using Oracle to store map data for SDE.
Is that not a normal scense to use SDE with Oracle Spatial? Why I got so bad performance? I just migrate data from Shapefile to SDO_GEOMETRY type and add indexes as Spatial required.
Any one can leave your comment if you know something about this.
Thanks in advance.

Answer 1

Here is a partitioning example as promised. Note an upcoming talk at Oracle Open World will show how to extend this model to include spatial partitioning, where we will describe some really important optimizations that will bring scalability (already a differentiator) to new levels. After Oracle Open World we'll post that information to OTN as well (please come talk to us if you happen to go).
-- First, remove table partition_sales if it exists
drop table partition_sales;
-- Create table partition_sales. This table is partitioned
-- by date range, breaking each year into 4 quarters.
-- What users see is a single table called partition_sales
-- but in reality there is one smaller table created for
-- each partition
-- For simplicity we are loading all partitions into the same
-- tablespace. Most often they are loaded into separate tablespaces
-- for performance, scalability, and manageability reasons
CREATE TABLE partition_sales
( customer_id number,
sale_date date,
sale_amount number(10,2),
geom mdsys.sdo_geometry
PARTITION BY RANGE (sale_date)
(PARTITION BEFORE_2003
VALUES LESS THAN (TO_DATE('01-JAN-2003','DD-MON-YYYY')),
PARTITION Q1_2003 VALUES LESS THAN (TO_DATE('01-APR-2003','DD-MON-YYYY')),
PARTITION Q2_2003 VALUES LESS THAN (TO_DATE('01-JUL-2003','DD-MON-YYYY')),
PARTITION Q3_2003 VALUES LESS THAN (TO_DATE('01-OCT-2003','DD-MON-YYYY')),
PARTITION Q4_2003 VALUES LESS THAN (TO_DATE('01-JAN-2004','DD-MON-YYYY')),
PARTITION Q1_2004 VALUES LESS THAN (TO_DATE('01-APR-2004','DD-MON-YYYY')),
PARTITION Q2_2004 VALUES LESS THAN (TO_DATE('01-JUL-2004','DD-MON-YYYY')),
PARTITION Q3_2004 VALUES LESS THAN (TO_DATE('01-OCT-2004','DD-MON-YYYY')),
PARTITION Q4_2004 VALUES LESS THAN (TO_DATE('01-JAN-2005','DD-MON-YYYY')),
PARTITION AFTER_2004
VALUES LESS THAN (MAXVALUE));
-- Each of these inserts goes into a separate partition.
-- Although there are only 9 rows inserted, each into a separate
-- partition, if you had 50 million rows they would be divided into
-- smaller, more manageable pieces
insert into partition_sales values (61243, '31-DEC-2002', 18764.23,
mdsys.sdo_geometry(2001, 8307,
mdsys.sdo_point_type(-73.943849, 40.66980, NULL), NULL, NULL) );
insert into partition_sales values (4576, '15-JAN-2003', 27797.05,
mdsys.sdo_geometry(2001, 8307,
mdsys.sdo_point_type(-71.017892, 42.336029, NULL), NULL, NULL) );
insert into partition_sales values (1161, '22-MAY-2003', 16222.50,
mdsys.sdo_geometry(2001, 8307,
mdsys.sdo_point_type(-76.610616, 39.30080, NULL), NULL, NULL) );
insert into partition_sales values (55033, '09-SEP-2003', 1211.33,
mdsys.sdo_geometry(2001, 8307,
mdsys.sdo_point_type(-77.016167, 38.90505, NULL), NULL, NULL) );
insert into partition_sales values (768, '15-DEC-2003', 84397.61,
mdsys.sdo_geometry(2001, 8307,
mdsys.sdo_point_type(-73.943851, 40.66975, NULL), NULL, NULL) );
insert into partition_sales values (61243, '05-JAN-2004', 21764.26,
mdsys.sdo_geometry(2001, 8307,
mdsys.sdo_point_type(-73.943849, 40.66980, NULL), NULL, NULL) );
insert into partition_sales values (6474, '17-JUN-2004', 76411.81,
mdsys.sdo_geometry(2001, 8307,
mdsys.sdo_point_type(-85.256956, 35.066209, NULL), NULL, NULL) );
insert into partition_sales values (505, '27-JUL-2004', 104100.89,
mdsys.sdo_geometry(2001, 8307,
mdsys.sdo_point_type(-74.173245, 40.7241, NULL), NULL, NULL) );
insert into partition_sales values (9151, '11-OCT-2004', 44298.66,
mdsys.sdo_geometry(2001, 8307,
mdsys.sdo_point_type(-79.976702, 40.43920, NULL), NULL, NULL) );
commit;
-- Let's make sure what we thought happened actually did happen
-- The following allows us to see how many rows are stored in each partition
exec dbms_stats.gather_table_stats('SCOTT','PARTITION_SALES');
select partition_name,num_rows
from user_tab_partitions
where table_name='PARTITION_SALES';
-- Now the data is loaded, we can spatially index it
-- First, insert into user_sdo_geom_metadata
delete from user_sdo_geom_metadata where table_name = 'PARTITION_SALES'
and column_name = 'GEOM';
insert into user_sdo_geom_metadata values ('PARTITION_SALES', 'GEOM',
mdsys.sdo_dim_array (
mdsys.sdo_dim_element ('LONG', -180, 180, 1),
mdsys.sdo_dim_element ('LAT', -90, 90, 1)),
8307);
-- Now create the index. Note the keyword local is used
-- which creates a separate index for each partition
-- Because this example is simple, we didn't show storage
-- of each spatial index partition in a separate tablespace,
-- which is the common usage, again for performance, scalability,
-- and manageability.
drop index partition_sales_sidx;
create index partition_sales_sidx on partition_sales (geom)
indextype is mdsys.spatial_index parameters ('layer_gtype=point')
local;
-- Any query that uses the partition key (the date) will only search the
-- partition associated with that date:
select customer_id, sale_amount
from partition_sales
where sale_date = '17-JUN-2004'
and sdo_relate(geom,
mdsys.sdo_geometry(2003, 8307, null, mdsys.sdo_elem_info_array(1,1003,1),
mdsys.sdo_ordinate_array(-86,34, -85,34, -85,36, -86,36, -86,34)),
'mask=anyinteract querytype=window') = 'TRUE';
-- The previous query only touched a single partition.
-- You don't have to specify the partition key, though.
-- All partitions can be searched if required. To speed up
-- these kinds of queries, you can search all partitions in
-- parallel by specifying the keywork parallel in the
-- create index statement, or altering the index
alter index partition_sales_sidx parallel 4;
-- No date specified in this query, so all partitions may be searched
select customer_id, sale_amount, sale_date
from partition_sales
where sdo_relate(geom,
mdsys.sdo_geometry(2003, 8307, null, mdsys.sdo_elem_info_array(1,1003,1),
mdsys.sdo_ordinate_array(-75,38, -70,38, -70,45, -75,45, -75,38)),
'mask=anyinteract querytype=window') = 'TRUE';