lewisje

76 million rows...SDE st_geometry vs Oracle sdo_geometry...

Discussion created by lewisje on Sep 11, 2013
Latest reply on Sep 27, 2013 by vangelo-esristaff
Does anyone know of why the sde.st_geometry functions take so long to run?  I need convert 76 million lat/lon's to shape objects. 

We're running on a Windows 2008 server using Oracle 11gR2 64bit with 64G ram and 24 core processors.

Following is the code I used to accomplish this and the results of both the SDE methods and the Oracle methods.

--Oracle sdo_geomtry�?�

create table sample_points (
RECORDID,
SHAPE) nologging as
  (select  /*+ NO_PARALLEL_INDEX(jl) */
   tab_row_id,
sdo_geometry(2001, null,
sdo_point_type(longitude, latitude, null)
null,null)
from jl_points_all jl);


Table created.

Elapsed: 00:01:24.29

--ESRI st_geometry�?�

create table sample_points (
   RECORDID,
   SHAPE) nologging as
   (select  /*+ NO_PARALLEL_INDEX(jl) */
           tab_row_id,
           sde.st_geometry (longitude, latitude, null, null,0)
   from jl_points_all jl);


--Still running after 11 hours �?? only 4% of the datablocks read from the source table.

Does anyone know of faster methods using the SDE functions?

Thanks in advance

John

Outcomes